NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
gregarican
Oct 29, 2021Aspirant
Netgear M4300 Loses SSH and Web Admin connectivity
Ran across this post from a few years ago --> https://community.netgear.com/t5/Managed-Switches/M4300-12X12F-XSM4324S-needs-reboot-to-access-admin-interface/m-p/1772350. Same situation. I need to enable a SPAN port on the switch for a intrusion detection appliance we are testing out. But I cannot access the Netgear M4300 via the web admin, via SSH, or even ping it.
Really not looking forward to having to reboot a core network production switch just so I can access the admin stuff. If I connect to the switch via a console serial cable then I suppose I can define the SPAN port in there. Pretty clunky for something that's part of our core networking envrionment...
I figured out a workaround. Connected to the console CLI issuing a command of ip management vlan 1 dhcp puts the switch back on the network where it can be managed. Without having to reboot it. For some reason the switch loses its DHCP assigned network config and defaults back to what it was out of the box.
2 Replies
- Olivier421Aspirant
hello
the only situation when i have this is when there is a loop in the network.
it's not doing it on my m4300 though (or maybe i did not wait long enough to see it happening), but to older gen switches (like GS7xx or S33x) it was doing it in seconds.
when this happens, you also can't get local access via console port ?
If Netgear support never saw that before in years, and you keep having it over multiple firmwares, and over multiple stacks, to me , it means either:
- you really have back luck and have purchased a series of bad 'hardware' in same time, all having same fault.
- I believe serial numbers do have a meaning in terms of construction batch, or years, or similar stuff . Trying with another would clear this point.
- something related to your environment : such as a loop
- gregaricanAspirant
I figured out a workaround. Connected to the console CLI issuing a command of ip management vlan 1 dhcp puts the switch back on the network where it can be managed. Without having to reboot it. For some reason the switch loses its DHCP assigned network config and defaults back to what it was out of the box.
- you really have back luck and have purchased a series of bad 'hardware' in same time, all having same fault.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!