This morning my home network seemed to be going a little slow / playing up. I didn’t too much of it and just assumed that the internet connection was running slow.
A few hours later and I am no longer able to access HA or my Synology NAS. Using the network tool Fing I see that HA is ‘seen’ but not given an IP address even though I have one assigned in the Ubiquiti EdgeRouter based on it’s MAC, similarly for the NAS although Fing isn’t even seeing the NAS.
I plugged a monito and kyboard into the HA server (Intel NUC) and see that it’s running fine but doesn’t have an IP address.
I’ve tried power cycling everything but for some reason the HA server and NAS won’t join the network.
I’ve never had this issue before and the network has been running flawlessly for years. It’s really strange that HA and the NAS are basically the only things not connected, with over 50 other devices happily running on the network.
Nope. The address’s are available. I have my DHCP range outside of anything statically assigned, which is really only for guest devices since all my devices have static assignments.
I just tried rebooting the Host again and watched for anything on the attached monitor, got the following error:
[192.002845] CIFS: VFS: Error connecting to socket. Aborting operation
HA otherwise appears to be running. The info command says so. The logs are mainly errors due to connectivity as expected
HA is definitely running ok as any automations that do not require network access are still working. ie: zwave controlled lights based on zwave motion detectors. Other than that, most things require a connection to a wifi device so my WAF is going to be zero tonight if I can’t get this sorted ASAP
Is there a rogue DHCP server on the network?
Edgerouter showing anyting in the logs or given that address elsewhere?
Are you using another NIC port on the HA box?
Any changes on your network? - VLANS, Firewall changes on the LAN interface?
Is the NAS and HA box using the same switch?
Hardware fault? Flashing lights on the back
POE turned on, on that port.
Not in network does not necessarily mean no ip, it can mean that it’s not in the same subnet. Have you tried a direct etnernet connection with a crossover cable? Something like wire shark or all my lan might also provide some insight.
So after lots of different tests last night I finally found the culprit and it was a very strange one… I worked out that the devices not getting IP address’s (despite having fixed ones allocated in the router) were all my wired ethernet devices, all of them.
So then I started thinking that my switch was the issue and dug out an old smaller one that would have enough ports to get me by for a few days. In doing so I left a few devices unplugged which let me to the cause of the problem the whole time - a smart TV. Once that TV was plugged in, the entire wired network would fail as well as any wifi devices that hadn’t already been assigned an IP address (ie: trying to connect my phone after having it disconnected). I power cycled the smart TV and everything started working perfectly again.
