F5F Stay Refreshed Hardware Desktop Failed to connect to NAS following router installation.

Failed to connect to NAS following router installation.

Failed to connect to NAS following router installation.

I
IFoskuruR3KT
Member
62
01-14-2025, 12:46 AM
#1
I've been relying on the Zyxel NAS326 for many years. The internet service changed the router to a newer model, and now I can't connect. It looks like DHCP isn't assigning an IP address, yet the admin panel shows packets being sent and received on the port my NAS uses. The green LED near the LAN port isn't lighting up. Could this indicate a hardware problem with my NAS?
I
IFoskuruR3KT
01-14-2025, 12:46 AM #1

I've been relying on the Zyxel NAS326 for many years. The internet service changed the router to a newer model, and now I can't connect. It looks like DHCP isn't assigning an IP address, yet the admin panel shows packets being sent and received on the port my NAS uses. The green LED near the LAN port isn't lighting up. Could this indicate a hardware problem with my NAS?

U
UnversedCake
Junior Member
39
01-15-2025, 07:02 PM
#2
This sounds like you may just wanna reapply a static ip that is not the same. Highly doubt it's a hardware issue sounds like stupid dhcp
U
UnversedCake
01-15-2025, 07:02 PM #2

This sounds like you may just wanna reapply a static ip that is not the same. Highly doubt it's a hardware issue sounds like stupid dhcp

Z
zamys
Senior Member
690
01-22-2025, 10:42 AM
#3
appears to be static with a fresh router setup. switch the IP from your previous range into the network card using the config. test connectivity by pinging each address and verify responses. if access works, log into your browser, enable DHCP, or assign a fixed IP in the new subnet.
Z
zamys
01-22-2025, 10:42 AM #3

appears to be static with a fresh router setup. switch the IP from your previous range into the network card using the config. test connectivity by pinging each address and verify responses. if access works, log into your browser, enable DHCP, or assign a fixed IP in the new subnet.

X
xJuliaKay
Junior Member
21
01-25-2025, 02:40 PM
#4
It worked once we switched back to the original subnet. Appreciate the fix!
X
xJuliaKay
01-25-2025, 02:40 PM #4

It worked once we switched back to the original subnet. Appreciate the fix!