Skip to content
English - United Kingdom
More support Customer Portal Sign In
See Our Pricing
  • There are no suggestions because the search field is empty.

Communications to NUC stopped with QSYS system

 

1. IP Address / Subnet mismatch

  • Q-SYS Core might be on a static IP, while the NUC got a new DHCP IP
  • Subnet mask could be different (e.g., 255.255.255.0 vs 255.255.0.0)
  • Both devices must be in the same network range

2. Gateway changes

  • Not critical for local communication, but if changed incorrectly it can sometimes affect routing

3. VLAN change

  • Switch port might have been moved to a different VLAN
  • Q-SYS and NUC could now be on separate VLANs → no communication

4. DHCP vs Static conflict

  • One device switched from static → DHCP or vice versa
  • IP conflict may occur if duplicate IP is assigned

5. Network adapter settings on NUC

  • Adapter disabled/enabled incorrectly
  • Wrong adapter being used (Wi-Fi vs Ethernet)
  • Priority/metric changed so traffic is going through another interface

6. Firewall / Security changes

  • Windows Firewall blocking Q-SYS Designer / control ports
  • Antivirus or policy update restricting communication

7. NIC speed/duplex mismatch

  • Adapter forced to 100 Mbps / Full vs Auto negotiation
  • Can cause intermittent or no connection

8. Q-SYS Core network settings

  • Core set to different IP mode (AutoIP / Static)
  • Designer file might be pointing to old IP

9. Switch configuration

  • Port shutdown or reconfigured
  • PoE issues (if applicable)
  • Spanning tree delay or port security blocking MAC

10. DNS / Hostname resolution

  • If system uses hostname instead of IP, DNS might not resolve

How do I manage devices remotely so that I don't need to escalate issues as they happen? 

Our SPORTrack platform gives you the ability to remotely monitor and manage all of your devices, across the globe. Check out the SPORTrack platform here.