Xp pro client unable to join 2003 AD domain

Running through the wizard to join the client to the 2003 AD domain, it takes ages to think about joining the domain and comes up with a message saying "the server is unable to process this request" or something along those lines. It doesn't give me a event id, nor does it comes up in event viewer from what i can see. I've played with the settings for DNS, etc in 2003 and  have used the nslookup function for it come up with:

" *** Can't find server name for address 192.168.30.9: Non-existent domain
Default Server:  UnKnown
Address:  192.168.30.9

>"

Any ideas? I've had a look around some of the other threads, but i'm a bit stumped on exactly what to do?

Many Thanks,

Mike
mikehenry85Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jay_Jay70Commented:
Hi mikehenry85,
 
make sure the client is pointing its dns settings to the server for one and then try nslookup again - try it also from the server and make sure there is an entry in DNS for the client if nslookup fails

check firewalls are disabled on the client

Cheers!
0
mikehenry85Author Commented:
i've tried it on both, the client is set up to look at the dns server, all the firewalls, are not activated, they were the first things i pulled off. As for the DNS entry for the client? Should i just enter it's IP into the name server records?

Cheers again!
0
rcheinCommented:
This may not be it at all, but make sure you client is with-in five minutes of the time of the server.  If the time is off there are authentication problems.  Probably not the problem with the description you gave, but always the first thing I check when a machine won't join.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

mikehenry85Author Commented:
Hi rchein, time is definately not off, looking at both clocks with both the server and client next to each other they're a second, maybe two seconds out, between each other. Any other ideas?
0
MazaraatCommented:
do an IPconfig /all from both the PC and the server...post here so we can make sure the settings are correct
0
acpressCommented:
I've had this happen before.  First, to check your connectivity, ping the Domain Controller by name (not IP Address).  Ping the DNS server, if different then the Domain Controller.

After you establish connectivity join the workstation to a Workgroup and reboot.
Change the NetBIOS name to something unique, then try to rejoin the Domain.  
0
mikehenry85Author Commented:
Ipconfig for the server is as follows:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : server1
   Primary Dns Suffix  . . . . . . . : manchester.acrison.com
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : manchester.acrison.com
                                       acrison.com

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-11-43-EC-2E-E7
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.30.9
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.30.254
   DNS Servers . . . . . . . . . . . : 192.168.30.9

Ipconfig for the client is as follows:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : nb06
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Network of Xircom 10/100 Network + 56k Modem PC Card
   Physical Address. . . . . . . . . : 00-10-A4-B5-6D-FF
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.30.106
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.30.254
   DNS Servers . . . . . . . . . . . : 192.168.30.9
                                               195.74.102.147
0
mikehenry85Author Commented:
Ok, i've just tried pinging the DC, which is also the DNS server using it's name, server1. I've tried pinging this off the client machine and for some reason the resolution of 'server1' is coming up with the ip of 192.168.30.2, which to my knowledge is an ip addres that is not in use?! Using the actual ip address to ping one another, it works, so that in turn should establish the connectivity right? As to changing the NETBIOS name? Am i changing this on the client or server?

Cheers!
0
MazaraatCommented:
check if you have something configured in the hosts or lmhosts file they are in the 'c:\windows\system32\drivers\etc' folder
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MazaraatCommented:
Then check DNS (forward and reverse lookup) to see if there is an old record that has a different IP associated with that dns server name
0
MazaraatCommented:
Also, your clients should be pointing to only internal DNS servers(only your DNS server should be pointing to the ISP, in the forwarders tab):

DNS Servers . . . . . . . . . . . : 192.168.30.9
                                               195.74.102.147<------ISP??
0
acpressCommented:
The post from Mazaraat is correct regarding pointing the client pc's to the internal DNS server.  Regarding changing the NetBIOS name, I was referring to the client pc, not the server.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.