Network Drive Unable to Connect

[karldenton]

Hi,

I'm currently getting an error with staff connecting to the shared area. This happens randomly on machines that have connected earlier in the day.

 

Its the message:

 

unable to connect to \\server\share. the local device name is already in use . this connection has not been restored.

 

Any ideas?

Thanks

[elsiegee40]

Is this a roaming profile problem?

 

Using delprof to clear out locally stored profiles so that a fresh copy is used from the server on logon may resolve this issue.

[karldenton]

No profiles are used either roaming or local. Its just whats on the local machine.

[mac_shinobi]

assuming you are using group policy to assign the script to map the drive / network share ?

 

If so can you post the script ?

 

Also how are you assigning the script ? Startup or logon ?

[7andY]

Is this to a server? I ask because this is the kind of message you get with a Desktop machine that has hit its 10 concurrent connections limit.

[karldenton]

Yeah its to a server. And after a few minutes the user in question could get on without doing anything different.

Guess it could be the concurrent connections limit. Is there a way to increase? Although it is to a 2003 server so shouldn't have the error.

[7andY]

Ah, won't be that, then...unless 'max users' has been set on the shares.

[Michael]

In your logon script, make sure it reads similar to this:

 

net use K: /delete
net use K: \\SERVERNAME\SHARE

[f21970]

Agree with Michael. That's how I do it too.

[mac_shinobi]

In your logon script, make sure it reads similar to this:

 

net use K: /delete
net use K: \\SERVERNAME\SHARE

 

Will using a persistent connection help at all ?

 

net use K: /delete
net use K: \\SERVERNAME\SHARE /Persistent:Yes

[Michael]

You could do that, but it shouldn't be necessary.

[chrbb]

This happens sometimes with our wireless, the laptop logs on uses a cached profile because the wireless wasn't available at logon, then cannot connect to the share on the server.

[CAM]

This happens to me too but with a machine that is logged on locally. Restarting the PC appears to fix it but I haven't been able to reproduce the issue.

[dtakias]

There is probably a previously cached network connection on the system.

 

There are 2 registry entries about network drives. Check them and see if there is any previously cached entries and delete them. Restart the machine and see if that got rid of the problem.

 

The entries are under Current User:

 

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU

 

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

 

 

cheers