General discussion

Locked

Disconnected Network Drives on a Domain

By mm212 ·
I'm having a problem with workstations getting disconnected network drives after non-use. If the user double-clicks on the drive, it will open but take a very long time and will never show up as anything other than "disconnected network drive" until the workstation is rebooted. I found that Windows 2000 and 2003 servers will autodisconnect client network drives after 15 minutes by default. I found the Microsoft knowledge base articles describing the command line "net config server /autodisconnect:-1" to disable autodisconnection. The problem is that the same kb article also states:

"For a Windows 2000 Server in a Domain, running either as a domain controller or as a server, the maximum value is 65,535 (0xffff). Values set above this will be returned to 0xffff after policy refresh. Windows 2000 Servers in a workgroup may be set to any value as indicated."

I have discovered that this is indeed true. Every Monday morning, our users again have disconnected network drives and the only fix we have it to reboot their workstations. Looking at the registry entry on the servers shows the setting was set back to 0x0000ffff rather than the 0xffffffff that I gave it previously. 0x0000ffff gives 18 hours of idle time before disconnecting. Unless they reboot every Monday morning, I don't see a way to make this work.

We use a domain. With the number of workstations and sites we have, that's the only way to do it. It is a Windows Server 2003 Active Directory domain with Windows 2000 and 2003 servers and Windows 2000 and XP clients.

I'd appreciate any information I've missed or even a workaround that will fix this problem!

This conversation is currently closed to new comments.

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

All Comments

Collapse -

all of these are a little off the wall, but should work.

how often do you make group policy changes that would effect the server?

put the servers in a seperate container, apply the group policy you want, and then set it to either never refresh, or refresh only on a reboot. if you set it up to refresh only on a reboot, write a quick little script that will change the registry setting you want changed, and put that in the startup folder or run key. sure, it'll run a few times when you don't need it to, but it won't hurt anything.

or...

set scheduled tasks to run 2-3 times a day to change that settings back to what you want it to be. i don't know how windows handles currently open sessions in regards to changing this key, but it's something worth looking into, maybe. i think my first suggestion is better that this one, and i can't really think of a better way to do it.

Collapse -

by mm212 In reply to

It may have worked but a better answer was listed. Thanks!

Collapse -

by sgt_shultz In reply to Disconnected Network Driv ...

wow, that bites big time. what about mapping the drives via a login script, then autologging the users out every friday night so they have to log in and get the drive mapping refreshed?
only other thing i can think of is to read from the drive every 17.5 hours via a scheduled task...
sorry if this is all too lame, just 2 cents

Collapse -

by mm212 In reply to

Poster rated this answer.

Collapse -

by NZ_Justice In reply to Disconnected Network Driv ...

we use a login scripts to map user network drives.

No autologging out is needed, In your script you just need to check for the mapping, If it exist delete it then remap every time the user logs in.

So every time the user logs in his drives get mapped.

Collapse -

by NZ_Justice In reply to

here is example. login bat file.
--------------------------------

:MAP_COMMON_DRIVES
REM **************************************
REM THESE ARE REQUIRED DRIVES. MUST REMOVE ANY REM EXISTING DRIVE PRIOR TO MAPPING TO ENSURE
REM CONNECTION
REM **************************************
if exist i:\nul i: /delete > nul
@net use i: \\[*mapshare] > nul
------------------------------------------------
*mapshare is the drive path you want to map eg. i: \\appserver\apps

you can do this for all the drives you need mapped.

Collapse -

by mm212 In reply to

Thanks, man. This worked. While you didn't give the vbs script to accomplish it, I at least had a place to start. For those interested, here's the vbs command to get this accomplished.

if fso.DriveExists("G:\") Then Net.RemoveNetworkDrive "G:"

Of course, substitute whatever drive letter you wish to remove the mapping for. I added this line just above the drive mapping in the logon script.

Collapse -

by CG IT In reply to Disconnected Network Driv ...

NZ is right. the log on scripts for mapping network drives is the way to go.

Collapse -

by mm212 In reply to

Poster rated this answer.

Collapse -

from the way i understood it - he really wants to avoid rebooting/logging off, in which case a login script does him no good. having a script like that run every morning at around 4am as a scheduled task should do the trick.

Back to Windows Forum
14 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums