First make sure you can ping to your domain controller, and manually set your DNS IP address to the domain controller you are trying to contact. You can also try a static IP address.
As for your network, it sounds like there are too many switches in a daisy chain which may also cause machines to timeout when attempting to contact the domain controller. Try to reduce that and expand the bandwidth with trunk ports. You might want to look into stackable Cisco 3750s or Juniper EX series switches.
<b>June 2, 2009 – UPDATE</b>
For those that read about this issue we’ve been able to help Yankusbobicus resolve his issue. Here are the troubleshooting steps we took.
Reviewing Event Logs for DHCP & DNS Errors which revealed that his Server was using a Single Name for domain which is not recommended.
<b>Added DNS Suffix to resolve this error</b>
Ran dcdiag on Domain Controller which revealed the following:
<b>Testing server: Default-First-Site\HCSSERVER
Starting test: Connectivity
The host 9223748e-b7e1-40e5-9622-2282914a4da6._msdcs.HuntingtonCatholic
.local could not be resolved to an
At this point checked to see if DNS was Active Directory Integrated
<b>The answer to this was No</b>
Changed it from Primary to Active Directory Integrated and ran another dcdiag test. The result of this test was:
<b> Testing server: Default-First-Site\HCSSERVER
Starting test: Connectivity
……………………. HCSSERVER passed test Connectivity</b>
The Server DHCP, DNS and WINS services were all active and working however still had some DNS trouble therefore NO records were being generated for the clients.
Tried joining a client to the domain and received an Error that it could not find the domain.
As it stood there had been some residual information in some old events that led us to believe that 2 NICS were used at onetime therefore leading to someone changing Active Directory Integration to Primary and enabling ICS on the Server.
The Event ID was as follows:
Event ID 113
Description The DNS server could not signal the service “NAT”. The error was 1168. There may be interoperability problems between the DNS service and this service.
Adrian Grigorof (Last update 4/4/2004):
From a newsgroup post: “Are you using ICS or NAT in RRAS? If it is ICS then disable ICS and use NAT in RRAS. If your are using NAT in RRAS then are you using the DNS proxy? If you have the DNS proxy enabled disable it.”
**This event has also been reported on DNS servers configured for Internet Connection Sharing (ICS). ICS installs its own DNS proxy service and that is in conflict with the DNS. ICS is not supposed to be used on servers that run DNS or DHCP
<b>Checked ICS on the Server and sure enough it was Enabled and Running. Shutdown ICS Service and configured to DISABLE. Read paragraph above.</b>
Once all the above was done DHCP, DNS and WINS was working correctly. Any client not joined to domain would receive an IP Address from the DHCP Server and register itself in WINS. Once Client was joined to the Domain it registered itself in AD and DNS.
Server was set with static IP example below of Single NIC configuration:
IP Address: 192.168.1.10
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.10
DNS Forwarders were set to OpenDNS
Diabled DHCP on the Cable Router.