From a certain workstation I can't join the doman, while from a different workstation I can.
Meanwhile, from the defective workstation I can ping the server using its FULLY Qualified Domain Name. However, the IP address it comes back with is the wrong one. (I have NO IDEA where the wrong address comes from.)
From the defective workstation, I can see the server in My Network Places, I can connect to it using a domain username, and I can see and access the files on it. I just can't connect to the domain.
I think the problem may have to do with how I set up DNS.
Following, I have included:
A. Evidence of the IP address confusion
B. Evidence of the error message produced when I try to join the domain from this machine
C. A clue - Error message from the Event Viewer that there is a redundant DNS zone laying around
A. Evidence of the IP address confusion:
Pinging server1.godslake.local.com [184.108.40.206] with 32 bytes of data:
Reply from 220.127.116.11: bytes=32 time=698ms TTL=107
(I have NO IDEA where it's getting that 18.104.22.168 IP address!)
Pinging server1 [192.168.0.9] with 32 bytes of data:
Reply from 192.168.0.9: bytes=32 time<1ms TTL=128
(192.168.0.9 is the correct IP address for Server1).
B. More evidence - Here's the error message I get when trying to join the domain:
Error when trying to join the domain:
An error occurred when DNS was queried for the service location (SRV)
resource record used to locate an Active Directory Domain Controller
for domain GodsLake.local.com.
The error was: "No records found for given DNS query."
(error code 0x0000251D DNS_INFO_NO_RECORDS)
The query was for the SRV record for _ldap._tcp.dc._msdcs.GodsLake.local.com
C. Clue - There may be a redundant DNS zone laying around:
From the DNS Event Viewer: Event ID - 4515 -
The zone GodsLake.local.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.GodsLake.local.com. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.