Heres a Hard one!!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

OS: Windows XP Pr
Server: Windows Server 200

Active Directory and DNS look fine. nslookup returns the correct info. Netdiag looks good

Here is a breakdown of what happened. Installed a program which corrupted the TCP/IP protocol. While troubleshooting this issue, I removed the computer from the domain. After reinstalling the TCP/IP protocol I went to join the computer to the domain once again. Here is what I get when attempting to do so


DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain domain.com

The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.co

The following domain controllers were identified by the query

server1.domain.co

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

- Domain controllers registered in DNS are not connected to the network or are not running

For information about correcting this problem, click Help

I really do not want to format this system so any help will be greatly appreciated. Thanks in advance
 
Is there an A record for server1 in the forward lookup zone? The error says
there isn't.


Shane said:
OS: Windows XP Pro
Server: Windows Server 2003

Active Directory and DNS look fine. nslookup returns the correct info. Netdiag looks good.

Here is a breakdown of what happened. Installed a program which corrupted
the TCP/IP protocol. While troubleshooting this issue, I removed the
computer from the domain. After reinstalling the TCP/IP protocol I went to
join the computer to the domain once again. Here is what I get when
attempting to do so.
DNS was successfully queried for the service location (SRV) resource
record used to locate a domain controller for domain domain.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.com

The following domain controllers were identified by the query:

server1.domain.com

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.
- Domain controllers registered in DNS are not connected to the network or are not running.

For information about correcting this problem, click Help.

I really do not want to format this system so any help will be greatly
appreciated. Thanks in advance
 
You're right this is a hard one! So tell us, what are you trying to achieve
(or should we just guess?)
Are the ppl responding to this newsgroup just supposed to guess what you are
trying to achieve. When will you posters learn that we really are not
miracle workers (but do aspire!) and would appreciate a little help from
you.... (tell us what you want)

Stephen

Shane said:
OS: Windows XP Pro
Server: Windows Server 2003

Active Directory and DNS look fine. nslookup returns the correct info. Netdiag looks good.

Here is a breakdown of what happened. Installed a program which corrupted
the TCP/IP protocol. While troubleshooting this issue, I removed the
computer from the domain. After reinstalling the TCP/IP protocol I went to
join the computer to the domain once again. Here is what I get when
attempting to do so.
DNS was successfully queried for the service location (SRV) resource
record used to locate a domain controller for domain domain.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.com

The following domain controllers were identified by the query:

server1.domain.com

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.
- Domain controllers registered in DNS are not connected to the network or are not running.

For information about correcting this problem, click Help.

I really do not want to format this system so any help will be greatly
appreciated. Thanks in advance
 
Rob

Yes, there is an A record for Server1. This is what is so confusing about this issue. Also tested another machine and removed it from the domain and added it back in. No problems

Stephen

I thought it was clear what I was trying to accomplish. ADD THE COMPUTER TO THE DOMAIN. Maybe read more carefully next time.
 
Back
Top