can't join XP Pro workstation to domain

  • Thread starter Thread starter Steve Powell
  • Start date Start date
S

Steve Powell

An IBM Thinkpad which has been a domain computer for over
a year has started having problems related to logon
authentication to the domain: Trying to logon to the
domain generates a "domain controller not found" message.
Using a different hard drive in the same machine and
trying to join the domain generates basically the same
message,"an error occurred when DNS was queried for the
service location (SRV) resource record used to locate a
domain controller for domain abc. On the server: removed
entries for this computer from DHCP, DNS, and Active
Directory Users and Computers. When this laptop tries to
logon or join the domain, the following system event entry
is created: 1) The session setup from the computer LOUIS
failed because there is no trust account in the security
database for this computer. The name of the account
referenced in the security database is LOUIS$. Also, if I
configure this laptop as a DHCP client, it gets the
169.x.x.x default instead of what it should (6.2.2.x).
This all started happening when the laptop was blue-
screening due to a bad NIC driver. IBM support had the
customer rollback his system (via system restore) to a
point before he had ever joined the domain. That's when
the logon issues began. Is this a problem on the laptop
or the server or is there possibly some bad hardware?
 
if it's getting a 169 address that means it has a bad
network connectivity and it can't reach the DHCP server.
Can you ping a domain controller or the DHCP server? If
everyone else is working fine then 99% says its the
laptop. Maybe try a different NIC. Make sure the
physical connectivity is there before going to far.
 
If the client is getting a autonet address (169.x.x.x) then it isn't
getting on the network and therefore can't find a domain controller.
If you assign it a good IP address can you ping the domain
controller, router, and other machines on the network? If not then
you still have an issue with the network card or driver.

If you can ping find out why DHCP isn't working. Once the networking
problems are gone the domain problem may go away as well.


Tom Ausburne (MSFT)
Windows 2000 Directory Services
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Sorry folks, I forgot to mention in my original post that
I can ping the server by either ip address or by name
from this laptop. In the dhcp log from yesterday there
are several entries for this laptop where the dhcp lease
was renewed, released, etc... as we were
troubleshooting. So does that mean that the server is
giving the laptop a dhcp address but the laptop isn't
accepting it for some reason?
 
Well that's interesting that it can ping machines by
name. this tells me that it is getting either the dns or
wins server address from dhcp? unless they are
statically configured.

so every time you do the ipconfig /release then
ipconfig /renew you get a 169. address? what about when
you ipconfig /all, do you have all of the other info,
like dns and wins?
 
I've done a workaround to get the guy going again. I
wiped and reloaded the hard drive but I still couldn't
join the domain using the old machine account so I tried
joining under a different machine account, which worked
this time(before the wipe/reload that did not work). So
I don't understand how the workstation and server
authenticate with each other, but evidently something
there was fouled up. If anyone can explain to me how
that process works please reply to my email address:
(e-mail address removed). Thanks for all the advice!
 
Back
Top