A Domain Controller for the Domain XXX Could Not be Contacted

[stevetilsed]

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,

D link route containing a 4port switch.

IP Address: 192.168.1.1
Netmask: 255.255.255.0
Default Gateway: 212.74.111.194
Host Name: mygateway
Domain name: ar7

Windows server 2003 R2

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

Win Xp prof

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

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.

Thanks in advance, please ask if you need any more information.

[Meinolf Weber [MVP-DS]]

If the server is Domain controller, do you also use it for DNS because the
DNS server ip address points to the router? Change it to the DC/DNS server.
Active directory relies on DNS and you should run DNS on the server not on
the router. To get internet access configure the FORWARDER to the ISP's DNS
server under the DNS server properties in the DNS management console.

Also for DHCP use the server not the router. You have much more options for
configuring the scopes what clients get and also DNS record updates are better
to handle.

[Phillip Windell]

Make it like this:

Linksys:
LAN Interface
IP 192.168.120.1 (avoid "0" or "1" in the third octect, too
overused)
Mask: 255.255.255.0
Gateway: N/A (none)
DHCP Range given to clients,..go with the defaults.
-------------------------------
WAN Interface
(I'm assuming ISP provided DHCP)
IP: (provided by ISP's DHCP)
Mask:(provided by ISP's DHCP)
Gateway:(provided by ISP's DHCP)
DNS1:(provided by ISP's DHCP, or blank)
DNS2:(provided by ISP's DHCP, or blank)
DNS3:(provided by ISP's DHCP, or blank)


Domain Controller
(Use one nic *only*)
IP 192.168.120.4
Mask: 255.255.255.0
Gateway: 192.168.120.1
DNS: 192.168.120.4 <---It points to itself!! Important!!!
DNS: (*None*) <---None!! Important!!!

Workstation
(Use one nic *only*)
IP 192.168.120.6
Mask: 255.255.255.0
Gateway: 192.168.120.1
DNS: 192.168.120.4 <---It points to DC!! Important!!!
DNS: (*None*) <---None!! Important!!!

In the Config of the DNS Service on the DC either add the ISP's DNS IP#s to
the Forwarders List or just leave it alone and it will use Root Hints.

All of these things I am very specific on for specific reasons. You don't
have to take my advice if you don't want to,...but I will not change what I
suggested.


I'd rather not take off my clothing as the same that you do. I'll
pass.

[stevetilsed]

Thanks guys that worked smashingly!

[eiger3970]

Thanks Phillip Windell for the thread reply. Unfortunately, I still have the same problem.
Removing the 2nd DNS stopped my client PC accessing the internet so I had to re-enter 8.8.8.8 to get the client PC back on line.

[babu321]

when i tried to connect xp to the domain this message appears a domain controller for the domain could not be contacted . my xp does ping the domain server and it gets an ip address which assigned by the dhcp of the domain server .

please help