General discussion

Locked

HELP!!!!! Disconnected Drives

By dwphilips ·
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?

This conversation is currently closed to new comments.

15 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Setup GPO

by Jonny Memonic In reply to HELP!!!!! Disconnected Dr ...

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?

Collapse -

by dwphilips In reply to Setup GPO

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

Collapse -

What about cals

by faradhi In reply to HELP!!!!! Disconnected Dr ...

do you have enough cals

Collapse -

by dwphilips In reply to What about cals

Plenty of them. More than I need.

Collapse -

HELP!!!! Disconnected Drives.....firewall ?

by johnk In reply to HELP!!!!! Disconnected Dr ...

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.

Collapse -

by dwphilips In reply to HELP!!!! Disconnected Dri ...

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.

Collapse -

Server side Reg change maybe..try this

by johnk In reply to

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

net config server /autodisconnect:-1

Collapse -

Server side Reg change maybe..try this

by johnk In reply to

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

net config server /autodisconnect:-1

Collapse -

by dwphilips In reply to Server side Reg change ma ...

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.

Collapse -

Hmmm....maybe this client side reg change

by johnk In reply to HELP!!!!! Disconnected Dr ...

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.

Back to IT Employment Forum
15 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums