Computing.Net > Forums > Networking > Failed to resolve DNS name in domain contrler

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Failed to resolve DNS name in domain contrler

Reply to Message Icon

Name: Clarkee09
Date: September 18, 2009 at 09:58:18 Pacific
OS: Windows 7
Product: Microsoft Windows server 2003 r2 standard edition
Subcategory: General
Tags: DNS, Server, Windows, 2003, DHCP, Active Directory, client, network, router
Comment:

Yeah. Im trying to set up a server at home for the first time..

I've set up the Active Directory, DHCP & DNS.

I thought I set it up correctly... but obviously not.
When I try to connect a client computer (Windows 7) to the domain i get the following error..

"The following error occurred attempting to join the domain "cluster":

An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windowa Help.



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: September 18, 2009 at 10:18:44 Pacific
Reply:

do an ipconfig /all at the pc. Is the dns server ip listed that of the DC?


0

Response Number 2
Name: Clarkee09
Date: September 18, 2009 at 10:22:51 Pacific
Reply:

This is from the client computer. I hope this what you meant.

Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Clarkee>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Clarkee-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
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-23-54-25-78-68
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::981b:fd5e:6eb:5924%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 18 September 2009 17:06:15
Lease Expires . . . . . . . . . . : 19 September 2009 18:09:28
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 234890068
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-9D-C1-0E-00-23-54-25-78-68

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{3ECE785C-95BF-43F2-ABA0-C253E89F1C00}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:184a:20a7:adf8:d676(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::184a:20a7:adf8:d676%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6TO4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Clarkee>


0

Response Number 3
Name: wanderer
Date: September 18, 2009 at 11:01:23 Pacific
Reply:

See that entry for dns at 192.168.1.1?

That is your router not your dns server.

Either disable dhcp on the router and have the server dhcp provide ip with the correct settings or change the dhcp on the router.

You want dns to be your dc's ip address when you do an ipconfig /all


0

Response Number 4
Name: Clarkee09
Date: September 18, 2009 at 11:07:16 Pacific
Reply:

ok i've sorted that.
i disabled DHCP on the router and now its pointing to the server.

now when i try to connect to the domain it says access is denied.

even though ive allowed the computer on the AD and made a user account on the AD

ive tried restarting the server but it still doesnt work..

im confused.#
help please


0

Response Number 5
Name: wanderer
Date: September 18, 2009 at 12:31:42 Pacific
Reply:

"even though ive allowed the computer on the AD "

that doesn't sound right.

You have to join the pc to the domain. How are you doing that? What account are you using to do so?

Did you activate dhcp? what ip for dns does the workstation have?


0

Related Posts

See More



Sponsored Link
Ads by Google
Reply to Message Icon





Use following form to reply to current message:

Login or Register to Reply
LoginRegister


Sponsored links

Ads by Google


Results for: Failed to resolve DNS name in domain contrler

Win resolves host to wrong IP www.computing.net/answers/networking/win-resolves-host-to-wrong-ip/36356.html

NAT configuration failing to resolv www.computing.net/answers/networking/nat-configuration-failing-to-resolv/12301.html

Dial Up fails to resolve URLs www.computing.net/answers/networking/dial-up-fails-to-resolve-urls-/23531.html