NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
MS510TX, can't manage because "not in the same subnet"
Just received my MS510TX.
Using win10 x64, FW is 6.7.0.50 (can't update)
so, SWITCH DISCOVERY finds the Switch, but pressing "admin page" gives me a timed-out connection error.
SmartControlCenter also finds it, but when I press "web browser access", same timed-out error.
"DHCP refresh" give "Could not refresh the selected task using DHCP"
When going to the "MAINTENANCE" tab, you can see in the bottom "Warning: Commands may fail because SmartControlCenter and device are not in the same subnet. Recommend changing device 192.168.0.239 or this SmartControlCenter workstation to the same subnet. SmartControlCenter has IP: 192.168.1.69 Gateway: 192.168.1.1 Subnetmask: 255.255.255.0", and there is also this message "Alert: This device IP is in a different subnet. Cancel or Continue the action".
Not sure what to do here as I am not familiar with subnet masks, gateway...
the Switch in the only device connected to my Zyxel AX7501-B0 router.
I also have a ASUS XT8 Mesh (2 nodes) connected to the MS510TX.
I hope someone can help!
Cheers to all.
One would expect the MS510TX would be able to receive a DHCP assigned IP address, e.g. from your ASUS XT8 Mesh primary node if it's in router mode. Ensure the MS510TX MAC address is added to any security on this router, so it can get access to the network like any other wired or wireless device.
The alternate approach would be to temporarily configure a computer into that other 192.168.0.x/24 network, like 192.168.0.123, MAsk 255.255.255.0, default gateway and DNS 192.168.0.1 (regardless if it exists, and override any kind of connectivity tests. Now you can ping the switch on 192.168.0.239, access the management Web interface using a Web browser, set a fixed IP (not overlapping, ideally outside of the routers DHCP pool) in your LAN subnet (like 192.168.1.123, mask 255.255.255.0, gateway 192.168.1.1, DNS 192.168.1.1). From here ou should be able to reach the switch from your nomal LAN/WLAN network (driven by the Asus router!). Everything under the assumption the Asus does isue 192.168.1.x addresses of course.
24 Replies
One would expect the MS510TX would be able to receive a DHCP assigned IP address, e.g. from your ASUS XT8 Mesh primary node if it's in router mode. Ensure the MS510TX MAC address is added to any security on this router, so it can get access to the network like any other wired or wireless device.
The alternate approach would be to temporarily configure a computer into that other 192.168.0.x/24 network, like 192.168.0.123, MAsk 255.255.255.0, default gateway and DNS 192.168.0.1 (regardless if it exists, and override any kind of connectivity tests. Now you can ping the switch on 192.168.0.239, access the management Web interface using a Web browser, set a fixed IP (not overlapping, ideally outside of the routers DHCP pool) in your LAN subnet (like 192.168.1.123, mask 255.255.255.0, gateway 192.168.1.1, DNS 192.168.1.1). From here ou should be able to reach the switch from your nomal LAN/WLAN network (driven by the Asus router!). Everything under the assumption the Asus does isue 192.168.1.x addresses of course.
Thanks,
I actually didn't notice the ASUS XT8 was in router mode. As I already have a router (the Zyxel), I have now switched the XT8 to Acces Point Mode, which seems more appropriate.
I will try your solution this weekend, as I have to make sure it works on Monday.
In the meantime, please find attached a map of my network, I guess that should help.
Ok, appears you have the ZyXEL CPE connected direct to the switch - permitting the port you connected the switch to isn't a special function of feature port like for IPTV - one would assume the switch can get an IP address assigned from the ZyXEL DHCP.
The XT8 wireless system should not have an impact in this set-up, permitting in router mode it's LAN does not use the same IP subnet (what would cause several other issues). AP mode is certainly the way to go.
So the switch receives an IP from the DHCP server but it cannot be accessed by a PC in the local network unless he assigns a static IP to the PC, Can we check if they are on the same subnet? Can you ping the switch? What are the IP address of the PC and the switch? Have you tried assigning a static IP on the switch and see if that will resolve the issue?
schumaku Thanks for reaching out. But I just have the same idea of a workaround as yours by which he hasn't tried yet.
Regards,
John
NETGEAR Community Team
Thanks JohnC_V ,
The Switch and the PC are not on the same Subnet, that was the error message given by Smart Control Center from the beginning.
I can't ping the Switch, it gives me a "request timed-out".
IP of the PC is: 192.168.1.1
IP of the Switch is: 192.168.0.239
I haven't tried to assign a static IP on the Switch (my knowledge is limited and I wouldn't know which IP to use).
Please note that I have been able to connect to the Switch web management page after changing my PC IP, but then internet goes on and off (mostly off), so I had to use DHCP again to make it work.
It seems that the switch is still on its default IP that is why you needed to assign the IP address of your PC in order for you to connect to the admin page. I suggest setting the switch to a static IP like 192.168.1.200, 255.255.255.0 so that it will be on the same IP subnet with your PC. Just make sure that the IP that you are going to assign to the switch does not conflict with any other devices on your network.
Regards,
John
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
