Disconnected network drive 2

[anthonymeluso]

Need I say more than that.

This problem has been huanting my network for a few months now and I have finally turned to the experts at Tek-tips for help.

This problem occurs when users logon and the logon script runs and maps drives. Howerver it can't map those drive because they're still mapped. When looking in my computer you can still see them there with the words "Disconnected Network Drive".

When you click on them they still work.When you try to disconnect them from windows a message says "Network Drive can not be found". You can't disconnect them from the command prompt either.

The quick fix it seems is to restart the computer. However that shouldn't be the case.

I have tried the auto-disconnect solution found on the net but that didn't seem to work.

Maybe its my logon script?

I'm thinking about forcing those connections to disconnect when a user logs out with a script.

Anyway any help will be greatly praised,

Anthony

 

[anthonymeluso]

Xmsre, I check my WUS records to see if I had the update but it told me that it was not needed for my servers. However, checking Microsoft site for that bulletin show that they have a fix for Server 2003 with SP1 installed, but you have to manually download it.

Hopefully this helps, because the symptoms are very close to the problems I'm having.

Mark, I did a gpresult and the client is getting all the correct policies. I also when around checking logon and logoff scripts to see if there was another one mapping network drives and their wasn't

But from all the suggestions I got here so far, I'm on a wait and see basis.

By the way guys I ran a script on every computer to set auto disconnect to -1.

Thanks you all,
Anthony

 

[anthonymeluso]

Just an update. I ran the suggested hot fix on all my servers and I'm still having this problem appear. The weird part is that drive that just maps itself after 10 minutes.

I really don't know what else to do. I can contribute this problem to SP1, most definitely because it wasn't a problem before that point. If not then some hot fix on the clients that broke something.

The bright side is this even though the drives are disconnected they still work. I mostly use shortcuts on the desktop for uses to get to the stuff they need on the network so they usually don't see the disconnected drives.

If, this causes problems other the things I found so far, I'm going to call MS. I never did that in 10 years of using their OS's.

Thank you all,
Anthony

 

[anthonymeluso]

Guess my streak of not calling MS for tech support will continue.

Problem solved!

Here's how. I searched the net again for any threads on the subject. I found one that was just recently answered by the person who posted it. He had the identical problem as myself but figured it out.

Apparently if you create a shortcut on the desktop to a map drive using its drive letter such as "H:\" in the shortcut's target source, the shortcut will try to connect to a drive that doesn't exists yet and windows will leave it as a disconnected drive.

The way around this is to use a UNC path for the shortcut. That way the drives stay connected and can be remapped with out problems. And the user still has a shortcut to the program or folder they need.

But I deeply thank those who gave up time to help me with this problem.

Still the best tech board on the net.

Anthony