mapped drived not available at logon?

[AMD]

My XP pro workstation's mapped drives are not available
when the user first logs-in. We have WIN Server 2003;
Clicking on each mapped drive prompts them to become
available. Why don't the mapped drives connect at login?
This has been a problem I have seen posted many times
before, without a solid solution. Has this been addressed
with a good hot-fix yet? I would be very grateful for a
solution.
(e-mail address removed) MCSE CCNA

 

[Bernie MCSE MCSA MCP]

what i have found with network drives the username and
password of the mapped drives user name and password must
match on both machines and that should take care of your
problem.

 

[Guest]

Don't feel like you're alone with this problem, I have a customer with 5 PCs all running WinXPPro connected to a Win2k3 Server in a workgroup environment. I receive a call at least once every other week informing me that a machine is not reconnecting the mapped drives. The biggest headache I have is that it's an intermittent problem and can affect any machine at any time without warning. Yes, when the double click the "Red X'd" drive it reconnects without a problem. In addition, each PC uses the same log on credentials and all mapped drives were created with those credentials.

I have seen more than necessary postings regarding this issue, but I have NOT seen a solid answer. The first attempt I made at fixing this was to install WINS on the server and then ensure each NIC was configured with WINS and pointing to the server and that didn't work.

My next theory is to statically assign IP's to each NIC and turn off DHCP at the router connected to the Internet. Will post my results.

----- Bernie MCSE MCSA MCP wrote: -----

what i have found with network drives the username and
password of the mapped drives user name and password must
match on both machines and that should take care of your
problem.

 

[Peter R. Fletcher]

I think that it is a consistent and repeatable problem with XP,
particularly seen with (client) systems that run substantial amounts
of software (e.g. virus checkers) as _services_. In my experience,
booting the client system and waiting at the logon screen until all
disk activity has died down before logging in solves the problem, but
this requires user cooperation! I have not found a "hands off" way of
solving the problem. My interpretation of what is going on, which may
or may not be correct, is that XP gives sorting out its networking
connections a fairly low priority in implementing its much vaunted
"fast startup", so that setting up the networking links that are
required for mapping to work doesn't happen until quite late on in the
system boot process. If a user logs in as soon as the login screen
appears or (especially) if the system uses autologon, the user level
code which tries to map the drives runs before the system level
networking code that makes them available for mapping has completed.

This can be seen particularly strikingly if a subdirectory of a local
drive is shared and mapped as a (different) networked drive. If you
login too fast, you can be toldl that a networked drive that is
physically located on the local system is "not available"!

My XP pro workstation's mapped drives are not available
when the user first logs-in. We have WIN Server 2003;
Clicking on each mapped drive prompts them to become
available. Why don't the mapped drives connect at login?
This has been a problem I have seen posted many times
before, without a solid solution. Has this been addressed
with a good hot-fix yet? I would be very grateful for a
solution.
(e-mail address removed) MCSE CCNA

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher