Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > Windows 7 client can't join win 2003 r2 domain

Reply
Thread Tools Display Modes

Windows 7 client can't join win 2003 r2 domain

 
 
DRedDog
Guest
Posts: n/a

 
      02-17-2010
When I try to add my computer to my win 2003 domain I get the following
error

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate an Active Directory Domain Controller
(AD DC) for domain "DBTAYLOR.DEV":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
ETC

DHCP is not configured on my Win 2003 server - the client's IP address is
fixed.

ipconfig/all give the following output

Windows IP Configuration

Host Name . . . . . . . . . . . . : DTWS1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family
PCI-E
Gigabit Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1F-C6-04-9D-C1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::adde:3a5a:c12b:7aa3%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 251666060
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-0F-5D-8F-85-00-1F-C6-04-9D-C1

DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e74:102f:1a14:3f57:fef8(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::102f:1a14:3f57:fef8%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{8A4855E0-B760-4AE6-87AD-6F8DE11CFC73}:

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

Thanks in advance.

dreddog

 
Reply With Quote
 
 
 
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      02-17-2010

Hello dreddog,

Didn't you read my answer in microsoft.public.windows.server.active_directory
with subject "Re: An active directory Domain Controller for the domain could
not becontacted in windows vista Business"?

Here it is again:
I have no idea what your question is, as in the microsoft.public.windows.server.active_directory
newsgroup is no old posting your replying to.

BUT, your ipconfig /all from DTWS1 points to external DNS servers and if
this machine is a domain member or should become domain member use ONLY the
domain DNS servers on the NIC and not your ISPs one as it looks like, 208.67.222.222
and 208.67.220.220.

Remove the 2 DNS server ip's and add them as FORWARDERS under the DNS server
properties in the DNS management console on the DOMAIN DNS server.


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


> When I try to add my computer to my win 2003 domain I get the
> following error
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate an Active Directory
> Domain Controller (AD DC) for domain "DBTAYLOR.DEV":
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
> ETC
> DHCP is not configured on my Win 2003 server - the client's IP address
> is fixed.
>
> ipconfig/all give the following output
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : DTWS1
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P)
> Family
> PCI-E
> Gigabit Ethernet NIC (NDIS 6.0)
> Physical Address. . . . . . . . . : 00-1F-C6-04-9D-C1
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::adde:3a5a:c12b:7aa3%10(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 251666060
> DHCPv6 Client DUID. . . . . . . . :
> 00-01-00-01-0F-5D-8F-85-00-1F-C6-04-9D-C1
> DNS Servers . . . . . . . . . . . : 208.67.222.222
> 208.67.220.220
> NetBIOS over Tcpip. . . . . . . . : Enabled
> Tunnel adapter Teredo Tunneling Pseudo-Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv6 Address. . . . . . . . . . . :
> 2001:0:4137:9e74:102f:1a14:3f57:fef8(Pref
> erred)
> Link-local IPv6 Address . . . . . :
> fe80::102f:1a14:3f57:fef8%11(Preferred)
> Default Gateway . . . . . . . . . : ::
> NetBIOS over Tcpip. . . . . . . . : Disabled
> Tunnel adapter isatap.{8A4855E0-B760-4AE6-87AD-6F8DE11CFC73}:
>
> 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
> Thanks in advance.
>
> dreddog
>



 
Reply With Quote
 
Chris M
Guest
Posts: n/a

 
      02-18-2010
On 17/02/2010 21:49, DRedDog wrote:
> When I try to add my computer to my win 2003 domain I get the following
> error
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate an Active Directory Domain
> Controller (AD DC) for domain "DBTAYLOR.DEV":
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
> ETC


Is DBTAYLOR.DEV your actual DNS name for the domain or is it the NetBIOS
name? (NetBIOS names can contain dots apparently)

From the ipconfig you posted, NetBIOS is disabled on the Win7 machine
so you won't be able to join the domain using its NetBIOS name. If it
has a different DNS name, try using that.

--
Chris M.
 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      02-18-2010
"DRedDog" <> wrote in message
news:35653C4D-F4DF-49A8-B56C-...
> When I try to add my computer to my win 2003 domain I get the following
> error
>
> The following error occurred when DNS was queried for the service location
> (SRV) resource record used to locate an Active Directory Domain Controller
> (AD DC) for domain "DBTAYLOR.DEV":
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
> ETC
>
> DHCP is not configured on my Win 2003 server - the client's IP address is
> fixed.
>
> ipconfig/all give the following output
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : DTWS1
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family
> PCI-E
> Gigabit Ethernet NIC (NDIS 6.0)
> Physical Address. . . . . . . . . : 00-1F-C6-04-9D-C1
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::adde:3a5a:c12b:7aa3%10(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 251666060
> DHCPv6 Client DUID. . . . . . . . :
> 00-01-00-01-0F-5D-8F-85-00-1F-C6-04-9D-C1
>
> DNS Servers . . . . . . . . . . . : 208.67.222.222
> 208.67.220.220
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Tunnel adapter Teredo Tunneling Pseudo-Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv6 Address. . . . . . . . . . . :
> 2001:0:4137:9e74:102f:1a14:3f57:fef8(Pref
> erred)
> Link-local IPv6 Address . . . . . :
> fe80::102f:1a14:3f57:fef8%11(Preferred)
> Default Gateway . . . . . . . . . : ::
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter isatap.{8A4855E0-B760-4AE6-87AD-6F8DE11CFC73}:
>
> 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
>
> Thanks in advance.
>
> dreddog




DRedDog,

As Meinolf said, how is it supposed to resolve an internal domain name info
for your AD domain, when it is using your ISP's DNS address in ipconfig? It
will never find it.

Only put in the internal DNS server. This must be set on ALL AD machines.
Setup a forwarder in DNS to point to that 208.x.x.x number. If not sure how
to setup a forwarder, follow the instructions in the link below.

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
http://support.microsoft.com/?id=323380

Keep in mind, as I mentioned, all machines in AD must only use the AD DNS
servers. If you put in the ISP's, even mixing it up with internal DNS,
*WILL* cause problems. Remove the ISP's DNS on the DCs.

Also, if the DC is multihomed (more than one NIC that are not teamed, more
than one IP, and/or if RRAS is installed). WILL ALSO cause major problems.

Was this posted elsewhere, as Meinolf mentioned? May be a good practice to
use Cross-Posting instead of Multi-posting. It will help you and us when
asking for assistance. This way, you and the folks helping, only have to
check one group, because all messages will simultaneously go to all groups.
Multi-posting doesn't do that.

--
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.


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
2nd Domain in a 2 domain forest cannot be contacted David Alge DNS Server 30 01-21-2010 05:26 AM
Windows Update error code 8007065E Martin R Windows Update 7 01-14-2010 01:33 PM
Re: Disable Windows Firewall Lanwench [MVP - Exchange] Windows Small Business Server 7 01-06-2010 11:45 PM
Re: re-installing Windows 2003 SBS Merv Porter Windows Small Business Server 0 12-21-2009 02:11 PM
Error not able to loging after upgrading domain controller Alexyy Active Directory 6 11-10-2009 06:09 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59