You are on page 1of 1

"Disconnected Network Drive" I've just had a similar problem where a supposed as a disconnected drive in Windows Explorer, but

to view the drive's contents. However, shortcuts this N: drive didn't work, I couldn't disconnect Explorer, and it wasn't listed using the Net Use N: network drive was listed I could double-click on it that pointed to locations on the drive through Windows command.

The problem was with a shortcut in the user's Startup folder that pointed to a command file on this N: drive. It was as if the N: drive definition was being created on the fly in response to trying to execute the shortcut, but not correctly. The following resolved the problem: 1. Log on as the affected user. 2. Move the shortcut from the Startup folder. 3. Open a Command window, and execute the following commands: net use /persist:no net use * /delete 4. Log off, and then back on again, and verify there were no mapped drives. 5. Open a Command window, and execute the following command: net use /persist:yes 6. Run our standard .cmd file to create our standard drive mappings. 7. Log off, and then back on again, and verify that the drive mappings were as expected. 8. Restore the shortcut to the Startup folder. 9. Log off, and then back on again, and check that behaviour was as intended. Your set-up won't match ours, but to generalise, you could look for any start-up processes that point to your problem mapped drives, disable them, and ensure that drives are mapped correctly before they are used by any other processes.

You might also like