We have a DC and two seperate Terminal Servers
On the Terminal Servers (Windows Server 2008) the network drives have been working just fine for a long time.
Since a week or so when we reboot the server(s) only the known connections are made and all seems fine, but when I check the next day all drives (A-Z so to speak) are occupied with several disconnected network drives. All mappings seem disconnected but are actually working when clicking on them..????
I have no idea where there mappings come from, I have allready checked the login script and it's fine. Somewhere on a forum I found you can change a setting to track the creation of mappings in de Event Log but you would have to set a property in regedit for I,J,Q and Z for instance. The problem is these links are nowhere to be found in the registry. I have checked for all (!) users seperatly...
I hope someone where can help me with this, because it is getting a bit anoying :-)
Thanks in advance !
Thank you for the post.
This behavior may occur because the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions: http://support.microsoft.com/kb/297684/en-us
Nick Gu - MSFT
We have the same issues on 2 different Terminal Servers (W2k3 + W2k8 different sites)
All drive letters which are not in the login script (net use command) or local drives get occupied as a "not connected network drive"
If I try simply to disconnect the drive letter it gives a error message "this network connection does not exist"
Any update on this issue ?
Marco van gameren