Hey everybody, this is my first post to the forums, so please forgive me if I leave out something...
We've had this problem with our Win2K clients who have the Firewall client installed. When they reboot, their IP address is 0.0.0.0. That happens only if the cord is connected. If I wait until the login screen is up, and then connect the ethernet cord, everything is fine. They get their IP, and everything works. Until the next time they reboot.
I've learned a few things playing with one of the affected PCs. First, if I set it to a static IP (specify in IP properties on client), it will reboot fine, and everything works. If I have it obtain, that's where problems come in. Also, Preparing Network Connections takes ~5 Minutes. Also, it is every Windows 2000 machine, without exception, that has the Firewall Client installed. Machines set to use a proxy are fine (all our servers).
No drive imaging at all. Just the standard pop in the Windows 2000 CD and away I go.
Repair under Add/Remove Programs has no effect. Disabling/Enabling Network Connection has no effect. I've waited about 10-15 minutes for the /renew to time out. Still waiting.
Exactly how would I determine if my DHCP server IS working correctly. I know that all the clients (2 XP, 7-8 2000, 7-8 Win98/Me) get their IPs fine and renew when they expire just fine. Is there some kind of test I can run?
FYI: Just installed Firewall Client on a fresh 2000 machine and it's been sitting at Preparing Network Connections for the last 20 minutes.