Question

Locked

Need assistance: unable to join workstations to win 2003 domain: DNS Issue

By jason.helm ·
Not sure if this is a domain controller issue or a DNS issue, but for some reason I cannot get my workstations to join my domain. My DC and my Exchange server are the same, and I have DNS running on this server as well. I can get email perfectly (though outlook 2007 cannot seem to find the server for the out of office assistant) and can access any and all shares on the server, ping by name and by IP.
Below is what I get when I do a DCDIAG on the server ( sorry its long):

C:\Documents and Settings\jason.LIGHTHOUSE>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MAIL
Starting test: Connectivity
The host d7656a0c-ec8f-431b-a213-0d7659a7521d._msdcs.lighthouse.local c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(d7656a0c-ec8f-431b-a213-0d7659a7521d._msdcs.lighthouse.local)
couldn't be resolved, the server name (Mail.lighthouse.local) resolved
to the IP address (192.168.2.51) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... MAIL failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MAIL
Skipping all tests, because server MAIL 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 : lighthouse
Starting test: CrossRefValidation
......................... lighthouse passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... lighthouse passed test CheckSDRefDom

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

C:\Documents and Settings\jason.LIGHTHOUSE>


I am guessing that its that first part that is killing me but for the life of e I cant figure out how to resolve it. Any ideas?

This conversation is currently closed to new comments.

73 total posts (Page 1 of 8)   01 | 02 | 03 | 04 | 05   Next
| Thread display: Collapse - | Expand +

All Answers

Collapse -

DNS

by shasca In reply to Need assistance: unable t ...

Yep the error says it's a DNS problem. Any possibility it's an IP Conflict? How big of a network, number of other PC's etc.? Do you static everything? You didn't say if you have DHCP enabled? Any other clients not communicating with the Domain?

Collapse -

dns...

by jason.helm In reply to DNS

workstations are running dhcp from our router, and they server ips are not included with the DHCP scope. Server IPs ( it has 2) are static and dns points back to itself. None of my workstations can join the domain, have about 35

Thank you for the prompt reply.

Collapse -

workstations

by shasca In reply to dns...

What type error at the workstations when attempting to join?

Any possibility the DNS has an IP conflict? The error says "unreachable".

This would cause the workstations to fail joining, as they would not be able to find the comain controller through DNS.

Collapse -

error msg

by jason.helm In reply to workstations

Error i am getting is this, AFTER it prompts me for the user name/password authorized to add computers to the domain:
The following error occurred while attempting to join the domain "lighthouse":
The specified domain either does not exist or could not be contacted

Collapse -

DNS

by shasca In reply to error msg

Do you have any other DNS issues? can you browse the internet etc.?

You did say you checked the DNS entry for the DC?

Collapse -

dns

by jason.helm In reply to DNS

No other DNS issues that I know of. all machines can browse the internet just fine. I checked the DNS entry, and looks fine to me. though i will admit that i am not a DNS expert at all. Kinda teaching my self as i go along. What information would you need to see to know if i have it set properly or missing something?

Collapse -

Re: DNS

by christianshiflet In reply to dns...

The router that is running DHCP: is it issuing your internal DNS servers to clients or the ISP DNS servers?

Collapse -

re: dns

by jason.helm In reply to Re: DNS

Router is providing the internal DNS server address, which is running on the same server as the Domain.

Good to hear from you sir, I was wondering if you would have any thoughts on this! Thank you!

Collapse -

Re: DNS

by christianshiflet In reply to re: dns

Ya, I haven't been around much. As for your issue, check CG IT's response below. I think it will point you in the right direction.

Collapse -

DNS problems.

by CG IT In reply to Need assistance: unable t ...

This is your problem.

lighthouse.local
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc

you need to go into your DNS MMC and test your DNS server with simple query and recursive query tests for your domain lighthouse.local

Also check that DNS service is actually running and that your SOA records reflect the correct domain and A records. Verify that your DC server A record has the the same IP address as the DC server NIC address [static address]and that they are all on the same subnet [IP address and subnet mask].

Can not resolve the domain name typically means that the workstation DNS server address isn't the correct one or that DNS records have a different IP address for the DC or that there is no record for it.

Example: If your DC server for the domain lighthouse.local is named Mail and has an IP address 192.168.2.1 then there should be a record in DNS that say Mail = 192.168.2.1

Workstations then would have for the first listed DNS server as 192.168.2.1.

make sure that you use the entire domain name when trying to join the workstation to the domain. if the domain name is lighthouse.local you type that in the domain box.

Back to Networks Forum
73 total posts (Page 1 of 8)   01 | 02 | 03 | 04 | 05   Next

Related Forums