NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS724TV6 - Refuses to get DHCP address non 192.168.0.x address
I have two GS724TV6 that I want to configure and set up on my network. The network is a Verizon FIOS router that serves as DHCP to a Netgear GS724TV4. I also have a few 8 port Netgear switches on the network (GS108EV4) and a GS316EPP. All of these get DHCP addresses perfectly fine.
- Neither get DHCP addresses
- They take the default address of 192.168.0.239
- I was able to configure a PC as 192.168.0.1 and connect to them
- I assured that they were both configured as DHCP
- When I configured one to 192.168.1.30 with a gateway of 192.168.1.1 (the Verizon Router) it would be seen when I plugged it into the network.
- I set up it's MAC address in the router to assign it 192.168.1.30, the router never assigned the address
- I upgraded the firmware to 7.0.0.14 from 7.0.0.12, no change
- The Network Discovery Tool doesn't see the device on either the 192.168.0.x or 192.168.1.x configurations
How to I get it do get a DHCP address from my regular network like all of the other 40 devices seem to be able to do?
8 Replies
In my test configuration I used ONE switch to ONE PC.
The switch was reset to default (several times).
When reset to default:
PC-------------> Switch
192.168.0.1 defaults to 192.168.0.239
- Can connect with HTTP
- Network discovery tool will NOT see the switch
If I change the switch and PC to a .1. address, nothing.
PC----------->Switch
192.168.1.1 explicitly set to 192.168.1.239
- Can no longer connect with HTTP
- Network discovery tool will NOT see the switch.
I'm at a loss to understand this.
I updated one switch to <mumble>.12 - the most recent firmware, no change.
I'm at a loss to understand this
I'm fully with you.
Time to open a support ticket with Netgear via HTTPS://my.netgear.com/
Afraid, I don't own any GS724Tv6 nor a bigger GS748Tv6, so completely lack of personal experience.
Something must be really wrong with your switches.
Regards,
-Kurt
In case you have ressources for redoing the factory reset - once you have Web UI access again, before setting the manual IP config, ensure
- Management VLAN is set to 1
- All ports are configured as access ports [U]ntagged (only), and
- All ports PVID is set to 1
This would be about the usual default config on these Smart Managed switches.
If you use VLANs, then double-check that they are all configured correctly.
I had a similar issue with a GS708v3. It turned out I had accidently misconfigured a VLAN port on another switch, which ended up putting VLAN 1 traffic on two trunks going into the GS708v3. That didn't result in a flood (not completely sure what prevented it), but it did result in the switch not getting a DHCP address.
see my note below - reset the switch to default. It works with a switch to PC when PC is configured to 192.168.0.1. If I change the switch and PC to explicitly be 192.168.1.1 and switch to 192.168.1.239 I can't event connect with HTTP. Network discovery tool doesn't work with either config.
All your newer explanations make perfect sense.
On a pure experimental approach, with the switch configured with the DHCP client active, I would check if the switch does not broadcast the DHCP discovery request on all ports - before it does fall-back to the 192.168.0.239/24 default config.
Also worth a try? Factory reset using the reset button - press and hold for some 3..5 seconds till the switch dies restart.
Definitely a case for NETGEAR customer service, especially because it appears the two switches are almost factory new.
Something is very fishy. A serial production issue for example.
Regards,
-Kurt
In the subject, you say "Refuse" - are the DHCP requests ever reach your LAN, and the Verizon FIOS router LAN and it's DHCP server, and you have some indications from that DHCP server that is has assigned the intended IP address?
They take the default address of 192.168.0.239
This is the Netgear default IP address config if the DHCP client does not recieve an anser on the LAN.
When I configured one to 192.168.1.30 with a gateway of 192.168.1.1 (the Verizon Router) it would be seen when I plugged it into the network.
Permitting the GS724Tv6 management VLAN (default VLAN 1, ...) is really connected to your LAN - yes, of course.
- I was able to configure a PC as 192.168.0.1 and connect to them
When doing so, this PC was connected to the LAN, or had used a temporary direct link to the GS724Tv6?
Based on your problem description, I guess that was a direct connection...How and where are your two new GS724Tv6 connected to? Thats the point you should start investigating...
The Network Discovery Tool doesn't see the device on either the 192.168.0.x or 192.168.1.x configurations
The NETGEAR Discovery Tool can make use of NSDP (NETGEAR Switch Discovery Protocol) and UPnP (Universal Plug and Play SSDP protocol) to discover NETGEAR devices.
In combination with these recent switches - NDT depends on a working network connection, the switch and the PC need IP configuration in the same subnet - its pure SSDP.
The legacy NSDP - able to discover any device on a transparent layer 2 network - is unlikely implemented
Your other GS108Ev4, and GS316EPP switches are supporting also NSDP, unless the admin has explicitly disabled the NSDP discovery function.
see my note below - reset the switch to default. It works with a switch to PC when PC is configured to 192.168.0.1. If I change the switch and PC to explicitly be 192.168.1.1 and switch to 192.168.1.239 I can't event connect with HTTP. Network discovery tool doesn't work with either config.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
