Home All Groups Group Topic Archive Search About

Unable to join xp client to server2003

Author
19 Aug 2006 11:50 PM
Reh
Hi all

This is the first post I am making on the site, after having tried
everything else (and now at the verge of pulling my hair out!).

Basically I have 2 clients and a server.  The server is 2003 Enterprise
edition, acting as the only DC within the domain.  It is also configured as a
DNS server, however the DHCP is done by the router.  All machines have
dynamic ip addresses except for the server, statically assigned.

The clients are set to use the server as the dns server, configured in the
NIC settings, and are able to use this successsfuly.

The problem - I am unable to add the clients to the domain.  I right click
My computer, go to properties, click on the computer name tab, click the
option box for Domain, enter the domain name, when prompted for user
credentials I enter the following:

domain\administrator followed by the password.  I get the egg timer, and
after some time I get the error message:

"Logon failure: unknown user name or bad password".

So far I have done the following:

Checked and reset the password
Created another admin account and tried that
confimed ping bothways, using both ip and hostname
checked event viewer for errors
tried the whole process from a different xp client machine
Added the computer account, and checked the 'manage by' setting is set to
Administrator
Tried entering the wrong password, get the same error.
Tried entering the username without the domain name prefix

Not having any joy whatsoever.  Finally to shed further light, I have tried
the net use command to connect to the root share on the server, and receive
the same error.  Finally I have confirmed that the 'Kerberos Key Distribution
Center' service is running.

The ip on the server is 192.168.2.2
The ip on the router is 192.168.2.1
the ip on the client xp  machine is 192.168.2.4, with the dns server set to
192.168.2.2.
The xp is running pro with sp2.  Firewall is turned off, with the guest
account also turned off. (I did try enabling this account to see if it made
any difference!)

The server is 2003 Enterprise edition, with all security patches and updates
applied.  No group policy is currently enforced, and the administrator
account is a member of the following groups:

Administrators, Domain Admins, Domain Users, Enterprise Admins, Group Policy
Creator Owners, and Schema Admins.

I think I've pretty much covered everything (i hope).

Any help whatsoever from anyone would be MOST appreciated.

Many thanks in advance.

Author
20 Aug 2006 1:41 AM
Chuck
On Sat, 19 Aug 2006 16:50:01 -0700, Reh <R**@discussions.microsoft.com> wrote:

Show quoteHide quote
>Hi all
>
>This is the first post I am making on the site, after having tried
>everything else (and now at the verge of pulling my hair out!).
>
>Basically I have 2 clients and a server.  The server is 2003 Enterprise
>edition, acting as the only DC within the domain.  It is also configured as a
>DNS server, however the DHCP is done by the router.  All machines have
>dynamic ip addresses except for the server, statically assigned.
>
>The clients are set to use the server as the dns server, configured in the
>NIC settings, and are able to use this successsfuly.
>
>The problem - I am unable to add the clients to the domain.  I right click
>My computer, go to properties, click on the computer name tab, click the
>option box for Domain, enter the domain name, when prompted for user
>credentials I enter the following:
>
>domain\administrator followed by the password.  I get the egg timer, and
>after some time I get the error message:
>
>"Logon failure: unknown user name or bad password".
>
>So far I have done the following:
>
>Checked and reset the password
>Created another admin account and tried that
>confimed ping bothways, using both ip and hostname
>checked event viewer for errors
>tried the whole process from a different xp client machine
>Added the computer account, and checked the 'manage by' setting is set to
>Administrator
>Tried entering the wrong password, get the same error.
>Tried entering the username without the domain name prefix
>
>Not having any joy whatsoever.  Finally to shed further light, I have tried
>the net use command to connect to the root share on the server, and receive
>the same error.  Finally I have confirmed that the 'Kerberos Key Distribution
>Center' service is running.
>
>The ip on the server is 192.168.2.2
>The ip on the router is 192.168.2.1
>the ip on the client xp  machine is 192.168.2.4, with the dns server set to
>192.168.2.2.
>The xp is running pro with sp2.  Firewall is turned off, with the guest
>account also turned off. (I did try enabling this account to see if it made
>any difference!)
>
>The server is 2003 Enterprise edition, with all security patches and updates
>applied.  No group policy is currently enforced, and the administrator
>account is a member of the following groups:
>
>Administrators, Domain Admins, Domain Users, Enterprise Admins, Group Policy
>Creator Owners, and Schema Admins.
>
>I think I've pretty much covered everything (i hope).
>
>Any help whatsoever from anyone would be MOST appreciated.
>
>Many thanks in advance.

Regardless of the ability to ping the server by its NetBIOS name (I'd bet), you
have specific settings to make in the DNS setup.  Be sure to make the right
settings in the DHCP server too.  I've written up these settings in my article.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My        email         is          AT         DOT
   actual       address    pchuck       mvps        org.
Author
20 Aug 2006 9:07 AM
Ian
- although a DNS fault wouldn't account for NET USE failing, provided the
hostname is being resolved this should work.

Also worth trying

NET USE  \\192.168.2.2\sharename /user:domain\username password

If this works, then it _is_ a name-resolution issue.

If this doesn't work, I'm inclined to think that there might be something
wrong with the server's setup, perhaps in the TCP/IP stack, and reinstalling
these components might be the way to go.

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

An alternative approach to XP network logon -  http://mylogon.net