Question Locked

Windows XP Pro randomly loses connection to network

0 helpful
23 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi there, I've been poking around the site and I've seen related posts about this, but no real solutions yet, figured I'd post my query about this and see if someone can help...

I have a lab of 17 Dell Precisions, and 1 Dell Poweredge 2900. The workstations are running WinXP Pro all patched and with the latest drivers. The server is running Server 2003, patched and good. The network runs my own private Active Directory domain.

All the machines have a static IP address given to me by the IT department, defined by MAC address.

There are two more labs connected to the same switches, running MAC OSX. These labs do not have the problem.

The problem began in February of 2007. Seemingly if a machine is left on for about 6~8 hours (doesn't matter if it is idle or being heavily used; doesn't matter if it is logged in or not logged in) the machine will spontaneously lose network connection, and will not see the internet. It will, however, still see the server if the user has a drive mapped.

Repairing the connection does not work. Re-inserting the ethernet plug does not work. Restarting the machine (not power cycling) does not work. Only Power Cycling the machine works to restore the connection.

Curiously, when the server loses connection, restarting (no power cycle) fixes the problem. I do not have to powercycle the server, only the workstations. When the server loses its connection, its connection to the AD Domain also fails. The restart fixes this too. As mentioned above, however, machines attached to the server via a mapped network drive can still access the server.

When the network connection goes out, there is no indication that the network has lost connectivity. The network icon indicator says the ethernet is connected at 1Gbps.

The wiring is all brand new and tested. The NICS are all brand new. All the machines exhibit this problem. The lab worked fine from Sept 2006 to feb 2007.

No software has been added or deleted from the machines since Sept 2006, save for Microsoft Patches through update.microsoft.com.

The workstations exhibit this problem regardless of whether they are logged into the AD Domain or logged in as a local administrator.

There is antivirus software, MCaffee 8.5, updated and the settings are set to a moderate level. Microsoft firewall is running.

I have another PC lab running all the same software on similar spec machines in a different location (connected to the same IT infrastructure) that does NOT exhibit ANY of these problems.

When the machines lose connection, ipconfig shows the IP addresses and DNS servers (i.e. - does not show 0.0.0.0, its shows the #'s its supposed to); pinging an IP locally and to the internet fail.

Hibernation mode is deactivated.
Power save mode on the NIC is disabled.
Once rebooted, it works for another 6~8 hours.

I appreciate any help.
Thanks much!!

23 replies

by bart777

Sounds like it's a DHCP problem though.
If you have no address when the connection is lost that machines are not getting an address assigned to them. These machines are not statically assigned but have a DHCP reservation from the server assigned to that MAC address.

Try this...
Take one of the PCs and set the address on the NIC to what the reservation says it should be. Then run the same machine for that timeframe and see if the connection is lost.

Your reservation is evidently set to an 8 hour lease and for some reason cannot renew the lease from the DHCP server.

Let me know how the test goes.

by beverins

Forgot to put in some info, sorry about that. In fact, all the IP addresses are already set in manual mode to the IP that I found in the DHCP. Found I had to do that to allow for network rendering (well, when the system didn't "forget" how to connect!).

Now, perhaps it seems illogical to do it in reverse, but I'll set a few of them to DHCP mode and see what happens if they go offline.

I'll let you know what happens anyway.

by sgt_shultz

If safe mode w/networking doesn't have the problem, i'd look for viruii or malware.
the only other thing i can think of to try is to set the media type on the nics something other than 'auto sense' such as 10mb half duplex or 100mb full duplex.
I would also start keeping a log of when stuff lost the connection.
this sounds like hardware to me but i can't offer more than that, sorry.
i'd try a new brand of nic if i could and i'd try a different switch (like, trade with the lab that doesn't have this problem, see if problem follows the switch)

by michael

I tried all of the suggestions that have been made here and it did not change. They were the first things that MS and Netgear told me to try. I've switched everything, ran every kind of spyware, and even tried changing settings throughout the user profiles, and the settings on my routers, but nothing makes a difference. I am going to continue searching and if I find any answers, I will post them here.

by beverins

Sorry I didnt monitor this thread closer, had to fix other things. I wanted to post an update and get any further ideas why this network loss happens.

To recap - when the XP machines and the 2003 Server machine lose network connection, the machine still reports itself as being connected. However, when one computer tries to either access the internet or each other, then we get the error messages.

This is also affecting Active Directory as two of the server machines can't connect to this machine and I get log on errors.

I'm working around the problem by having the server reset itself every morning using a utility. It still fails at night, but at least in the day when most classes are up the problems on the server end are minimized.

I reinstalled all the lab computers and they seem to not exhibit the problem anymore, but more testing is needed. I am loathe to reinstall the server at the moment.

If I log in locally and not as part of the domain, then the computers never lose network connectivity.

What frustrates me about this problem is that the OS doesn't report it. You never get that little yellow arrow or a red x over the network icon - and in part, why should it? It IS connected - its apparently the OS that's doing it.

What is also interesting is that the server's network loss can be cured with a reboot but when the lab XP computers did it, they needed to be Powered Down to fix the problem. Keep in mind, they only lost connectivity when part of the domain.

The lab computers are now reattached to the domain, and aside from the server still losing connectivity they seem alright for the moment.

So, long story short, I'm almost 100% positive its something in the OS. The network card is set to be on all the time, the profile is set to Presentation Mode as well.

by 666mr666

Right click "my computer" and left click manage. in the computer management box left click device manager. in the right hand pane click the + sign beside "network adapters".
right click your network card and left click properties. a new box appears. thew last tab is "power management"
if the box "allow computer to turn off this device
2 is ticked then there is your problem. untick it and ok/apply and close all windows.
job done!.

by michael

I tried your suggestion and it did not resolve the issue. Our issue is pretty specific, although the original post stated that the network connection was lost randomly, to be more specific, the connection to network resources is lost every day after approximately 8 hours after we login to the network. The reason I used the word randomly, is because we cannot determine exactly when it loses the connection to the network. It might very well be exactly 8 hours or 7 hours and 56 minutes, but there is no way to tell. We can use the internet connection, but we cannot access resources on the server and our printers. I have checked the event logs on my computer and here are the Warning entries when this seems to occur every day:
The browser was unable to retrieve a list of servers from the browser master \\SERVER on the network.
The other event description is:
The Security System could not establish a secured connection with the server cifs/Server. No authentication protocol was available.
Under Category is shows SPNEGO (Negotiator) and I don't know what that means.
These two Warnings seem to occur every day at different times, but I'm guessing that it has to do with the time that I login to my computer. I am going to continue to check the logs to see if I can figure out more information.
Thank you for your help. Michael

by michael

I have had the EXACT same problem for the better part of 2 years. I have a simple home office network with a Dell Poweredge 1800 Server running Win Server for SB 2003 and various yet current Dell Workstations and Desktops. All are completely updated using McAfee and no firewall, using NAT for this simple network. I use Netgear Routers and Gigabit Switches. I was an IT/Network Consultant in NYC for 15 years, and I have not been able to resolve this issue, even with help from MS and Netgear. There is no simple reason why this is happening, but I share your frustration. If you would like to work together to try to resolve this, I would be most happy to. You can reply here and I will get an email about the post. I have noticed that my laptop when connected wirelessly, does not drop the network connection, so it seems to me that it is in the network components and not the server. Have you tried testing a laptop?
Mike

by vdoisan

Have about 2 dozen Dells, this same problem is on 3 OptiPlex PCs (GX520, 745 and 745C) for me.
Changed NICs, Reloaded Windows, disabled power save, everything that was mentioned in this thread - no go. Still every morning these PCs have to be rebooted. Strangest thing - I can Remote Desktop into them, but can't connect to any network services once I am in nor ping out. Very strange.

To me it looks like a Windows or BIOS/Firmware problem. Hardware and cabling has been ruled out in my case.

by michael

I'm also still having this problem and I have tried everything that everyone has suggested to me, but nothing will resolve this issue on our computers. I'm not using AD, and even more strange, it is NOT happening on my new Dell 820 notebook, which is also running XP and is a wired connection. If I come up with any possible fixes, I will post them here. Take care. Mike

by sue t

I had the same problem only the server was running NT4 sp6 and the workstations were running Windows 98se. We also have a mixed enviroment and our DHCP is running on a Mac OS X server. DNS runs from both a Mac server and a Windows 2003 server. Drove me nuts for over a year until I finally just set the server to reboot every night. I no longer had the problem. It doesn't solve the problem but I wanted you to know that I tried everything you did with the same results but the OSes involved were different.

by edkim77

Here's something that might work for you:

Mapped Drive Connection to Network Share May Be Lost
View products that this article applies to.
Article ID : 297684
Last Review : March 1, 2007
Revision : 5.5
This article was previously published under Q297684
On a computer that runs one of the versions of Windows that is listed at the beginning of this article, if you map a drive to a network share, the mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red "X" on the icon of the mapped drive. However, if you try to access or browse the mapped drive, it reconnects quickly. This behavior occurs if the network share computer runs Microsoft Windows NT 4.0, Windows 2000, or Windows Server 2003.

Back to the top
CAUSE
This behavior occurs because Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. The connection can be re-established very quickly, if required.

RESOLUTION
To resolve this behavior, change the default time-out period on the shared network computer. To do this, use one of the following methods.

NOTE: You cannot change the default time-out period for Microsoft Windows 95-based computers and Microsoft Windows 98-based computers that have shared resources.

Registry Editor
NOTE: You cannot use this method to turn off the autodisconnect feature of the Server service. You can only use this method to change the default time-out period for the autodisconnect feature. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Use Registry Editor to increase the default time-out period. To do this, follow these steps, and then quit Registry Editor:
1. Click Start, click Run, type regedit (Windows 2000 or Windows Server 2003) or type regedt32 (Windows NT 4.0), and then click OK.
2. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

NOTE: The client side session is automatically disconnected when the idling time lasts more than the duration that is set in KeepConn. For this reason, the session is disconnected according to the less set duration value between AutoDisConnect and KeepConn. To modify the timeout duration in the client side during a UNC connection, specify the arbitrary time in KeepConn from registry value.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\lanmanworkstation\parameters
Value: KeepConn
Data type : REG_DWORD
Range : 1 to 65535 (sec)
Default value: 600 sec = 10 mins
3. In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:
a. On the Edit menu, point to New, and then click REG_DWORD.
b. Type autodisconnect, and then press ENTER.
4. On the Edit menu, click Modify.
5. Click Hexadecimal.
6. In the Value data box, type ffffffff, and then click OK.

Back to the top
Command Line
NOTE: If you use this method, you may turn off the autotuning feature for the Server service.

To change the default time-out period for the autodisconnect feature of the Server service, open a command prompt, type the following line, and then press ENTER
net config server /autodisconnect:number
where number is the number of minutes that you want the server to wait before it disconnects a mapped network drive. The maximum value for this command is 65,535.

NOTE: If you set the autodisconnect value to 0 (zero), the autodisconnect feature is not turned off, and the Server service disconnects mapped network drives after only a few seconds of idle time.

To turn off the autodisconnect feature, open a command prompt, type the following line, and then press ENTER:
net config server /autodisconnect:-1

by michael

I don't have a KeepConn key in my registry, so I am not sure how to proceed with your help above. I am using Windows2003SBSR2. If you have any other suggestions, I would like to hear them, thanks. Michael

by wesley.chin

In your post, you mentioned that static IP is used. In that case, ipconfig will never show "0.0.0.0"

Do you have any automation that occurs each day?

Check Network Connections and see if anything is disabled.

by eddieduce

Bevery,

Have you checked the Local Security Policy on the client/server? Besides the network cards themselves, there are also timeout policies for the account/session connections that may force the accounts/PC's to not have access to the server even though they can still see it.

by michael

Thanks everyone for their suggestions here. I spent this entire Thanksgiving holiday re-installing my server and I made a few changes from when I first installed the server, but I think the change that I made that has solved this problem, is that I am allowing the Windows Server to be the DHCP server instead of my router. I cannot explain why I believe this to be the case, but my computers have all been running for 3 days straight now and have not lost the connection to the server even once. I would try to research further into what the real solution is, but I simply don't have the time. I will however change it back to the router to see if I am correct, that's easy enough, but if that wasn't the cause, then it could be something that I changed during the re-installation that's different from the initial install. I hope that you all find the solution to your problems. Good luck and thanks again for all the input. Michael

by juanp

Anyone find or come to a concrete solution?

by charles

On the server, go to Active Direct Users and Computers. Right click on the user account that is losing connection, and select Properties. This will open a new window with multiple pages. Select the Sessions tab. There you can see few settings for disconnection. I had the Idle session limit set to 2 hours. I changed that to Never and all seems to be fine so far. Good luck.

Cheers
Charles

by olando.berry

im not tooo tech savvy but i do know that dells seem to have networking issues with thier pcs and you can only have 10 in a workgroup...more thanb that has to be in a domain....if im sayin something u already know then dont beat me over the head but i am aware of dell having problems cuz that seems to be all the stuff i find that comes up. some implementations arent correct obviously but breakin that down perfectly id say im not certin of....however, this problem does spark my interest

by jay_tech

I faced this problem on my work laptop.
> HP Elitebook, WinXP Pro SP3
I had all the symptoms as above.
- Driver had no errors in Device Manager
- Network icon shows connected until you start a file transfer on the network or somethign similar
- Un-checking Power management options for NIC & hard set to 1000mbps had no effect.
- I would get back the connections if I deleted the driver & re-installed it. (Saved me from re-booting)

The same network point hooked into another laptop had no problems.
The only change I recall was that i inserted a router from my wall socket, so I could connect 2 laptops.
I removed the router from the equation today & it's all back to normal now.

It's not the router's fault per se, but seems to be the interaction between the Linksys SD2005 router & my Hp Elitebook laptop...

Hope this helps someone.

by ajcraley

I attacked this same basic problem for about 2 months. Found the issue was with the servers Kerberos settings. The default ticket time is 10 hours. It took some digging on my part to find where to change these settings but im only a novice when it comes to servers/networking. Change the default ticket time to 15 or so hours and your problem should be resolved.

This discussion is closed to new replies.