Discussion Locked

HELP!!!!! Disconnected Drives

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have approx. 200 windows XP Pro. computers that are mapped to shares on a Server 2003 Standard OS on my server. The problem is the mapped drives disconnect at random times and random drives. The only way to reconnect the drives is to restart the machine. I receive the error "System Resources Unavailable". NIC drivers are updated. I have turned off the power settings on the NIC local machines. I have set the autodisconnect on the server to autodisconnect-1 and turned off the power settings on the NIC on the server. This is random throughout the organization. I need any and all help as this is causing quite the issue. Any suggestions?

15 replies

by jonny memonic

Did you do all the updates for windows 2003 and how are the clients being mapped to the drive. was it done manually?
or GPO?

by dwphilips

It was done with a net use batch file. Never had problems until I changed the workstations from Win 2000 to Win XP

by johnk

I have seen this with McAfee Personal Firewall that it will disconnect the network drives after a period of time. Try to disable any firewall on the clients and see if this is it.

by dwphilips

I am using McAffee Enterprise version 9.0 and the firewalls are all disabled. Including the windows firewall. This is driving me crazy and my boss is pressuring me to solve this problem.

by johnk

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.

The purpose is to disconnect idle sessions after a set number of minutes.

Resolution

Refer to Microsoft article 138365 ? How Autodisconnect Works in Windows NT and Windows 2000.

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

Registry Editor

Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Use Registry Editor to increase the default time-out period. To do this, follow these steps and then quit Registry Editor:

Choose Start > Run, type regedit (Windows 2000 or Windows Server 2003) or type regedt32 (Windows NT 4.0), and click OK.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
In the right pane, click the autodisconnect value, and from the Edit menu, click Modify.
If the autodisconnect value does not exist, follow these steps:
From the Edit menu, point to New and click REG_DWORD.
Type autodisconnect and press ENTER.
Click Hexadecimal.
In the Value data box, type ffffffff (8 letter F?s) and click OK.
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.

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 press ENTER:

net config server /autodisconnect:

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 press ENTER:

net config server /autodisconnect:-1

by johnk

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.

The purpose is to disconnect idle sessions after a set number of minutes.

Resolution

Refer to Microsoft article 138365 ? How Autodisconnect Works in Windows NT and Windows 2000.

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

Registry Editor

Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Use Registry Editor to increase the default time-out period. To do this, follow these steps and then quit Registry Editor:

Choose Start > Run, type regedit (Windows 2000 or Windows Server 2003) or type regedt32 (Windows NT 4.0), and click OK.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
In the right pane, click the autodisconnect value, and from the Edit menu, click Modify.
If the autodisconnect value does not exist, follow these steps:
From the Edit menu, point to New and click REG_DWORD.
Type autodisconnect and press ENTER.
Click Hexadecimal.
In the Value data box, type ffffffff (8 letter F?s) and click OK.
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.

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 press ENTER:

net config server /autodisconnect:

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 press ENTER:

net config server /autodisconnect:-1

by dwphilips

I have set the server to not autodisconnect with the command line
net config server /autodisconnect:-1. This did not solve my problem. But thank you anyway.

by johnk

System Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\

Parameters]

Value Name: Autodisconnect

Data Type: REG_DWORD (DWORD Value)

Value Data: 0 to 4,294,967,295 (0xffffffff) in minutes.

Are these workstations connected to the server via a VPN? If VPN, then we could be dealing with DNS issues. Try adding the servername and IP to lmhost and hosts.

Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.

by dwphilips

The workstations are connected to the server throught patch cables and manual switches not a vpn. They all worked fine until I updated from Win 2000 Pro to Win XP Pro.

by jfo

I am having the same problem. Moved from W2K Pro about 3 months ago to XP Pro. Have a shared drive on a W2K Server. For the last 4 years never dropped the connection to the shared drive. Now at random poof its just not there anymore. At first it I thought it was conflicting drive letters, every now and then I have to hook up a USB thumb drive or zip drive. They always wanted the same letter as the shared drive. So I changed the shared drive to N. It is still dropping. No idea what is going on there. Anybody, Bueller?

by stacey

I have been having the same problem since we upgraded to Small Business Server 2003 and Windows XP. I too have done all the registry fixes and disabled autodisconnect and disabled sleep on the NIC. I have also replaced all my switches and NICs and even reformatted and replaced hard drives and mother boards. I have replaced all the patch cables and had the wall wiring tested professionally. I have deleted and recreated my dns server and dhcp server. I have done everything I can think of.

The only thing that fixed it was to assign static IP addresses. But now I am having trobule with even the static IPs dropping connections to mapped drives. It is like the machines lose connection to the domain controller. It doesnt happen to machines outside of the domain.

by nelsonk

My issue with this happened sometime around Thanksgiving 2006. We have all windows XP clients to windows 2003 servers. All the autodisconnects on servers and clients have been modified with no luck. The wierdest part is this doesn't happen on all machines. Even updated the NIC in clients to latest drivers (intel pro set).

Any ideas on what is causing this and how to fix it? I am pretty sure its client related. My boss is getting a little upset to the "no one has a clue" i get even from techs we brought in.

Thanks

by thedragonman

I have had this issue when we have a power outage. The problem is the workstation reboots faster than the network.

If the workstation tries to reconnect to the network before the network comes up the drive will be detected as missing or disconnected. Usually a going into "My Computer" or launching "Windows Explorer" will reconnect them. A simple reboot will usually have the same effect.

If your workstations are set to stay off in the event of a power outage this will allow the network to be restored before the workstation tries to come online.

This discussion is closed to new replies.