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]

Oh I left out a couple of key details. This problem starting popping up after I installed SP1 on all my servers. It also appears that the Home Folder comes up as "Disconnected Network Drive" and Windows maps that one through their account info.

Thanks again,
Anthony

 

[bustamove]

hi,

we use the following for our network.

net ues Z: /delete
net use Z: \\server\share

 

[anthonymeluso]

I tired that to no success. When you type

net use Z: /delete it will say no such connection exists.

Yet the drive still is there in my computer and you can't map the same drive letter again without turning off the PC.

Also any other combination of command line commands will not work. I have been researching this problem for two months and I have tired every type of combination.

I'm hoping someone here got either an answer from MS or found the solution to this type of problem.

Thanks anyway,
Anthony

 

[markdmac]

I'll first refer you to my FAQ on vbscript login scripts: faq329-5798.

That out of the way, it sounds like you may have a probably have a drive stuck in the registry.

\\hkcu\software\Microsoft\Windows NT\CurrentVersion\Network\Persistent Connections

Delete the offending connection from there if the script methods do not work for you.

I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

Mark your script is world famous in my opinion I have used parts of it to delete and map printers on our network and it works very well.

I have just switched my script with the part of your script that deletes and maps network drives. Hopefully this will help. I will look into your registry fix and see if that is the case for the home folder mapping.

Like I said earlier this problem does exists out there. You will see others with it but no definite answer. For me it started after I had installed SP1 on the servers.

I hope your suggestion will help me Mark,

Thank you,

Anthony

 

[markdmac]

Just to be certain, you have NOT configured the home folder within the users properties right?

Glad you are finding my script useful. It does seem to be rather popular which makes me happy.




I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

Yes I have configured the home folder with the user's properties in AD and that drive also comes up as disconnected. So I not do this? Was working well for months.

Thanks again,

Anthony

 

[markdmac]

That is really for legacy support. Remove that setting from within the user properties and just use the script to map the drive.

I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

Ok here's something for you to chew on. I logged into a computer which I had mapped three drives with your script a little while ago. Two of those drive work fine and can be disconnected the third says its disconnected and can not be found when I try to remove it.

I check the registry key you had mentioned before and all that was there was a key for savedconnections and it was set to yes.

I will do what you just suggested about the home folder though and see how that goes.

Anthony

 

[anthonymeluso]

Fooled around some more and have a good feeling its some autodisconnect setting that causes this problem. Whether its server based or workstation based, I don't know. I mean when a user logs off doesn't windows end that user's network connections?

If not autodisconnect, maybe it has to do with some remote desktop setting. It appears this problem crops up on machines that have been logged into remotely.

Just talking out loud here. Anyone that can make a connection here?

Mark, thanks for you super quick help,

Anthony

 

[markdmac]

Try running the following command on both a workstation and the server:

net config server /autodisconnect:-1

this will disable the autodisconnect feature which can drop a network drive mapping due to inactivity...just in case that is a contributing factor.

Was the drive that is giving you trouble the drive letter mapped as the home drive int he users properties?

I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

It wasn't always the home drive that had the problem it was basically any drive that I mapped.

Since I started using your script to map drives I've been mostly alright. I will try the autodisconnect command on the client if I start to see this problem again.

Oh, I use DFS with replication on my home and profile directories. Could that maybe contribute to this problem?

Thanks,

Anthony

 

[markdmac]

I don't think the DFS would be a factor.

I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

Where to begin. I changed the autodisconnect setting on a client to -1 and I also created a logoff script that disconnects all mapped drives.

The result is not good. If I restart the computer and login everything works great. If I log off and then back on again 2 out of 3 drives are disconnected but still there. If I try to disconnect them it says that the network connection can not be found, even though if I double click on it it connects.

Is there some setting in the GP that might cause this?

Thanks,

Anthony

 

[anthonymeluso]

Mark, this just keeps getting better.

I'm on a computer that I just restarted and it had no mapped drives. Ten minutes later I check my computer there is a mapped disconnected drive that I can connect to but can't disconnect.

How it got there I do not know,

Anthony

 

[markdmac]

Wow, seems you are in a world of hurt. What happens if you edit that registry setting and get rid of all the dirves listed there?

I hope you find this post helpful.

Regards,

Mark

 

[anthonymeluso]

That's the thing. There is nothing there where you told me to go in the registry.

\\hkcu\software\Microsoft\Windows NT\CurrentVersion\Network\Persistent Connections

No drives listed at all even through they are mapped correctly when I do a restart. The only thing that is there is a key called SaveConnections and its set to yes.

The funny thing in my research of this problem since June is that there a few threads about it on the net. Which means to me its a some what new problem or very rare. Each thread just ends without an answer.

I tired real hard over the past year to keep this once horrible network into shape. Then this happens.

Mark, I can't thank you enough for all the replies you put in this thread so far.

Anthony

 

[markdmac]

If you run a gpresult at the client end, what policies does it say are being applied? Need to see if there is another login script processing from somewhere you are not aware of. Also be sure to check the netlogon directory to verify it does not have anything in there.

I hope you find this post helpful.

Regards,

Mark

 

[xmsre]

You mentioned that you installed SP1, did you install KB 898060 as well. IF not, you may want to do that. It specifically resolves issues with:

• Inability to connect to terminal servers or to file share access.
• Failure of domain controller replication across WAN links.
• Inability of Microsoft Exchange servers to connect to domain controllers.

These issues can occur after installing SP1.