A domain controller for the domain abc.local could not be contacted
Greetings,
I am trying to join a computer to my new domain on a Windows Small Business
Server 2003 and keep getting the following error: A domain controller for
the domain abc.local could not be contacted.
After reviewing the error details I feel I'm close to solving the problem
(I'm pretty sure it's the Host (A) record not being set right), I just don't
know where to look to actually fix the problem.
Does anyone have any suggestions on where to look?
Thanks,
Chris
Error details:
Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain grendelcompanies.local:
The query was for the SRV record for _ldap._tcp.dc._msdcs.abc.local
The following domain controllers were identified by the query:
grendel.grendelcompanies.local
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.
Re: A domain controller for the domain abc.local could not be contacted
Make sure to check that this prot is opened. It helped me.
Port Number: 389
TCP / UDP: UDP
Delivery: No
Protocol / Name: ldap
Port Description: Lightweight Directory Access Protocol. LDAP server's port, an adaptation of x.500 dir std. Through it, LDAP clients access central dir to retrieve, add, and modify info. Examples: Database for PKI systems. - Address book for mail & personnel progs. - Internet Directory Service that tracks users of collaborative apps (chat, video, audio, etc). Would track who is on-line, their IP, and data about user. Used by Win2000 Active Directory. SSL version at TCP 636. Security Concerns: Valuable source of user info used in attacks; excellent target for DOS attack.