General discussion


Network drives not connected, but are

By pbtoms ·
A user in my office (unfortunately, he's the boss!) is having an ongoing issue with mapped drives. He has Win XP, server is a Win2k Server (only one, DC, file server, etc.) When he logs on, more often than not (but not EVERY time) he gets the little pop-up that says the network drives could not be connected. Everything works (he can open outlook, it sees the Exchange server just fine), and if he clicks on the drives in WinExplorer they open. But our billing program uses a mapped drive, and he has to go to Windows (My computer or explorer) and click on the drive first, or the billing program sees that it is "not connected" and doesn't even try. Any suggestions? I originally assumed it was because he was logging on too fast, and all the services weren't up yet, but it happens even if he turns on the computer, goes for coffee, THEN logs in.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by sgt_shultz In reply to Network drives not connec ...

this is a known bug in xp is what i remember from my browsing in the mskb. the workaround i think was to first try to patch with all windows updates, of course, then if no joy use login script to map drive with persistant switch then maybe try putting that folder in startup so force drive access. write again if you need help with that the guys here can do it with one eye shut this is yucky answer for you as i only have tiny time. just know there is bug and go to and search mskb.
anyway, the bug part comes up because of the drive having been mapped in the first place with 'reconnect' checked from Map Network Drive in explorer. somehow that makes bug if remember right. can't remember details. so think maybe there was registry hack to remove. anyhow, fix is somewhere at search under windows xp use mapped drive for search and you will find

Related Discussions

Related Forums