Annoyances.org
Home » Windows Server 2003 Discussion Forum » Message 1235107267 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: A Domain Controller for the Domain XXX Could Not be Contacted
Thursday, February 19, 2009 at 9:21 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by appleoddity (2369 messages posted)


Hi.. FIrst of all, when you post your message make sure you check the option to "preserve spacing" so that it doesn't look so jumbled up and we can read it. Now, you have made some very basic and fundamental mistakes on how you configured your network. And yes, you are right, this is a DNS issue. Several things need to change and I am not going to tell you step by step how to do this because this is not a training forum, and the information is well documented elsewhere. However, I will tell you what needs to be done. You need to disable DHCP on your router. It is currently enabled and is unable to give your computers the proper IP information. You need to setup your server with a static IP address, not an automatically configured one. Lets say, for these purposes, you make the server have an IP address of 192.168.1.200. It shouls also have a subnet of 255.255.255.0, gateway of 192.1681.1, and DNS server of 192.168.1.200. (DNS points to itself). You need to enable the DHCP server on the server to replace the router's DHCP server. It should have options turned on that give out a range of IP addresses... Lets say for these purposes you assign a range of 192.168.1.100-192.168.1.150 to be available. The subnet should be 255.255.255.0. You also need to set the "router" option in DHCP to be 192.168.1.1. And the DNS or Name Server setting to be 192.168.1.200. Now, you need to enable the DNS server on your windows server station. It needs to have a forwarder configured that point to 192.168.1.1. Now, reboot the windows workstations so they get the new IP information and your domain will function properly. To sum things up: In order for a windows domain to function properly all workstations (and the server) must point to the server for DNS information, if the dns request is for an external website, the windows DNS server will forward the request to your router. The new IP address information on your workstations should look similar to this when you get done: IP: 192.168.1.1xx, subnet 255.255.255.0, GW 192.168.1.1, and DNS 192.168.1.200. This is the absolute most basic first step to any domain setup and you would do yourself a huge favor by getting a book on setting this kind of thing up so you understand why things work the way they do.




Written in response to:
A Domain Controller for the Domain XXX Could Not be Contacted (stevetilsed: Wednesday, February 11, 2009 at 1:27 pm)

There are presently no replies to this message.

All messages in this thread [show all]
-A Domain Controller for the Domain XXX Could Not be Contacted (stevetilsed: Wed, Feb 11, 2009, 1:27 pm)
*re: A Domain Controller for the Domain XXX Could Not be Contacted (appleoddity: Thu, Feb 19, 2009, 9:21 pm)
Return to the Windows Server 2003 Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.