NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
EX3700-100PES can't connect through a switch
Hi!
I'm trying to set up an EX3700 attached in AP mode to a Netis ST3105G Unmanaged Gigabit switch, and got stuck hard.
The Power LED is green, the Device LED is green, there's a NETGEAR_EXT netw...
coldbear wrote:
The router is at 192.170.1.2 and assigns IP addresses with DHCP in the 192.170.1.100-150 range.
This is an unusual choice, since 192.170.1.x are routable internet addresses (and these addresses happen to be assigned to Hewlett-Packard).
I suggest reconfiguring the router to stay within the address ranges that are reserved for private use (and which are not routable over the internet).
- 10.0.0.0 – 10.255.255.255
- 172.16.0.0 – 172.31.255.255
- 192.168.0.0 – 192.168.255.255
coldbear wrote:
Any other device connected to the switch works, in that it gets a proper IP address and can promptly access the Internet. The EX3700, however, doesn't. Factory reset didn't help. Anything else I could try? Should this kind of setup even work?
Thanks!
This should work. One thing you could try is setting up the EX3700 as an extender first.
You could also
- try a different switch
- try configuring the PC (temporarily) to use a 192.168.1.x address. Then try 192.168.1.250 again.
Thanks for your assistance, StephenB.
Long story short, I changed the router's IP to 192.168.1.2 (to avoid an address conflict with other devices that default to .1). Disconnected all cables running to the switch except for one that connects it to the router. Through trial and error, got so far as to actually configure the extender and its _2GEXT and _5GEXT networks. Reconnected the TV (STB) and boom, _2GEXT went kaput and never recovered (looks like all the routes were dead even though it had a correct IP and GW in the correct subnet). Disconnected TV, connected PC to _5GEXT, all good, reconnected TV, and everything still kept working. Whew...
So, apparently it was the STB that borked the connection (how and why, I can't tell. Maybe the fact that the STB expects a 10.247.126.x IP is a factor, but I'm not sure about that.). In any case, as a precaution I'm going to run a separate cat5 to the STB in the future .
So far, so good.