DHCP client loosing connectivity to the network
I have 1 DHCP client who looses connectivity to the network around 1 to 2 times per week. All it takes is a IPCONFIG/release /renew to fix the problem. But, then it happens again in a few days.
This user is the ONLY one who has this problem. The DHCP server is a 2000 server domain controller.
Here's the scenario that I saw today when it happened:
User informs me that she suddenly can not get to any websites or the server's shared files. I look at the DHCP server and see her listed with an IP 192.168.1.125. The IP does not reply to pings; times out. User verifies that is the IP the machine has. The IP is leased until 2-28-05 @ 7:47:01AM (current date/time: 2-24-05 2:15PM). I have the user release/renew IP and then refresh the DHCP server to find her listed with the SAME ip address, but now it's leased until 2-28-05 @ 2:17:54PM. She is back online again.
The DHCP server leases addresses for 4 days. I'm not sure if there's a pattern of when this occurs, as it's only occured around 4 times and I didn't take note of the date.
This user is the ONLY one who has this problem. The DHCP server is a 2000 server domain controller.
Here's the scenario that I saw today when it happened:
User informs me that she suddenly can not get to any websites or the server's shared files. I look at the DHCP server and see her listed with an IP 192.168.1.125. The IP does not reply to pings; times out. User verifies that is the IP the machine has. The IP is leased until 2-28-05 @ 7:47:01AM (current date/time: 2-24-05 2:15PM). I have the user release/renew IP and then refresh the DHCP server to find her listed with the SAME ip address, but now it's leased until 2-28-05 @ 2:17:54PM. She is back online again.
The DHCP server leases addresses for 4 days. I'm not sure if there's a pattern of when this occurs, as it's only occured around 4 times and I didn't take note of the date.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I can't think of a device that would be trying to use her IP. Plus, when she looses connectivity, I am not able to ping the IP she has. I can try to force her machine to stop using the 192.168.1.125 ip that she always has... I'll make and exception for that IP so its not handed out any more and see if that will help.
I'm not sure why the lease time is so short... It was setup that way when I came onboard and I just left it. We don't have many mobile users.
I've thought about the physical connectivity issue... It just doesn't seem right becasue it always starts working right after and IP release/renew (even though she still has an IP address configured that I have to release, and she always renews the same address). It just doesn't add up. I will try some other things before changing her physical network connection.
I'm not sure why the lease time is so short... It was setup that way when I came onboard and I just left it. We don't have many mobile users.
I've thought about the physical connectivity issue... It just doesn't seem right becasue it always starts working right after and IP release/renew (even though she still has an IP address configured that I have to release, and she always renews the same address). It just doesn't add up. I will try some other things before changing her physical network connection.
Another possibility is that there is a Netbios naming conflict...this would cause the OS to disable the interface. Next time it happens, run NBTSTAT -n, and see if any of the names show a conflict.
Make sure Time settings on her PC and the DHCP server are exactly the same.
Sometimes becuase of Time mis-configuration you could recieve these type of errors.
Check this site out for a correct use of net time. Could be your problem.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_time.mspx
Sometimes becuase of Time mis-configuration you could recieve these type of errors.
Check this site out for a correct use of net time. Could be your problem.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_time.mspx
ASKER
The machine just did this again today. This time, I added an exception on the IP lease range to remove the users IP from the range. She released/renewed and got a different IP now. I'll wait and see if this helps.
Didn't the Net Time help you out? you should have your whole LAN with the same timing...
ASKER
Well, the affected user hasn't lost connectivity in 7 days now, and it seemed to be happening every 5 days, so maybe not allowing her to get the .125 IP address anymore solved the issue. I'm going to wait a few more days and see if she does have any more issues with this.
I appreciate everyone help with this issue so far!
I appreciate everyone help with this issue so far!
You should periodcally do a "ping" for that .125 address to see if it's on the network somewhere. One possibility is that you may have a network printer (or similar network device) that uses IP in addition to its other protocols. You'll find that whenver that device is rebooted, it'll attempt to use its programmed IP address, and if that address is taken, it'll just not use the IP protocol (which you won't even notice if its also using somethign like NetBios, IPX or something like that). Now that .125 is free, that device may be up and active on your network.
ASKER
This issue just happened again. The user said it happened yesterday also, plus one more time since 3-8-05. The user remembered the command I had her type in to release/renew her IP and has been fixing it herself when it happens. Good for her, but not so good for troubleshooting the issue!
So, here's what I have narrowed down:
-It's not a IP conflict
-It's not a net time, as I synched up the PC with the DC and it's still happening.
-I haven't done a good job of tracking when it happens, but it does seem to be every 4 days (my DHCP lease time)
-There's no consistant events logged on the Domain controllers or the PC that coinside with when this happens.
I think I'm going to jack up the DHCP lease time and see what happens after that. Any other ideas??
So, here's what I have narrowed down:
-It's not a IP conflict
-It's not a net time, as I synched up the PC with the DC and it's still happening.
-I haven't done a good job of tracking when it happens, but it does seem to be every 4 days (my DHCP lease time)
-There's no consistant events logged on the Domain controllers or the PC that coinside with when this happens.
I think I'm going to jack up the DHCP lease time and see what happens after that. Any other ideas??
ASKER
This issue has not occurred again since I changed the DHCP lease time to a larger number of days. I'm giving RWrigley the points, as his suggestion about the lease time helped me narrow down the issue.
I appreciate everyone's help!
I appreciate everyone's help!
Could be a possible connectivity issue, can you change her connection point at the desk and or on the switch/hub. Could be a long shot but it seems strange that it is only one user being affected this way. You could even try changing cables although it will be a test and see if it fixes the issue as you make the various changes.