Mapped Network Drive keeps disconnecting

[Kiriray]

Hi.

Anybody knows how to prevent users from getting disconnected to mapped network drives?
They are accessing a terminal server wherein they're constantly connected via VPN.
The data folder is mapped as f:almost everyday, a user would call saying that s/he lost the f: drive and would ask us to remap it for them.
It seems that they are connected to it during the first part of the day but after a few hours, they would lose their connection.

Any thoughts?

thanks!

 

[itpro34]

Have you attempted to to re-service pack the server?
I have not been able to find anything on this issue specifically...If I do, I will let you know

 

[koquito]

try using the command net use with the persistent option. A+, MCP, CCNA
marbinpr@hotmail.com

"I just know that I know nothing"
Socrates (469-399 B.C.E.)

 

[PaulGillespie]

Is this win XP per chance? I've seen it too. Don't know how to fix it but write a script to re-map and place it on the users desktop so they can use it instead of phoning.

Paul

 

[jgtriangle]

see microsoft knowledegebase article 297684

 

[Kiriray]

hi,

we've tried everything but they didn't help... for some reason, the /persistent option cannot be set on some client computers (they're all windows 98), and the net config server set to -1 didn't help either... i guess we're down to the batch file for now...

thanks for all the help...

 

[pytchley]

Windows 9x cannot use the persistant word in logon scripts.
The registry ca be hacked to prevent a timeout when mapped drives are idle. This can be found on this forum on Jan 27 user g4j4hgil4 - this resets the amount of ideal time before disconnection.

 

[iNfAmOuSeNiGmA]

in the registry change the mapped drive timeout to 0 or i think -0. I had the same problem with my 2000 server you might also wanna check your server's registry.

 

[Zcript3r]

I am having an issue where my mapped drives, even after I am able to connect the network resource, will still not get rid of the red X. This is keeping me from testing the registry change I made to the paremeters key of the lanmanserver to increase the disconnect time. Does anybody have any ideas how to get the red X to go away after network connectivity has been re-established?

Thanks,
Rob

 

[itsisnofun]

If this term server is on a w2k box. You have to set the network drive disconnect option on the server to a -1 or they will continue to get dropped don't remember the artice number but do a search at microsoft for disconnected network drives. there is a dos command to run that will set this option for you.

 

[itsisnofun]

Sorry about that I did not get it from microsoft but it is the command

net config server /autodisconnect: -1

this will set the autodisconnect feature on the server. It is the one that disconnects idle connnections.

 

[Zcript3r]

I am reading that if you use the command "net config server /autodisconnect: -1", it should fix the disconnecting drive problem in the LAN, but that it also shuts off the Autotuning ability of Windows 2000 Server, (Like if you add RAM, the OS will not recognize the change, etc. . .).
Is there a way to reverse whatever running the "net config server /autodisconnect: -1" command does, so that you could enable the Autotuning in the OS, add the RAM or whatever else needs to be done, and then re-run the "net config server /autodisconnect: -1" command when finished?

Thanks,
Rob

 

[wbg34]

"net config server /autodisconnect: 15"
To avoid this problem make the autodisconnect change in the registry. This will leave the autotuning features alone.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
Then modify the reg key autodisconnect to -1.

 

[golfballsmasher]

I am also having the same problem. I've modified the regisrty, and did the net config server. When I change the idle time out setting to -1 , it will get changed back the following day to the 65535 setting. I've even installed SP4 for Win 2000 , and that didn't fix the problem. I'm also running citrix metaframe 1.8 for win 2000 and I've installed SP3 for metaframe. I've had this problem since the day I bought the server from Dell. Dell tells me its not a hardware problem so they can't do anything unless I pay there outrageous software support fee's.

Has anyone else been able to fix this problem?

Thanks!

 

[wbg34]

Are your drives still disconnecting? When you change the registry to -1 Windows interprets that setting to mean the max value(The connection would have to be idle for 65535 minutes or 45 days 5 hours and 15 minutes before it is disconnected). So your server is operating correctly. If the reg setting is at the max and your drives are still disconnecting, then you are having a seperate issue.