Windows 7 register to Windows Server 2003 domain server problem
in [Windows Servers]
|
From: Ray on 14 Jan 2010 22:30 Windows 7 Pro can't join to Windows Server 2003 domain server, error message as follow: "Your computer could not be joined to the domain because the following 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
From: Ace Fekay [MVP-DS, MCT] on 14 Jan 2010 23:52 "Ray" <ray(a)ray.com> wrote in message news:eiyBeMZlKHA.2592(a)TK2MSFTNGP04.phx.gbl... > Windows 7 Pro can't join to Windows Server 2003 domain server, error > message as follow: > > "Your computer could not be joined to the domain because the following > 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 > > 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 > can resolve DNS names in the target domain." 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.
From: Ray on 15 Jan 2010 02:58 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", "address:192.168.1.251" 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 "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> �b�l�� news:OQpGS6ZlKHA.5060(a)TK2MSFTNGP05.phx.gbl �����g... > "Ray" <ray(a)ray.com> wrote in message > news:eiyBeMZlKHA.2592(a)TK2MSFTNGP04.phx.gbl... >> Windows 7 Pro can't join to Windows Server 2003 domain server, error >> message as follow: >> >> "Your computer could not be joined to the domain because the following >> 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 >> >> > > > 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 >> can resolve DNS names in the target domain." > > 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. >
From: Meinolf Weber [MVP-DS] on 15 Jan 2010 03:07 Hello Ray, Remove the ISPs 202.175.3.3 from client the NIC and configure this address as a FORWARDER in the DNS server properties in the DNS management console. Additional stop the IP Rounting functionality on the DC. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > 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", > "address:192.168.1.251" > 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 > "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> ??? > news:OQpGS6ZlKHA.5060(a)TK2MSFTNGP05.phx.gbl ???... > >> "Ray" <ray(a)ray.com> wrote in message >> news:eiyBeMZlKHA.2592(a)TK2MSFTNGP04.phx.gbl... >> >>> Windows 7 Pro can't join to Windows Server 2003 domain server, error >>> message as follow: >>> >>> "Your computer could not be joined to the domain because the >>> following >>> 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 >> 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 >> >>> can resolve DNS names in the target domain." >>> >> 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. >>
From: kj [SBS MVP] on 15 Jan 2010 03:11
Ray wrote: > 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", > "address:192.168.1.251" > 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 > As recommended, remove the isp dns (202.175.3.3) and retry. > ------------------------------------------------------------------- > > 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 > > "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> �b�l�� > news:OQpGS6ZlKHA.5060(a)TK2MSFTNGP05.phx.gbl �����g... >> "Ray" <ray(a)ray.com> wrote in message >> news:eiyBeMZlKHA.2592(a)TK2MSFTNGP04.phx.gbl... >>> Windows 7 Pro can't join to Windows Server 2003 domain server, error >>> message as follow: >>> >>> "Your computer could not be joined to the domain because the >>> following 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 >>> >>> >> >> >> 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 >>> can resolve DNS names in the target domain." >> >> 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. -- /kj |