I’m having a lot of trouble getting my 2x SC600 / X1850 setup to take an assigned IP address from my network. Have tested multiple cables and different power-up orders for the players and the mixer. I’ve tried factory resets, refresh IP address from the utility menu etc. Nothing seems to get it to grab an address from my DHCP server. My network is all on a 10.10.10.XXX IP address set. However the mixer only ever gets 169.254.180.18 as it’s IP address.
Any help would be appreciated. Thanks!
Have you tried factory resetting your Router?
If it gets APIPA (169.254.x.x) then DHCP isn’t working on the network or the ethernet switch in the mixer is broken.
Do the SC6000’s get an IP if they’re directly connected to the network (omitting the mixer)?
I don’t think a factory reset of the router is warranted. Perhaps doing a deep dive in the Router’s console to see if the devices are at least visible (assuming the router’s software is sophisticated enough).
I connect my 4 SC6000Ms to the network directly via a switch and they seem to get IP addresses just fine.
My only thoughts are, someone has been poking around in the Router settings (lots of buttons to press, lots of settings to change, lots to go wrong) and they have somehow restricted the level of access devices have to connect. So a factory reset would remove all that potential config and open the device back up for connection.
Yes that is possible for sure.
I work in telecoms, and have more to do with networks/wifi than i want to as part of my day job… but even i get a bit confused with the mass of config options in my Router’s GUI. They are a bit like network printers, an absolute minefield.
Yeah, for sure!
Computers are complicated machines, no matter how many attempts to make them simpler – they still remain very very complicated. Networking itself is a slew of abstractions known as the OSI model:
I don’t do much network programming and i feel it’s a mind-bender.
100% man, it might even be something simple like port forwarding to other devices that is causing the conflict. If they aren’t able to tap into the DHCP pool to obtain an IP i dare say something has been set to block that type of device.
Thanks all, I’ll try some of these suggestions tonight. However, no one has been poking around in the router settings and I’ve never had issues with any other devices not getting IP’s assigned. Regardless I’ll try resetting it tonight. No harm in that.
I have a second device, a Synology NAS that can also function as a DHCP server (currently disabled). I may try disabling the router DHCP and switching to the NAS for that just to see if it’s a weird incompatibility with the Router & X1850. Too bad no option for Manual IP. If my 5 year old $100 HP printer can do that, so should the X1850…
Hi Reese, I’ll try this tonight. Question, is there a way to see the assigned IP in the SC6000 interface?
Do the SC6000’s get an address within the correct subnet ?
What is the topology ?
Not in the normal GUI, but you could check internet access if you have any streaming service. Or check the router if it has given a DHCP lease.
Not even close. I run my network on 10.10.10.1-255 and the IP 169.254.180.18 is what gets assigned.
Using nmap, you could scan your network for active devices:
sudo nmap -sn 10.0.1.0/24
...
Nmap scan report for sc6000m.localdomain (10.0.1.36)
Host is up (0.00036s latency).
...
And see which ones have one or more of the following TCP ports open.
sudo masscan -p1-65535 10.0.1.36 --rate=1000
Password:
Starting masscan 1.3.2 (http://bit.ly/14GZzcT) at 2024-06-05 00:34:21 GMT
Initiating SYN Stealth Scan
Scanning 1 hosts [65535 ports/host]
Discovered open port 38213/tcp on 10.0.1.36
Discovered open port 34955/tcp on 10.0.1.36
Discovered open port 34093/tcp on 10.0.1.36
Discovered open port 43409/tcp on 10.0.1.36
Discovered open port 43553/tcp on 10.0.1.36
Discovered open port 46033/tcp on 10.0.1.36
Discovered open port 41409/tcp on 10.0.1.36
Discovered open port 44633/tcp on 10.0.1.36
Discovered open port 44323/tcp on 10.0.1.36
Discovered open port 41857/tcp on 10.0.1.36
Discovered open port 35721/tcp on 10.0.1.36
Confirmed with nmap
nmap -p- 10.0.1.36
Starting Nmap 7.95 ( https://nmap.org ) at 2024-06-04 20:39 EDT
Nmap scan report for sc6000m.localdomain (10.0.1.36)
Host is up (0.00063s latency).
Not shown: 65524 closed tcp ports (conn-refused)
PORT STATE SERVICE
34093/tcp open unknown
34955/tcp open unknown
35721/tcp open unknown
38213/tcp open unknown
41409/tcp open unknown
41857/tcp open unknown
43409/tcp open unknown
43553/tcp open unknown
44323/tcp open pmwebapi
44633/tcp open unknown
46033/tcp open unknown
How are the devices connected together ? Do you see link lights on the router/switch ports when devices are powered up ?
OK… KINDA SOLVED… But really strange behaviour. If I power up the mixer, then wait for it to boot up completely, then power up the SC6000’s. It will be stuck with the with the APIPA IP address… 169.254.180.18
If I power up the SC6000’s, wait for them to have booted up completely, then power on the x1850… Again, I’m stuck with the APIPA IP address 169.254.180.18
HOWEVER…
If I hit all three power buttons, x1850 & the two SC6000’s at pretty much the same time. I’ll get a correctly DHCP assigned IP addres such as (in my case) 10.10.10.118
So basically turn everything on at as close to the the same time as each other as possible…
So frustrating, but I think this seems to have fixed the problem.
This is not normal behavior, but if you regard it as a fix for now, that’s okay of course. 
Ya I figured as much, but it’s a repeatable solution. Really strange, but I’ll stick with it for now. I have a new router on the way that I intend on trying that might see the issue disappear entirely, but who knows… 
Agreed. Perhaps it is solved then.
The DHCP scope on the router isn’t full by any chance?