Sign in with
Sign up | Sign in
Your question
Solved

Active Directory Domain Services - Domain Controller Error

Tags:
  • Domain
  • Configuration
  • Connection
  • Business Computing
  • Domain Controller
Last response: in Business Computing
Share
November 16, 2013 5:42:19 PM

I am running Windows Server 2008 Enterprise. I am trying to connect a Windows XP Computer to the domain. The following error appears on the Windows XP Machine: "A domain controller for the domain paradise.local could not be contacted."

Windows XP Client IP Config:
Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix: att.net
IP Address: 192.168.1.64
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.254

Server IP Config:
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix: att.net
IPv4 Address: 192.168.1.148
Subnet Mask: 255.255.255.0
Default Gateway: fe80::b277:acff:fed2:2a70%10
192.168.1.254

Tunnel adapter Local Area Connection* 8:

Media State: Media disconnected
Connection-specific DNS Suffix: att.net

Thanks so much! If there is any more information needed, I will gladly provide it.

More about : active directory domain services domain controller error

Best solution

November 16, 2013 6:20:55 PM

Click on the properties of the network card and manually configure the DNS on the client machine. Now if ALL the computers on the LAN connect to the Domain its easier to set the local DNS on the router then you don't have to tinker with the machines because it gives it out when they get an IP address. But set the primary DNS to the Domain Server IP and then set the secondary DNS to the Router IP. that should fix your issues!

Also it doesn't look like the server has a static IP? a domain controller should ALWAYS HAVE A STATIC IP!! If it doesn't have a static IP then someone did something wrong when setting it up. when ever you setup a Domain Server in the setup process it ALWAYS ask you to set a STATIC IP. yes you can skip this but thats a big NO NO.
Share
November 16, 2013 6:48:59 PM

drtweak said:
Click on the properties of the network card and manually configure the DNS on the client machine. Now if ALL the computers on the LAN connect to the Domain its easier to set the local DNS on the router then you don't have to tinker with the machines because it gives it out when they get an IP address. But set the primary DNS to the Domain Server IP and then set the secondary DNS to the Router IP. that should fix your issues!

Also it doesn't look like the server has a static IP? a domain controller should ALWAYS HAVE A STATIC IP!! If it doesn't have a static IP then someone did something wrong when setting it up. when ever you setup a Domain Server in the setup process it ALWAYS ask you to set a STATIC IP. yes you can skip this but thats a big NO NO.


Thanks. Much appreciated
m
0
l
Related resources
November 16, 2013 6:57:33 PM

You have not configured DNS properly. Notice that the Conection-specific DNS Suffix is not set to your domain but to att.net, it's no wonder a domain controller can't be found. The DC must be set up with a static IP and be set up to provide DHCP and DNS services to the domain, point to itself for DNS with a forward to the ISP. Disable all DHCP functions on the private side of the router. The clients only receive the DC address for DNS, never the ISP's DNS.
m
0
l
November 16, 2013 7:38:05 PM

The server DOESN"T need to run DHCP on it. As long as you set the server with a static IP (Not in the range of IP's the router gives out to avoid something getting the same IP) and making sure the DNS is set properly on the Client's side and you'll be fine. Have a dozen clients set up like this. Only ever had one that had their server also run as DHCP.
m
0
l
November 16, 2013 7:57:32 PM

Yes, that will work, and I also have set things up that way on client request. However, in a small setting, Microsoft's published "best practices" calls out for DHCP to be provided by the DC/DC's (or at least did last time I read them, many moons ago). For a novice it's best to start with best practices before expanding out.
m
0
l
November 16, 2013 8:16:41 PM

Yea its best in a way so that the DHCP and DNS settings get to the correct way on the PC and you have less issues. In some routers (Like the Linksys WRT54GL which we use for a lot of clients because they are just so damn rock solid you can set the DNS in there and have it point to the Server first and then to the router. But yea in a BIG enviroment i would use the DC as the DHCP. But most of my clients have no more than 20 or so Domain PC's. The one that did have DHCP had like 40 PC's Plus an IP Phone system so it was a bit easier to manage with the DC as the DHCP
m
0
l
November 17, 2013 8:39:32 AM

Personally I can see the merits to setting up your DHCP server on the same system that is doing your domain controlling and DNS services. However, I've not done this for one main reason for most of our small business client systems. There are multiple networks. If I wish to keep networks separated (for instance, at my own office we have a private LAN for our computers and a separate LAN for any customers or service work computers) then I could set up DHCP on my own server to handle my domain computers, but other computers are not going to be able to reach that domain controller to get a DHCP assigned address. For this reason, I've used the DHCP server within the Sonicwall to assign dynamic pools as well as static assignments.

However, I know that there are other situations that I'd much rather use a DHCP service on the server. For example, there are customers utilizing some entry-level wireless routers like the Linksys E1200 which don't even support static assignments or IP reservations. Also, if there is a single domain network with multiple computers, then it may make much more sense to control pretty much all of your network settings from one VM in Windows.
m
0
l
!