A Domain Controller for the Domain XXX Could Not be Contacted

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


Win Xp prof
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


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.
3 answers Last reply
More about domain controller domain contacted
  1. I am not Windows Expert but I do know about networks. I don't see any problem with either your network or DHCP setup.

    If you feel it is a DNS issue, trying using IP address of the server directly. If that works, it is a DNS issue (or more likely NETBIOS name issue, unless your server is acting as DNS server too). If it doesn't work, then your problem is something else. Ask for more help here!!!
  2. Thanks, that actually was the issue! was that because of the reinstall using the same network?
  3. I don't know. Google is your friend.
Ask a new question

Read More

Routers Domain Domain Controller Networking