Question Locked

Cannot Join a PC to a Domain

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just built a new PC and was trying to join it to the domain, and it says it cannot locate the domain on the network. I also cannot browse to it from the run command by typing the network path, but using the IP address I can view the shared resources. I had noticed earlier in the month that when looking at My Network Places under the CLASSICEQUINE domain, that the server, CEEFS1, doesn't appear in the list. I ran dcdiag on the server and this is the result:

C:\Documents and Settings\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\CEEFS1
Starting test: Connectivity
The host c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.loca
l could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.local)
couldn't be resolved, the server name (CEEFS1.ClassicEquine.local)
resolved to the IP address (192.168.110.7) and was pingable. Check
that the IP address is registered correctly with the DNS server.
......................... CEEFS1 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\CEEFS1
Skipping all tests, because server CEEFS1 is
not responding to directory service requests

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : ClassicEquine
Starting test: CrossRefValidation
......................... ClassicEquine passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ClassicEquine passed test CheckSDRefDom

Running enterprise tests on : ClassicEquine.local
Starting test: Intersite
......................... ClassicEquine.local passed test Intersite
Starting test: FsmoCheck
......................... ClassicEquine.local passed test FsmoCheck

16 replies

by bart777

It appears that you have some AD problems.
I'm wondering if you have ever had to rebuild the DC. From that DCDIAG report the server is trying to find a server that no longer exists. That's what that SID is.
First I would look into AD Sites and services to see if there is a bad replication partner.
Next check DNS for the same.
Verify that your current DC is a global catalog server.
Verify that all of the FSMO roles are set to a valid server.

Let us know.

by dlester

No and to be real honest I don't know what previous IT people have done to this domain. I believe there was an old classic-equine0 domain at one time, but i dont know for sure. DNS is a mess i think, seems to me a lot of entries are missing in the _msdcs.Classicequine.local zone, but I have tried to re-enter entries but to no avail.

by dlester

none of our existing machines are having this issue. All of them can see the server from run by typing \\ceefs1, and can access the domain. The other strange thing is the server cannot ping the IP of the machine that will not add to the domain.

by cg it

this host : c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.loca
l is not a valid host name in DNS [meaning it doesn't resolve to an IP address].

this host: CEEFS1.ClassicEquine.local is a valid host in DNS [meaning it resolves to the 192.168.110.7 address].

So for the DC in question, what is it's name and is there a record in DNS that says DC Name = IP address?

by dlester

This is the first thing i checked. See what is strange is that there is an IP address associated with CEEFS1 (the DC) on the DNS server, which is on the same server ans AD. Another strange thing is that i can ping the server name from the PC that will not join successfully. I took a screenshot of our DNS configuration if that will help, let me know and ill post it

by cg it

don't confuse AD with DNS.

How many servers you got? how many are DCs?

In DNS, are your servers including DCs listed with an A record? If not, then there ya go. If DNS can not resolve a name to IP address then your \\servername\C$ or whatever share your trying to connect to won't resolve [you could use WINS or even a host file like in workgroups but the point is something has to resolve the name to an address].

by dlester

We only have one server, its the DC and runs DNS, and the server has an A record for itself in DNS

by bob from califon

I am puzzled by the fact that you can't ping the new machine by address from the server.

Are all of the IP settings correct on the machine that you want to add to the Domain? Especially check the gateway address and the net mask.

You really need a WINS server or host file.

Bob

by dlester

The Machine is getting the correct settings from DHCP, and it is in the DHCP client list, but it does not report to the DNS server at all, plus I did finally get the server to ping the machine, when i disabled windows firewall. The strange thing is I have built two other machines identical to this and those joined right in without disabling.

by cg it

ok this is your problem:

The host c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.loca
l could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.local)
couldn't be resolved, the server name (CEEFS1.ClassicEquine.local)
resolved to the IP address (192.168.110.7) and was pingable. Check
that the IP address is registered correctly with the DNS server

So DNS is saying the host c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.loca
l doesn't have a record in DNS.

DNS does say it has a record for the server name (CEEFS1.ClassicEquine.local)

And also says that it resolved to the IP address (192.168.110.7) and was pingable.

So, clients are looking for a DC in which to authenticate to and are getting this host c328fb9a-0e6e-494e-97e9-7e3323dfef24._msdcs.ClassicEquine.loca
l which doesn't have a record in DNS therefore clients can't find a DC in which to authenticate to so you can't join the client computer to the domain.

Give us a list of what's in your SOA record.
That might shed light on what the problem is.

by dlester

Ok from what I see, my SOA only shows the one server, ceefs1.classicequine.local. It has the hostmaster.classicequine.local as well, but it is the responsible person data. I can post screenshots to flickr if that would help, im just at a loss now as to what to do. I know its not a local machine issue, I just wiped the drive and re installed windows and the drivers, and still yet i get the same errors, it also still does not resolve the CEEFS1 name to the correct IP, but if i navigate via IP to the server, it can successfully access its data. Im just lost! The only other hint I can offer is that this is the first machine we have tried to join to the domain since my boss installed RRAS and then promptly uninstalled it since the network stopped functioning, since then the server, CEEFS1, has not shown up in the directory under my network places as a browsable machine.

by cg it

DNS is simply resolving a name to an address.

If your server name is CEEFS1 and it's IP address is 192.168.110.1 then there should be an A record in DNS that say CEEFS1 = 192.168.110.1.

note: servers typically have static addresses that do not change. This is so that DHCP doesn't decide to change a server address and DNS doesn't get that info, users looking for that server by name can't find it.

So what is the IP address of the server in question? What is the name of the server in question? Once you have those 2 pieces of information, then you can check DNS and see if there is an A record that says server name = IP address. If not you have to create it.

If this is not the problem then a solution is a little more complex. Like is the server in the domain that DNS is authoritative for that domain zone? etc.

RRAS doesn't have anything to do with it.

by cg it

it had to come from somewhere? if you try to join the domain from the workstation using the Network Wizard from the computer name properties page in System Properties of control panel, then you just enter credentials and the DNS servers listed in the NIC properties page would resolve [hopefully they are your CEEFS1 DNS server address of 192.168.110.1 [or whatever the IP address is].

If you have any other DNS server than yours listed, then they won't be able to resolve.

by dlester

The A record for the server is in place already, every other client on the network can resolve the name.

Server: CEEFS1
IP: 192.168.110.7

by dlester

Ok, so im not sure what changed overnight, but my DNS system refreshed itself and added values that were not there yesterday, and now somehow the client joined the domain...not sure what did it though...but the server still doesnt show up in the My Network Places

This discussion is closed to new replies.