|
|
|
re: domain controller could not be contacted
Friday, July 11, 2008 at 6:52 am
Windows Server 2003 Annoyances Discussion Forum
Posted by appleoddity
(1643 messages posted)
This is usually a DNS issue.
You must make sure DNS is active and AD integrated. You must also make sure no firewalls
are blocking the communications.
On a vanilla system, you would begin the installation of AD and it would automatically
tell you about installing DNS and configuring it.
All the PCs on the domain should have their DNS settings set to the IP address of
the domain controller.
Go to a command prompt on one of the PCs, and type 'nslookup' -> then type in the
name of one of your PCs.
Something like this:
C:>nslookup
> default server: xxxxxxxx
> Address: xxx.xxx.xxx.xxx
> mypcname
> Server: [192.168.100.1]
> Address: 192.168.100.1
>
> authoritative answer:
> Name: mypcname
> Addresses: 192.168.100.54
If DNS is working properly you will get output similiar to the above. If it fails
you will see DNS request timed out errors, or non-existent domain.
This does not guarantee that AD is working properly. But, it shows that DNS is at
least installed and functioning.
|
All messages in this thread [show all]
 |  | re: domain controller could not be contacted (appleoddity: Fri, Jul 11, 2008, 6:52 am) |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
|
|
