Windows 2000 Static IP problem.

[Kaervak]

When I disable my DHCP server on my router my Win2k machine's internet dies. It's setup for static IP, yet completely dies if the DHCP is disabled. My XP laptop doesn't do this, neither does my aunt's Win98 machine. I have no idea why it does this. As long as the DHCP server on my D-Link DI-614+ is enabled, it's perfectly fine. The two previously mentioned systems are perfectly fine with the DHCP server being disabled. When I check the DHCP table, my system shows up. No host name, just the MAC address, and IP expire time. Any idea how to correct this or what's even causing it?

 

[Oaf357]

Hmm... quite the predicament.

First, is the Windows DHCP client enabled?
Double check your Network settings.

 

[DnetMHZ]

On the systems with static IPs did you enter the DNS servers and the correct default gateway?

 

[Kaervak]

Originally posted by: Oaf357
Hmm... quite the predicament.

First, is the Windows DHCP client enabled?
Double check your Network settings.

Everything relating to DHCP is good to go on all systems. One of the strangest problems I've ever come across, aside from the one I had a few days ago. Using DHCP on my system is no big deal, just having a static IP and disabling DHCP entirely would be a nice little added security measurement.

 

[Kaervak]

Originally posted by: dnetmhz
On the systems with static IPs did you enter the DNS servers and the correct default gateway?

Yep. Everything matches on all three systems. Cept on this one, DHCP disabled = dead internet.

 

[maxis]

do you try to use ipconfig /all to view your win2k's ip configuration? (before & after u disable the dhcp)
also try o use tracert.exe to help troubleshoot

 

[Kaervak]

Originally posted by: maxis
do you try to use ipconfig /all to view your win2k's ip configuration? (before & after u disable the dhcp)
also try o use tracert.exe to help troubleshoot

Yep used IPCONFIG. Everything showed as normal. I'm about 99% sure it's 2k being goofy. I know a reinstall will take care of it, but it's such a minor thing, I'm not gonna reformat for it. Thanks for all the suggestions & advice everyone .

 

[Scarpozzi]

I know you checked ipconfig, but you may wanna check that again. What happens with DHCP most of the time is you get a lease of like 3 days from the DHCP server... Some clients try to keep the address because it's cached in TCP/IP settings (this is really bad on Macs and you have to trash TCP/IP Preferences to clear it up). For Windows 2000, you can always try doing the same and remove TCP/IP completely and doing a reboot. First though, I'd try going to a command prompt and typing "ipconfig /release", then do "ipconfig /all" This should display the static ip as before, but the release command should clear out any bad settings you may have.

Also, just in case...make sure you have the right subnet and gateway settings. DHCP auto-populates these.

 

[Kaervak]

Originally posted by: Scarpozzi
I know you checked ipconfig, but you may wanna check that again. What happens with DHCP most of the time is you get a lease of like 3 days from the DHCP server... Some clients try to keep the address because it's cached in TCP/IP settings (this is really bad on Macs and you have to trash TCP/IP Preferences to clear it up). For Windows 2000, you can always try doing the same and remove TCP/IP completely and doing a reboot. First though, I'd try going to a command prompt and typing "ipconfig /release", then do "ipconfig /all" This should display the static ip as before, but the release command should clear out any bad settings you may have.

Also, just in case...make sure you have the right subnet and gateway settings. DHCP auto-populates these.

Tried all of that, no dice. Static still dies with my DHCP server disabled. Oh well, no big deal.

 

[lobadobadingdong]

looks to me like your dhcp server on your router is giving out an address to the win2k box that has already been claimed by one of you static boxes. If at any point in time in your os's life you disabled alerts on dhcp errors it can be easily overlooked and can be a major pain in the @ss. I'd suggest going through each machine and remove and restore your tcp/ip bindings (with a restart inbetween to clear the ip stack) and try again with the dhcp server disabled. And make darn sure they have the same subnet and different ip's of the same class address as the router when re-configuring your bindings. You might also try resetting your router to defaults and loading your login info again, to make sure the router didn't get a flaky bug of some kind.