DHCP-LAN ok, WAN not working, Static, LAN/WAN both OK

[jj14]

Hello,
I have an ethernet based network at home - multiple PCs (XP-SP2 & Vista Ultimate based) - CAT5E cabling throughout - DHCP served by linksys BEFWS114 - using a Dell Powerconnect Unmanaged switch for different rooms. Wireless is disabled on the BEFWS114.
The setup has been working fine (all devices on same subnet) - n/w printer & NAS had static IPs while the PCs had dynamic IP (DHCP enabled) - everything was working fine for over a couple of years without any problems. Out of the blue, last week, the PCs just wouldn't connect to the internet, but could access the other devices on the LAN ok. Tried to restart the PC, release and renew the IP, no problems there, but the PC just wouldn't access the internet. I forced it to a static IP and it worked fine! I have no idea what caused this - this is the same case with ALL pcs - two laptops (Dell Inspiron/Latitude), one Dell desktop, two custom built PCs (ASUS P5WDH-E6600-4GB, MSI-NEO2PLS-P4Prescott2.8GHz-2GB), so I don't think it is related to a PC setting.
I then tried to disable the DHCP on the linksys and then connect a Netgear WGT624 to the Dell switch and enabled DHCP on it - same results.
Any idea as to what the problem might be?
Thanks

 

[DrGreen2007]

Whats the IPCONFIG /ALL from a machine when its set for DHCP
Compare that to IPCONFIG /ALL from a machine you set statis....whats different?

 

[Goosemaster]

Originally posted by: DrGreen2007
Whats the IPCONFIG /ALL from a machine when its set for DHCP
Compare that to IPCONFIG /ALL from a machine you set statis....whats different?

Aye.

Might be DNS or subnet related.

run this on every machine in the command prompt

ipconfig /flushdns

then run

ipconfig /release all

tell us what happens...

 

[jj14]

DrGreen2007,
That should have been the first thing to check, yet, I didn't! Yikes! The default gateway is showing up different. Let me explain.
The linksys has always been the DHCP server and its IP was 192.168.1.1 (Static)
The netgear (I use it only for wireless access) always had it's DHCP set to OFF and it's IP was set to 192.168.1.5 (static)

When I go with a static IP, I get the default gateway of 192.168.1.1 (the linksys's IP)
But when I go with DHCP, I get the default gateway of 192.168.1.5 (the netgear's IP)

So, I guess the question would be "Why does my default gateway change to 192.168.1.5 (wireless AP's IP) when I choose to go DHCP?"

Goosemaster,
the flushdns worked ok - "Successfully flushed the DNS Resolver Cache."
but the RELEASE ALL responded - "The operation failed as no adapter is in the state permissible for this operation."

Thanks again for your help and valuable input.

 

[DrGreen2007]

Whatever is giving out your DHCP is giving out the gateway, so youll need to change that.

 

[kevnich2]

Ok, a few things here. Why on earth do you have TWO routers? Pull out the linksys one, it's a pretty old router so it's probably just time to get a new one. Second, it sounds like the netgear's DHCP is still turned on if when you go to DHCP it's receiving the 192.168.1.5 as the gateway. Pull out the linksys completely and use the netgear as the main router. Reconfigure it's IP to 192.168.1.1, turn on DHCP (I think it's already on) and make sure the WAN is setup correctly. After that, reconfigure your computer's back to DHCP. If in the netgear, if the DHCP is set to off and the computer's are still receiving IP's from it, I'd say get a whole new router because the netgear is flaky too. I personally don't like linksys any more than netgear. Every netgear I've ever used has been flaky (a total of 7 so far from various people). If you do end up having to replace it, look into a buffalo WHR-HP-G54.

 

[jj14]

I originally had the linksys, but later decided to upgrade to 802.11G - that's why I ended up buying the netgear. I used it only as an AP (not as a router) - the linksys served as the router.

You are right about the netgear being kinda flaky (DHCP lease to client machines would expire during the day while the PC was in use - irrespective of the settings on the netgear) - that's why the linksys is still around as the DHCP provider.

I rechecked to verify that the netgear has the DHCP disabled (only the linksys has DHCP enabled), that's what's baffling me. I have a call in with netgear and linksys separately - the problem is that the moment they hear that I have both devices on the network, they start blaming the other device

I'm kinda regretting buying the DELL unmanaged switch - should have spent the extra money and gotten one of their good managed switches - could have gotten rid of this mess completely.

 

[jlazzaro]

Originally posted by: jj14
I'm kinda regretting buying the DELL unmanaged switch - should have spent the extra money and gotten one of their good managed switches - could have gotten rid of this mess completely.

a managed switch wouldnt have done anything for you but complicate things even further.

 

[JackMDS]

The Linksys BEFWS114 is an old "clunker" (was not so good even when it was new).

D-Link Devices is a mixed bag. Some Routers are OK, but some do behave strangely with DHCP leases.

The best is to get a Router that can do Static DHCP.

I.e. All network devices are getting the IP from the Router's DHCP server, but it can be configured to give always the same IP to the same PC.

All the Routers that can be flashed with DD-WRT would do after Flashing Static DHCP.

Buffalo, SMC, and some others would do Static IP within the DHCP as is.