XP Home login OK to NT4 domain, not so OK to W2003R2 domain

[hjacobson]

Hello,

I've searched this pbm w/o success so:

I'm migrating my school's NT4 domain to Windows Server 2003 R2. So far
3 of 4 servers are upgraded from NT4 to W2003R2 or replaced. XP
professional workstations on network function OK with migrated DHCP,
DNS, WINS, shares, login scripts.

The problem is with one teacher's personally owned laptop running XP
Home. It so happens her local machine ID and password is identical to
her domain ID and password. The laptop successfully maps to shares on
the remaining NT4 server but the process fails when attempting to map
to shares on a server upgraded to W2003R2.

In both cases we 'connect using a different user name',
<DomainName>\<DomainID>. This succeeds with the NT4 server but fails
with the W2003R2 server. The error message returned is 'incorrect
username or password'.

The map is successful when I use a domain administrator ID or a test
user's ID, of course both different than her local laptop ID. So I
think the laptop is configured OK.

I suspect this is a syntax problem in 'connect using a different user
name', however use of variants of domain name (e.g., DomainName.org)
are unsuccessful.

What to do?

Harry

P.S. I think renaming her local ID may succeed but I'd like to get her
laptop to successfully login with her existing ID.

 

[Lanwench [MVP - Exchange]]

In

Hello,

I've searched this pbm w/o success so:

I'm migrating my school's NT4 domain to Windows Server 2003 R2. So far
3 of 4 servers are upgraded from NT4 to W2003R2 or replaced. XP
professional workstations on network function OK with migrated DHCP,
DNS, WINS, shares, login scripts.

The problem is with one teacher's personally owned laptop running XP
Home. It so happens her local machine ID and password is identical to
her domain ID and password. The laptop successfully maps to shares on
the remaining NT4 server but the process fails when attempting to map
to shares on a server upgraded to W2003R2.

In both cases we 'connect using a different user name',
<DomainName>\<DomainID>. This succeeds with the NT4 server but fails
with the W2003R2 server. The error message returned is 'incorrect
username or password'.

The map is successful when I use a domain administrator ID or a test
user's ID, of course both different than her local laptop ID. So I
think the laptop is configured OK.

I suspect this is a syntax problem in 'connect using a different user
name', however use of variants of domain name (e.g., DomainName.org)
are unsuccessful.

What to do?

Harry

P.S. I think renaming her local ID may succeed but I'd like to get her
laptop to successfully login with her existing ID.

You don't have any NT DCs left, do you? The NT box is just a file server?

Am thinking it might be helpful if you first do a net use * /del to make
sure there are no remembered connections, and then try again.

I'm not familiar with R2 stuff, so I'm not sure what might've changed there,
but I would probably have her connect using a batch file script anyway - put
it on her desktop or in her startup folder.

net use * /del
net use x: \\servername\sharename userOMAIN\username password
/persistent:no

.....or
net use x: \\servername\sharename userOMAIN\username /persistent:no
(note that she'll be prompted for her password)

....or
net use x: \\servername\sharename /persistent:no userOMAIN\username
password

(I can't remember if the /persistent:no needs to go before or after the
credentials)

Of course, it'd be very nice if you could upgrade her machine to XP Pro and
join it to the domain, but maybe she doesn't want that on her personal
laptop.