• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DHCP server unreachable ???????

D

Doomer

Diamond Member
I'm trying to configure my new Netgear ME 103 Wireless access point and it's saying that the DHCP server is unreachable. Funny thing is, my laptop connected via the AP can get an IP from the DHCP server just fine. The AP is defaulting to 192.168.0.224 which makes it a PITA to configure since I have to change the IP to 192.168.0.xxx on one of my computers in order to reach the AP. If it did get an IP from the DHCP server it would be somethoing like 192.168.1.xxx. Hope this makes sense.

Anybody have any idea why the DHCP server is unreachable to the AP
 
What is your DHCP server? Usually your router is what provides DHCP services. If the router is giving that message, it probably is trying to pull an IP address from your ISP and is having trouble for some reason.

 
My Westell DSL moddem is my DHCP server. It's at 192.168.1.254. The laptop picks up the IP, default gateway, dns server, etc. from it without any problems so I don't understand why it's unreachable by the AP. Thanks
 
OK, I manually assigned an IP that puts it where it needs to be and all appears well but I still don't understand why or how it defaults to a subnet of 192.169.0 and thus won't see a DHCP server on subnet 192.168.1. I see no way to set a subnet. Can anyone shed any light on this. I'd really like to know. Thanks
 
Originally posted by: Doomer
OK, I manually assigned an IP that puts it where it needs to be and all appears well but I still don't understand why or how it defaults to a subnet of 192.169.0 and thus won't see a DHCP server on subnet 192.168.1. I see no way to set a subnet. Can anyone shed any light on this. I'd really like to know. Thanks
Click to expand...
  • How did some of your computers get IPs on the 192.168.1.xxx subnet?
  • If you want to use 192.168.1.xxx, why don't you move the AP over there too?
  • How many DHCP servers do you have active?
  • Your subnet mask is (most likely) set to 255.255.255.0. In your head (or on paper) change that to BINARY - 11111111.11111111.11111111.00000000. Wherever you see a '1', the address is "fixed" (i.e. 192.168.0.xxx or 192.168.1.xxx); Wherever you see a '0', anything can go in there. So, if you want to use TWO subnets on your LAN, you need to change the subnet mask ON EVERY MACHINE to 11111111.11111111.11111110.00000000, which will allow '0' *OR* '1' in the third octet.
Clear?

 
Clear as mud. 😀

OK, All the computers on the network have a 255.255.255.0 subnet mask as does the AP. All the computer are able to get an IP from the DHCP server. The AP is not. It defaults to 192.168.0.224. It says the DHCP server is unreachable. I wasn't able to reach the AP with it set to this IP from any of the computers. When I changed the IP from 192.168.0.224 to 192.168.1.224 all was well and I'm now able to reach it from any computer.

With my limited knowledge, the question I have is how do I change the default subnet from 192.168.0 to 192.168.1 ? If I manually assign an IP then obviously it's not using the DHCP server. I don't know if this is a good thing or a bad thing but I do know that by manually assigning an IP I'll always know where it's at. My only concern is that this might cause other problems down the road.

Thanks for the help.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top