Archived from groups: microsoft.public.win2000.file_system (More info?)
I have a W2K Server with a shared folder; on a W2K3 Server (running Terminal Services) next to it, I have mapped a drive to that folder for the purpose of allowing access to users on RDP. At the W2K3 (TS) Server, I began to experience problems opening the line-of-business app that is loaded from the W2K Server. Started to get error messages regarding the path. Meanwhile, I noticed that when first logging on to the TS, I received notification that "all network drives" failed to reconnect. Windows Explorer showed the drives appearing in a normal connected state, and they all opened quickly and without complaint. So... the logon process exhibits some odd behaviour that the app seems to confirm. I have attempted to disconnect the mapping, but the letter drive continues to appear with the "disconnected network drive" label attached; it won't go away or release the drive letter for reuse. And it continues to open as if normal. If I try to disconnect it again, that is not a given option. BTW, this was all working just fine for several weeks before abruptly breaking, perhaps after a massive Netsky attack. The boxes were protected, and are clean.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.