Annoyances.org
Home » Windows Server 2003 Discussion Forum » Message 1234387670 » Entire Thread Search | Help | Home
  
A Domain Controller for the Domain XXX Could Not be Contacted
Showing all messages in thread #1234387670
Windows Server 2003 Annoyances Discussion Forum


The following are all of the messages in this thread (2 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
A Domain Controller for the Domain XXX Could Not be Contacted
Wednesday, February 11, 2009 at 1:27 pm
Posted by stevetilsed (1 messages posted)

Hi all, I’m having issues adding one of my clients to a test domain that I have set up. Error: A domain controller for the domain tilsed could not be contacted Path used: Right click my comp etc etc. Your have to bare with me on this one I am self teaching myself (which is probably not the best) I have the following, [b]D link route containing a 4port switch.[/b] [quote]IP Address: 192.168.1.1 Netmask: 255.255.255.0 Default Gateway: 212.74.111.194 Host Name: mygateway Domain name: ar7 [/quote] [b]Windows server 2003 R2[/b] [quote] C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : tilsed Primary Dns Suffix . . . . . . . : tilsed.com Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : tilsed.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-1B-B9-A5-BE-46 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.4 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 Lease Obtained. . . . . . . . . . : 11 February 2009 20:26:11 Lease Expires . . . . . . . . . . : 11 February 2009 21:26:11 [/quote] [b]Win Xp prof[/b] [quote] C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : right Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-50-04-4B-01-96 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.6 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 [/quote] Background – I had a domain during my test setup with I have decided to reinstall windows server over the top and start again as I was not happy with some of it. - Both machines have windows firewall disabled (router has firewall but this worked before) - DHCP is not enabled on the server as the router takes care of this - The computers are both wired to the router (the cables have not moved and the XP client was added to the domain before) - Upnp is enabled on the router - The server can pin the IP address of the workstation but not the host name - The workstation can ping both the IP address and the host name - Both machines can ping the servers IP - Both machines can access the internet I have a feeling this is a DNS issue? Please please please provide some help if you have any ideas before I give up. Please also bare in mind im not the most tech savy and currently self teaching so don’t worry about sounding patronising. [b]Thanks[/b] in advance, please ask if you need any more information.

[Reply or follow-up to this message]

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
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.

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
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.