Login/Drive mapping error

[Ryan McGowan]

2 W2K SP3 DCs, 4 Shares (2 on DC1, 2 on DC2), XP clients.

When XP client logs in, the shares from DC2 are always
mapped, no matter what the authenticating DC is.

However, the shares from DC1 sometimes do not map through
the login script. It is using a simple net use command,
after login, this command runs fine.

Debugging shows a "System error 53 has occurred. The
network path was not found" message.

The scripts are running via group policy, but it still
occurs if you include the script attached to the user.

Summary: Why during login, can the client not access the
shares on DC1, but it can access them after login?

Any thoughts/suggestions/fixes?

 

[Ryan McGowan]

Yeah, for sure. I'm going to try and change it to
\\IP\share name to rule out some sort of translation
issue.

But I don't want to leave it that way...

 

[Philip Nunn]

Are you sure the GPO's are being replicated between your DC's? You may
check your FRS.

Philip Nunn

 

[Ryan McGowan]

After checking that they could map via IP addresses with
no problems, I did an ipconfig /all on the clients (I
should have done this at the start).

As well as the LAN connection the Compaq machine had a
WAN driver adapter in there as well.

So the reason it worked sometimes and not others is that
it would use the LAN for some mappings and the WAN
adapter for others.

I disabled the WAN adapter (not used) and unbound the
protocols.

This fixed the problem.