Windows Server - Windows 7 register to Windows Server 2003 domain server problem

Asked By Ray

14-Jan-10 10:30 PM

Windows 7 Pro cannot join to Windows Server 2003 domain server, error message
as follow:

error occured:
An attempt to resolve the DNS name of a DC 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."

Windows 7 can ping the Windows 2003 server, all machines ip & dns settings
are from dhcp server,
but Windows XP machine is all fine to join the Windows 2003 domain server.

I google the problem, found that some ppl has the same problem with vista,
Anyone has similar experience?
Thanks

15-Jan-10 12:17 AM

age
t
s
.
,


Hi,

Sound like DNS issue. If your domain is mydomain.local try this :

Try joining mydomain.local and also mydomain without the TLD
extension.

If DNS is configured, you should be able to resolve the DC by pinging
mydomain.local from the Vista box.

Under TCP/IP properties advanced, check it has append primary DNS
suffix

Miguel Fra / Falcon ITS
http://www.falconits.com

14-Jan-10 11:50 PM

I agree with Miguel. It sounds like a DNS problem. Does this client use
the DC only for DNS? What happens if you run an nslookup from the client for
the domain name using the formats Miguel suggested?

14-Jan-10 11:52 PM

This is typically caused by a DNS misconfiguration. If you can post an
unedited ipconfig /all from the workstation, and from the DC, we can
evaluate the configuration to help diagnose this for you.

What I can say, is basically the fix for this, just as the part in the error
message said, "...Please verify this client is configured to reach a DNS
server that

To eliminate any problems with AD, always make sure the ONLY DNS server in
the machine's IP configuration is your domain controllers that are running
DNS. If you use an ISP's DNS, or the router as a DNS address, expect
numerous AD problems, including what you are seeing.

To get efficient internet resolution, I recommend configuring a fowarder.

Also, if the domain controllers are multihomed, which is defined as a domain
controller with more than one NIC, IP address or RRAS installed, will also
cause problems.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

15-Jan-10 02:58 AM

Thanks all!!
I tried both "company" or "company.local" to join the domain, but not
sucess, append primary DNS suffix is checked. when I type "nslookup
192.168.1.251" it returns "server: srv1.company.local",
ipconfig /all result as followings.
Thank you for all of u!!

Windows 7 Pro (ipconfig /all)
Host Name  . . . . . . . . . . . . .: dx7510
Primary Dns Suffix    . . . . . . . . . .:
Node Type  . . . . . . . . . . . . .: Mixed
IP Routing Enabled . . . . . . . . . . . : ?_
WINS Proxy Enabled . . . . . . . . . : NO

Description . . . . . . . . . . . . . . .: Realtek PCIe GBE Family
Controller
Physical Address . . . . . . . . . . . . .: 00-25-B3-18-AD-B5
DHCP  . . . . . . . . . . . . . . . . : No
IPv4 Address . . . . . . . . . . . . : 192.168.1.25
Subnet Mask . . . . . . . . . . . .: 255.255.255.0
Gateway . . . . . . . . . . . . .: 192.168.1.9
DNS Server . . . . . . . . . . . .: 192.168.1.251
(internet isp)      202.175.3.3
NetBIOS over Tcpip . . . . . . . .: Enable

-------------------------------------------------------------------

Windows Server 2003 (ipconfig /all)

Host Name . . . . . . . . . . . . : srv1
Primary Dns Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : company.local

Connection-specific DNS Suffix  . : company.local
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-11-85-D4-99-7B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.251
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.9
DNS Servers . . . . . . . . . . . : 192.168.1.251

15-Jan-10 03:11 AM

As recommended, remove the isp dns (202.175.3.3) and retry.

15-Jan-10 03:52 AM

ok, thanks all, need to wait for non-business hour to try!!

15-Jan-10 11:49 AM

This is a workstation IP config change. If your server is already resolving
public internet names then you have at least a working config but perhaps
not ideal (root hints vs. an ISP forwarder).

Changing the windows 7 workstation should not make any difference to anyone
but the workstation user.

15-Jan-10 01:09 PM

Follow Meinolf's recommendation to remove that ISP's DNS. That's why you are
having problems. The client machine is asking the ISP, "where is my domain
controller?" Does it know that answer?

Ace

15-Jan-10 01:11 PM

Why? Making this change will help immediately. There will be no downtime,
matter of fact it will work.

Also, the client is set to a static config. Not using DHCP? It would be
easier toset a centrally controlled config for all machines using Windows
DHCP, wihcih interoperates with Dynamic DNS.

Ace

23-Jan-10 12:07 PM

I have similar problem with windows 7,  could not join the domain, I can ping the gateway but not the domain only from the windows 7 machin.

thank you fot looking in to it
alem

---
frmsrcurl: http://msgroups.net/microsoft.public.windows.server.general/Windows-7-register-to-Windows-Server-2003-domain-server

25-Jan-10 05:13 PM

Bear in mind that Ping is an IP connectivity test. First is uses Hosts_file/DNS
to resolve the name and then Netbios to resolve the name to an IP. After the IP
is obtained the ICMP "ping" is done. So first you need to determine is Ping is
resolving the name to a IP, If not you have a name resolution issue not in IP
issue. It the correct IP is found and there is no connectivity (no reply) is it
a "Request timed out", "Destination not reachable", "Reply from <gateway>
Destination no reachable" etc. Each tells a different story as to where the
issue lies.

Your do not "ping a domain" you ping a host name so you need to be a lot more
specific about the ping command you issues and the response message you
received. If you edit the response to hide the name you may simply introduce
your own interpretation thus masking the read issue.

--
Dave Mills
There are 10 types of people, those that understand binary and those that do not.

25-Jan-10 09:17 PM

Hello customer,

The managed support service of the microsoft.public.windows.server.general
is now available instead on General forum:
http://social.technet.microsoft.com/Forums/en-US/winservergen/threads.
Would you please repost the question in the forum with the Windows Live ID
used to access your Subscription benefits? Our engineers will assist you in
the new platform.

The web link http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx
introduces more information about the migration. In the future, please post
your Print-related questions directly to the forums. If you have any
questions or concerns, please feel free to contact us: tngfb@microsoft.com

David Shen
Microsoft Online Technical Support