Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows Server 2003 / DNS / February 2010

Tip: Looking for answers? Try searching our database.

A domain controller for the domain abc.local could not be contacted

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris Hayes - 30 Jun 2007 15:28 GMT
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.
Chris Hayes - 30 Jun 2007 15:50 GMT
I found out where to add the Host (A) record and that didn't fix it... any
other ideas?

Chris

> Greetings,
>
[quoted text clipped - 37 lines]
>
> For information about correcting this problem, click Help.
Chris Hayes - 30 Jun 2007 15:56 GMT
Problem found, it was on the client that was trying to attach the Grisoft
firewall was active and preventing the necessary communication.

Sorry for the false alarm... (stupid firewalls).

Chris

>I found out where to add the Host (A) record and that didn't fix it... any
>other ideas?
[quoted text clipped - 42 lines]
>>
>> For information about correcting this problem, click Help.
tr777ple - 17 Feb 2010 18:53 GMT
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'
port, an adaptation of x.500 dir std. Through it, LDAP clients acces
central dir to retrieve, add, and modify info. Examples: Database fo
PKI systems. - Address book for mail & personnel progs. - Interne
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. Securit
Concerns: Valuable source of user info used in attacks; excellent targe
for DOS attack

--
tr777pl

http://forums.techarena.i
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.