Red "X" on Mapped network drives in peer to peer

[Dennis RIce - Tablet PC MVP]

Help!
I have a user with an XP Pro machine (that was upgraded
from Windows ME), that has a problem with getting shares
reconnected. When they restart the machine, all mapped
network drives mapped to a particular XP machine in the
peer to peer network show up with red X's in Explorer.
IF you dbl-click the share in Explorer, it will
reconnect, but if an application tries to access the
share letter before that, you get a resource not
available message. The KB refers to stored names and
passwords as a possible solution, but when I go to stored
names on this user, it shows none. I have tried to
disconnect and manually re-add them, same result. FYI,
there are 2 drive letters being mapped to the same share
due to application requirements.

Suggestions? Thanks!

Dennis Rice, MVP - Tablet PC Platform

 

[Fred Davis]

Dennis,

Let me sympathise with you.

I have been stuggling with this for the past 3 weeks!

I've read anything and everything I can find here, on the
net and on the knowledge base, all to no avail. There are
far too many posts here on and around this subject for
this to be just a slight glitch. It is my opinion that MS
have c*ck*d up here but will not admit it.

XP is a defininte pain when you are used to using 98SE
networking.

I will be watching this thread with interest.

Fred

 

[Danny Slye - [MSFT}]

There are numerous causes for this issue. The most common being the
default autodisconnect setting for lanmanserver. See 138365 How
Autodisconnect Works inWindows NT and Windows 2000
http://support.microsoft.com/?id=138365. Setting autodisconnect to a very
high value on the machine that hosts the mapped drives is the first thing
that you want to try. You may also want to make the following change on
the client machine that has the mapped drive if the one above does not work:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
eters

name = KeepConn
type = REG_DWORD
value = 1 to 65535 seconds (Default: 600)

Third party applications, personal firewalls, cd-burning software (Roxio is
one), NIC power management, antivirus software have all been known to
contribute to this problem.

--------------------

Fred

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!

 

[Mike]

I had this problem also and have found a way to make it
work. It's not very elegant, but here it is -

1. Turn off the fast logon in windows xp. you
can do this in the control panel under user accounts.

2. Create a .bat file on your drive that contains
the "net use" command to map your drive. For my network
the syntax was

net use J: \\dell\dell_c password /USER:dell\Guest

3. You need to execute the file on logon. I tried
several things with autoexec but couldn't get them to
work. I went into the registry and added an entry
that would autorun on startup. see the following
link as a reference.
http://www.winguides.com/registry/display.php/823/

Hope this helps.

Mike