network error in xp

[offmyrocker]

I keep on getting an error when trying to connect to a mapped drive on my network, it works fine for most of the day and then out of the blue it dosen't. This is happening at least once a day.
The error:
"An error occurred while reconnecting X:\\dhpch01\foldername
Microsoft Windows Network : The local drive name is already in use. This connection has not been restored."

I then have to restart my pc, what a pain! Any help would by great!

 

[offmyrocker]

....just one other thing, this never used to happen in 98 or 2000, seems to be only with xp

 

[Jazket]

First, assign a unique IP to your computer, the one that has the network folder shared. and a unique name. Make sure you don't repeat the IP and/or the name.

restart those computers which u assigned the new IP to...
then you wont have any problem..

then thing is that your router as a DHCP that assigns any random ip to those computers directly connected to it, and somehow, sometimes, it assings an ip to a computer that has it already, but that will only happen if you got PC1 with a static ip assigned by your own, and another PC2 that has dynamic ip assignment. This is it:

PC1 - IP: 192.168.0.10. <--- Assigned by you at the TCP/IP Properties.

PC2 - IP: 192.168.0.11. <--- Assigned by your Router's DHCP service.

you restart PC2....

now, PC2 - IP: 192.168.0.10 <--- IP Conflicts!!!
"The ip (name) is already in use.".

now, when it says:
"local drive name is in use..." (which is the problem you have) means that the name you assigned to that drive, and the letter are in use in your computer already.

is like this:

you got C:/Local disk in your computer, then you map a drive and you name it "C:/Local disk". lol. it will always give you conflicts.

Try not assigning same names and same letters never. Neither same IPs.

Hope it helps.

 

[bcastner]

This is an annoying problem that Service Pack 2 is supposed to eliminate. In most cases a Red "X" on a drive can simply be ignored; there is no reason to attempt a reconnection as it will be done automaticly if the share is called.

The pre-SP2 recommendation does not always work, but it works enough times it is worth mentioning:

This is the autodisconnect on the server disconnecting you after a set period of time. You can extend this time almost indefinately by modifying the "autodisconnect" registry value. I would reccomend setting this value
to 65535. This will cause the autodissconnect to not kick in for 45 days. However, the downside to this is that it will not autodisconnect any connections. You will need to watch the server to make sure that sockets are not being used up. You can run a "netstat -an" to see how many
Active Connections you have.

The autodisconnect value is located at
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters.

138365 How Autodisconnect Works in Windows NT and Windows 2000

http://support.microsoft.com/?id=138365

It does help to clear any previous persistent connections in the logon script. Add before mapping any drive letter:

net use * /delete

This oddly can occur in XP if the Netbios machine name and the user name are identical. So if the machine name is offmyrocker, then user offmyrocker can occasion this error.

So:
. Check explorer and see if the drive letter is in fact i n use and ignore any red X's
. Try adjusting the autodisconnect values on the share server (not your workstation);
. Clear persistent entries with net use at the beginning of your logon script;
. Do not name computers after users
. And upgrade to SP2