NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS108Ev3 refuses to connect
I have 4 GS108Ev3 switches. As they are all configured and working well I don't need to administer them often.
Today I wanted to login to them - and can't.
All 4 refuse to connect when I access the admin screen (http://192.168.0.XXX).
I can ping them all.
Netgear Discovery Tool v2.0.7 finds them all, shows the firmware is v2.06.24 but when I click Admin Page, a new tab opens followed by:
This site can’t be reached
192.168.0.231 refused to connect.
Try:
- Checking the connection
- Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
When I try the ProSafe Discovery Tool and ProSafe Plus Utility v2.7.8, they also discover the switches but report that the admin feature is disabled on the switches.
I have factory reset the switches. They pick up an IP address from the DHCP server after the reset, and respond to pings but still refuse admin web connection.
I've seen some threads about MTU length required to be 1500 and it is. I tried changing that - it didn't work so I changed it back and it still didn't work!
This is on a flat network (no VLANs etc), from Windows 11 and Chrome. I have a lot of web-managed devices that all work but these switches don't and I can't figure out why!
How do I get access to the admin screen for these switches, please?
5 Replies
I've seen some threads about MTU length required to be 1500 and it is. I tried changing that - it didn't work so I changed it back and it still didn't work!
Double check - from PowerShell run:
netsh interface ipv4 show subinterfaces
Example:PS C:\Users\kurts> netsh interface ipv4 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
---------- --------------- ------------ ------------ -------------
4294967295 1 0 14450590 Loopback Pseudo-Interface 1
1500 1 891408824 94922849 WiFi
1500 2 190977316 74523312 Ethernet
1500 5 0 0 Ethernet 2
1500 5 0 0 Local Area Connection* 1
1500 5 0 0 Local Area Connection* 2
1500 5 0 0 Bluetooth Network Connection
The reson for this behaviour: This simple IP stack does not support any PMTUD (Path MTU Discovery) .
When I try the ProSafe Discovery Tool and ProSafe Plus Utility v2.7.8, they also discover the switches but report that the admin feature is disabled on the switches.
Indeed: Following a factory reset, NSDP Configuration functions are disabled by default for security reasons.
This applies to the legacy tools only, because they are using the NSDP (Netgear Switch Discovery Protocol).
And: The current NDT (Netgear Discovery Tool) might discover switches like your GS108Ev3 (and earlier), or GS308E (very similar to your GS108Ev3) - due to lack of ressources (DRAM, Flash, ...) the modern UPnP SSDP can't be implemented on these very small switches, only by using NSDP.
I did that - and have done it again. The one labelled Main Ethernet is the LAN used for this.
C:\>netsh interface ipv4 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
---------- --------------- ------------ ------------ -------------
4294967295 1 0 103549 Loopback Pseudo-Interface 1
1280 1 336594023 34626830 Tailscale
1500 5 0 0 WiFi
1500 5 0 0 Local Area Connection* 9
1500 5 0 0 Local Area Connection* 10
1500 1 3243206781 2037463622 Main Ethernet
1500 5 0 0 Bluetooth Network Connection
1500 1 41662522 312358 MGMT Ethernet
Thanks for clarifying why the admin capability is disabled.
This site can’t be reached
192.168.0.231 refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSEDYour home LAN is really on the 192.168.0.x/24 IP subnet?
What does
ipconfigshow on your computer?
Yes - my LAN is 192.168.0.X - that has not changed in years.
I read all about the default 192.168.0.239 address related to these switches so I moved the device that was on that address elsewhere to free it up, just in case.Ethernet adapter Main Ethernet:
Connection-specific DNS Suffix . : **redacted**
IPv4 Address. . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
Because these devices respond to ping (and I know it is them and not some spurious device because they stop when I cut their power), it seems clear to me that the subnet and address issues are not the problem. Why these devices refuse browser connections is what confuses me.
OK, I have figured out what is causing it and can work around it - but don't understand why yet!
This PC rune Tailscale. When that is enabled then I can't access those admin pages despite them being on the same LAN and main switch. When I exit Tailscale, I can.
I can live with this and will try to figure out what is causing it!
Even with that, one provided the admin login screen but did nothing when a password was entered. I had to factory reset it, after removing it's reserved DHCP lease so it assumed a new IP address. Only then would it properly factory reset and allow login and administration.
At least they are working but clearly I need to delve deeper into what is happening!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
