flemingh
asked on
Unable to add computers to the DOMAIN
I am currently running Windows Server 2003, workstations are on XP/SP2. I was getting the error "Unable to logon due to domain controller could not be located". I have since taken workstation off of the domain and attempted to put it back on the domain with no success.
I am getting the error "DNS was successfully queried for the service location (SRV) resource reocrd used to locate a domain controller for domain <domain name removed>:
The query was for the SRV record for_ldap._tcp.dc._msdcs.<d
The follwoing domain controllers were identified by the query.
msqnpdc.<domain name removed>
msqnsdc.<domain name removed>
ccpn-mail.<domain name removed>
Common causes of this error include
-Host A records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
-- I have verified that the IP Addresses are correct.
-Domain controllers registered in DNS are not connected to the network or are not running.
-- I have verified that that controllers are running.
Have still been unable to add computers to the domain.
I am getting the error "DNS was successfully queried for the service location (SRV) resource reocrd used to locate a domain controller for domain <domain name removed>:
The query was for the SRV record for_ldap._tcp.dc._msdcs.<d
The follwoing domain controllers were identified by the query.
msqnpdc.<domain name removed>
msqnsdc.<domain name removed>
ccpn-mail.<domain name removed>
Common causes of this error include
-Host A records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
-- I have verified that the IP Addresses are correct.
-Domain controllers registered in DNS are not connected to the network or are not running.
-- I have verified that that controllers are running.
Have still been unable to add computers to the domain.
ASKER
We have checked the above however we continue to get the same errors
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are the machines that you are attempting to join to the domain seperated from the Domain Controller by a VPN tunnel, by any chance?
If that is the case, then I suggest that you use the full domain name (pacomccp.jtf.pacom.mil) during the JOIN DOMAIN process.
Thanks
JEEGO
If that is the case, then I suggest that you use the full domain name (pacomccp.jtf.pacom.mil) during the JOIN DOMAIN process.
Thanks
JEEGO
ASKER
The machines are connected to the network via cable, I have typed in the fully qualified name, and still unable to join the domain.
start --> run --> CMD
DCDIAG <enter>
http://technet2.microsoft.com/WindowsServer/en/Library/5237db58-a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true
DO YOU SEE THE NETLOGON DIRCTORY ON YOUR DC's????? Other things to check... make sure the the netlogon directory is being displayed on your DC's. to check Start --> Run--> \\servername\
On your DC's check for Event log ERRORs!!!
DCDIAG <enter>
http://technet2.microsoft.com/WindowsServer/en/Library/5237db58-a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true
DO YOU SEE THE NETLOGON DIRCTORY ON YOUR DC's????? Other things to check... make sure the the netlogon directory is being displayed on your DC's. to check Start --> Run--> \\servername\
On your DC's check for Event log ERRORs!!!
ASKER
Get time errors and also get the following error:
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down.
Warning: DcGetDcName(Time_Server) call failed, error 1355 A time server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(good_time_serv
A good time server could not be located.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down.
Warning: DcGetDcName(Time_Server) call failed, error 1355 A time server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(good_time_serv
A good time server could not be located.
ASKER
Another error I have showing Kerberos does not have a ticket for host/msqnpdc.pacomccp.jtf.
The Security System detected an authentication error for the server cifs/PDC. The failure code from authentication protocol Kerberos was
" There are currently no logon servers available to service the logon request.
The description for Event ID in Source W32Time cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE=flag to retrieve this description.
The Security System detected an authentication error for the server cifs/PDC. The failure code from authentication protocol Kerberos was
" There are currently no logon servers available to service the logon request.
The description for Event ID in Source W32Time cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE=flag to retrieve this description.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We are back up online. Able to add computers to the domain.
Ran DC Diag
did a W32tm /register
and rebooted.
Ran DC Diag
did a W32tm /register
and rebooted.
Server DC 1
NAme: ServerDC1
IP: 10.10.10.5
subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 10.10.10.5 or 127.0.0.1 <--- must point to itself and not to ISP DNS server
DNS 2: Some other internal DNS server in the internal domain ....recommended also to be in the same site if possible
Client IP settings
Name: Clientworkstation1
IP: 10.10.10.25
subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 10.10.10.5 <--- do not point to ISP ,...must point to local DNS server of the windows domain
DNS2: some other internal Windows 2003 DNS server....but not to domain.
Other things to check... make sure the the netlogon directory is being displayed on your DC's. to check Start --> Run--> \\servername\