Network logon failure, false ip and no logon script.

[m3gatl20n]

Hey all, I am an intern for my company and Im trying to get some research for a problem we been having, we have about 200 users, and every morning we tend to get 3-4 people that cant log on to network or get email off our exchange server. Usally we can resolve it fast all it usally takes is a reboot or a ipconfig release/renew. It seems to be giving a bogus ip and no logon script, its 1 exchage server and 2 others all windows 2003 any ideas or suggestions thanks.

 

[Serbtastic]

When they can't log onto the network, what IP address are they assigned? If its in the 169.254.x.y range, then your client machines are not able to reach the DHCP server to get a valid IP address, and this is why they cannot log onto the network nor connect to the Exchange server.

Try a static IP on these clients instead.

 

[m3gatl20n]

I think they are in the 198.200.x.y range...I dont think its in that range. It just doesnt seem to pick up its ip right away, I dont know if its due to the fact that so many people are all logging in at the same time in the morning that it causes a problem...

 

[m3gatl20n]

192.168.x.y was the ip.

 

[noobtechie]

Did someone plugged a wireless router in one of the jacks? It might be getting an ip address through that router even if it's plugged in to the uplink port. Cheap routers do that. If it's DHCP enabled then you know it's getting that address from somewhere.

============================
Hope this helps.

 

[m3gatl20n]

No I dont think so, about the wireless router...And yea its DHCP, it just doesnt make sense that if u just reboot it usally does the trick, just annoying cause no one will try that first before they call us, but hey thats the job.

 

[noobtechie]

Try to download an Ipscanner from

http://www.angryziber.com/ipscan/

and do a scan of your network.
Look for that odd ip address and check the host name to see if rings a bell, go from there...

============================
Hope this helps.

 

[Serbtastic]

Did you check the event logs for IP conflict errors?