unable to join to the domain with netbios name

October 14, 2008

Hi

I am unable to join my Vista business machine to a windows 2003 domain

using netbios name, FQDN is fine. Netbios resolution is working as I can

browse the domain and use net use to map network drive on all DCs within

the domain. Also, all Windows XP machines can join to the domain with

netbios name.

Netbios over tcpip is enabled and IPV6/local firewall is disabled. All

client machines are on the same subnet. No WINS is used on the network.

The error message is:

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.

Any idea?

Thanks

October 14, 2008

Re: unable to join to the domain with netbios name

OM <om@discussions.microsoft.com> wrote:

> Hi

>

> I am unable to join my Vista business machine to a windows 2003 domain

> using netbios name, FQDN is fine. Netbios resolution is working as I

> can browse the domain and use net use to map network drive on all DCs

> within the domain. Also, all Windows XP machines can join to the

> domain with netbios name.

>

> Netbios over tcpip is enabled and IPV6/local firewall is disabled. All

> client machines are on the same subnet. No WINS is used on the

> network.

> The error message is:

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

>

> Any idea?

>

> Thanks

Please post the unedited output of an ipconfig /all from this PC and one of

your DCs.

October 14, 2008

Re: unable to join to the domain with netbios name

"OM" <om@discussions.microsoft.com> wrote in message

news:%230F24bhLJHA.3496@TK2MSFTNGP04.phx.gbl...

> Hi

>

> I am unable to join my Vista business machine to a windows 2003 domain

> using netbios name, FQDN is fine. Netbios resolution is working as I can

> browse the domain and use net use to map network drive on all DCs within

> the domain. Also, all Windows XP machines can join to the domain with

> netbios name.

>

> Netbios over tcpip is enabled and IPV6/local firewall is disabled. All

> client machines are on the same subnet. No WINS is used on the network.

>

> The error message is:

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

>

> Any idea?

>

> Thanks

I had a lot of trouble joining Vista computers to my domain until I started

using the script below:

===========

' JoinDomain.vbs

' VBScript program to join a computer to a domain.

' The computer account is created in Active Directory.

' The computer must have XP or above.

' The AD must be W2k3 or above.

' See c:\Windows\debug\NetSetup.log for details.

Option Explicit

Dim strDomain, strUser, strPassword

Dim objNetwork, strComputer, objComputer, lngReturnValue

Dim strOU

Const JOIN_DOMAIN = 1

Const ACCT_CREATE = 2

Const ACCT_DELETE = 4

Const WIN9X_UPGRADE = 16

Const DOMAIN_JOIN_IF_JOINED = 32

Const JOIN_UNSECURE = 64

Const MACHINE_PASSWORD_PASSED = 128

Const DEFERRED_SPN_SET = 256

Const INSTALL_INVOCATION = 262144

strDomain = "MyDomain"

strPassword = "zyX321$q"

strUser = "administrator"

strOU = "ou=Computers,ou=West,dc=MyDomain,dc=com"

Set objNetwork = CreateObject("WScript.Network")

strComputer = objNetwork.ComputerName

Set objComputer = GetObject("winmgmts:" _

& "{impersonationLevel=Impersonate,authenticationLevel=Pkt}!\\" & _

strComputer & "\root\cimv2:Win32_ComputerSystem.Name='" & _

strComputer & "'")

lngReturnValue = objComputer.JoinDomainOrWorkGroup(strDomain, _

strPassword, strDomain & "\" & strUser, strOU, _

JOIN_DOMAIN + ACCT_CREATE)

Wscript.Echo "ReturnValue = " & CStr(lngReturnValue)

============

The log file c:\Windows\debug\NetSetup.log created by this program is very

helpful.

--

Richard Mueller

MVP Directory Services

Hilltop Lab - http://www.rlmueller.net

--

October 14, 2008

Re: unable to join to the domain with netbios name

Vista PC

Windows IP Configuration

Host Name . . . . . . . . . . . . : pcs05

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : domain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.com

Description . . . . . . . . . . . : Intel® PRO/100 VE Network

Connection

Physical Address. . . . . . . . . : 00-11-11-47-D4-68

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.224.0

Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008 8:52:53 AM

Lease Expires . . . . . . . . . . : Wednesday, October 15, 2008

8:52:53 AM

Default Gateway . . . . . . . . . : 155.50.100.18

DHCP Server . . . . . . . . . . . : 155.50.100.186

DNS Servers . . . . . . . . . . . : 155.50.100.19

155.50.100.68

155.50.106.82

155.50.127.50

155.50.113.101

NetBIOS over Tcpip. . . . . . . . : Enabled

Windows 2003 DC

Windows IP Configuration

Host Name . . . . . . . . . . . . : addc

Primary Dns Suffix . . . . . . . : addomain.domain.com

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : addomain.domain.com

domain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast

Ethernet NIC

Physical Address. . . . . . . . . : 00-16-3E-00-00-21

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 155.50.100.220

Subnet Mask . . . . . . . . . . . : 255.255.224.0

Default Gateway . . . . . . . . . : 155.50.100.18

DNS Servers . . . . . . . . . . . : 155.50.100.19

155.50.100.68

Lanwench [MVP - Exchange] wrote:

> OM <om@discussions.microsoft.com> wrote:

>> Hi

>>

>> I am unable to join my Vista business machine to a windows 2003 domain

>> using netbios name, FQDN is fine. Netbios resolution is working as I

>> can browse the domain and use net use to map network drive on all DCs

>> within the domain. Also, all Windows XP machines can join to the

>> domain with netbios name.

>>

>> Netbios over tcpip is enabled and IPV6/local firewall is disabled. All

>> client machines are on the same subnet. No WINS is used on the

>> network.

>> The error message is:

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

>>

>> Any idea?

>>

>> Thanks

>

> Please post the unedited output of an ipconfig /all from this PC and one of

> your DCs.

>

October 14, 2008

Re: unable to join to the domain with netbios name

OM <om@discussions.microsoft.com> wrote:

> Vista PC

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : pcs05

> Primary Dns Suffix . . . . . . . :

> Node Type . . . . . . . . . . . . : Hybrid

> IP Routing Enabled. . . . . . . . : No

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : domain.com

>

> Ethernet adapter Local Area Connection:

>

> Connection-specific DNS Suffix . : domain.com

> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

> Connection

> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

> DHCP Enabled. . . . . . . . . . . : Yes

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.224.0

> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday, October

> 15, 2008 8:52:53 AM

> Default Gateway . . . . . . . . . : 155.50.100.18

> DHCP Server . . . . . . . . . . . : 155.50.100.186

> DNS Servers . . . . . . . . . . . : 155.50.100.19

> 155.50.100.68

> 155.50.106.82

> 155.50.127.50

> 155.50.113.101

> NetBIOS over Tcpip. . . . . . . . : Enabled

>

> Windows 2003 DC

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : addc

> Primary Dns Suffix . . . . . . . : addomain.domain.com

> Node Type . . . . . . . . . . . . : Unknown

> IP Routing Enabled. . . . . . . . : No

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : addomain.domain.com

> domain.com

>

> Ethernet adapter Local Area Connection:

>

> Connection-specific DNS Suffix . :

>

> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast

> Ethernet NIC

> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

> DHCP Enabled. . . . . . . . . . . : No

> IP Address. . . . . . . . . . . . : 155.50.100.220

> Subnet Mask . . . . . . . . . . . : 255.255.224.0

> Default Gateway . . . . . . . . . : 155.50.100.18

> DNS Servers . . . . . . . . . . . : 155.50.100.19

> 155.50.100.68

>

OK - you've got addomain.domain.com as the DNS suffix on your DC, but

domain.com on the client.

Also, why are you using public IPs on your LAN, and why so many DNS server

IPs on the client?

>

> Lanwench [MVP - Exchange] wrote:

>> OM <om@discussions.microsoft.com> wrote:

>>> Hi

>>>

>>> I am unable to join my Vista business machine to a windows 2003

>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>> working as I can browse the domain and use net use to map network

>>> drive on all DCs within the domain. Also, all Windows XP machines

>>> can join to the domain with netbios name.

>>>

>>> Netbios over tcpip is enabled and IPV6/local firewall is disabled.

>>> All client machines are on the same subnet. No WINS is used on the

>>> network.

>>> The error message is:

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

>>>

>>> Any idea?

>>>

>>> Thanks

>>

>> Please post the unedited output of an ipconfig /all from this PC and

>> one of your DCs.

October 14, 2008

Re: unable to join to the domain with netbios name

addomin is the netbios name of the Active Directory. The DC

automatically added addomain.domain.com as the primary DNS suffix when

it joined to the domain. By default, the dhcp server assigns domain.com

as the DNS suffix for all dhcp clients on the network. As I mentioned

before, all XP machines are able to join to the domain with the Netbios

name but not Vista machines (work if I use FQDN).

We are educational organization and have a qualified class B address

assigned. I can't tell why we use public IP addresses and why there have

so many DNS servers as I am not the network administrator. I am only

responsible for the Windows servers.

BTY, we don't use Windows DNS server in our network, we use BIND

instead. Would it make a difference?

Lanwench [MVP - Exchange] wrote:

> OM <om@discussions.microsoft.com> wrote:

>> Vista PC

>>

>> Windows IP Configuration

>>

>> Host Name . . . . . . . . . . . . : pcs05

>> Primary Dns Suffix . . . . . . . :

>> Node Type . . . . . . . . . . . . : Hybrid

>> IP Routing Enabled. . . . . . . . : No

>> WINS Proxy Enabled. . . . . . . . : No

>> DNS Suffix Search List. . . . . . : domain.com

>>

>> Ethernet adapter Local Area Connection:

>>

>> Connection-specific DNS Suffix . : domain.com

>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>> Connection

>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>> DHCP Enabled. . . . . . . . . . . : Yes

>> Autoconfiguration Enabled . . . . : Yes

>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday, October

>> 15, 2008 8:52:53 AM

>> Default Gateway . . . . . . . . . : 155.50.100.18

>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>> 155.50.100.68

>> 155.50.106.82

>> 155.50.127.50

>> 155.50.113.101

>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>

>> Windows 2003 DC

>>

>> Windows IP Configuration

>>

>> Host Name . . . . . . . . . . . . : addc

>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>> Node Type . . . . . . . . . . . . : Unknown

>> IP Routing Enabled. . . . . . . . : No

>> WINS Proxy Enabled. . . . . . . . : No

>> DNS Suffix Search List. . . . . . : addomain.domain.com

>> domain.com

>>

>> Ethernet adapter Local Area Connection:

>>

>> Connection-specific DNS Suffix . :

>>

>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast

>> Ethernet NIC

>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>> DHCP Enabled. . . . . . . . . . . : No

>> IP Address. . . . . . . . . . . . : 155.50.100.220

>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>> Default Gateway . . . . . . . . . : 155.50.100.18

>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>> 155.50.100.68

>>

> OK - you've got addomain.domain.com as the DNS suffix on your DC, but

> domain.com on the client.

> Also, why are you using public IPs on your LAN, and why so many DNS server

> IPs on the client?

>>

>> Lanwench [MVP - Exchange] wrote:

>>> OM <om@discussions.microsoft.com> wrote:

>>>> Hi

>>>>

>>>> I am unable to join my Vista business machine to a windows 2003

>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>> working as I can browse the domain and use net use to map network

>>>> drive on all DCs within the domain. Also, all Windows XP machines

>>>> can join to the domain with netbios name.

>>>>

>>>> Netbios over tcpip is enabled and IPV6/local firewall is disabled.

>>>> All client machines are on the same subnet. No WINS is used on the

>>>> network.

>>>> The error message is:

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

>>>>

>>>> Any idea?

>>>>

>>>> Thanks

>>> Please post the unedited output of an ipconfig /all from this PC and

>>> one of your DCs.

>

October 15, 2008

Re: unable to join to the domain with netbios name

OM <om@discussions.microsoft.com> wrote:

> addomin is the netbios name of the Active Directory.

OK.

The DC

> automatically added addomain.domain.com as the primary DNS suffix when

> it joined to the domain.

No, it shouldn't have. What you showed in the ipconfig /all indicates that

addomain.domain.com is the domain name.

From the server itself, if you ping the server's NetBIOS name, what FQDN

does it return?

> By default, the dhcp server assigns

> domain.com as the DNS suffix for all dhcp clients on the network. w

Only because someone set it up to do that.

> As

> I mentioned before, all XP machines are able to join to the domain

> with the Netbios name but not Vista machines (work if I use FQDN).

>

> We are educational organization and have a qualified class B address

> assigned.

OK, but that still doesn't mean you need them internally. I understand

that's not your department, but it's probably a bad choice unless there's

some compelling requirement.

> I can't tell why we use public IP addresses and why there

> have so many DNS servers as I am not the network administrator. I am

> only responsible for the Windows servers.

I'd ask them. This does impact what you work on.

>

> BTY, we don't use Windows DNS server in our network, we use BIND

> instead. Would it make a difference?

You probably should be using AD-integrated DNS, but you don't necessarily

have to, as long as your DNS server supports dynamic updates.

If you open AD Domains and Trusts, what is the AD domain name listed there?

Whatever it is, is the primary DNS suffix you should have on all servers and

clients.

>

> Lanwench [MVP - Exchange] wrote:

>> OM <om@discussions.microsoft.com> wrote:

>>> Vista PC

>>>

>>> Windows IP Configuration

>>>

>>> Host Name . . . . . . . . . . . . : pcs05

>>> Primary Dns Suffix . . . . . . . :

>>> Node Type . . . . . . . . . . . . : Hybrid

>>> IP Routing Enabled. . . . . . . . : No

>>> WINS Proxy Enabled. . . . . . . . : No

>>> DNS Suffix Search List. . . . . . : domain.com

>>>

>>> Ethernet adapter Local Area Connection:

>>>

>>> Connection-specific DNS Suffix . : domain.com

>>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>>> Connection

>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>> DHCP Enabled. . . . . . . . . . . : Yes

>>> Autoconfiguration Enabled . . . . : Yes

>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday, October

>>> 15, 2008 8:52:53 AM

>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>> 155.50.100.68

>>> 155.50.106.82

>>> 155.50.127.50

>>> 155.50.113.101

>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>

>>> Windows 2003 DC

>>>

>>> Windows IP Configuration

>>>

>>> Host Name . . . . . . . . . . . . : addc

>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>> Node Type . . . . . . . . . . . . : Unknown

>>> IP Routing Enabled. . . . . . . . : No

>>> WINS Proxy Enabled. . . . . . . . : No

>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>> domain.com

>>>

>>> Ethernet adapter Local Area Connection:

>>>

>>> Connection-specific DNS Suffix . :

>>>

>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI

>>> Fast Ethernet NIC

>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>> DHCP Enabled. . . . . . . . . . . : No

>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>> 155.50.100.68

>>>

>> OK - you've got addomain.domain.com as the DNS suffix on your DC, but

>> domain.com on the client.

>> Also, why are you using public IPs on your LAN, and why so many DNS

>> server IPs on the client?

>>>

>>> Lanwench [MVP - Exchange] wrote:

>>>> OM <om@discussions.microsoft.com> wrote:

>>>>> Hi

>>>>>

>>>>> I am unable to join my Vista business machine to a windows 2003

>>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>>> working as I can browse the domain and use net use to map network

>>>>> drive on all DCs within the domain. Also, all Windows XP machines

>>>>> can join to the domain with netbios name.

>>>>>

>>>>> Netbios over tcpip is enabled and IPV6/local firewall is disabled.

>>>>> All client machines are on the same subnet. No WINS is used on the

>>>>> network.

>>>>> The error message is:

>>>>> 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. Any idea?

>>>>>

>>>>> Thanks

>>>> Please post the unedited output of an ipconfig /all from this PC

>>>> and one of your DCs.

October 15, 2008

Re: unable to join to the domain with netbios name

If I ping the server's netbios name form its console, I got

addc.addomain.domain.com reply. And the AD domain name listed in the

Domain and Trust utility is addomain.adomin.com

Lanwench [MVP - Exchange] wrote:

> OM <om@discussions.microsoft.com> wrote:

>> addomin is the netbios name of the Active Directory.

>

> OK.

>

> The DC

>> automatically added addomain.domain.com as the primary DNS suffix when

>> it joined to the domain.

>

> No, it shouldn't have. What you showed in the ipconfig /all indicates that

> addomain.domain.com is the domain name.

>

> From the server itself, if you ping the server's NetBIOS name, what FQDN

> does it return?

>

>> By default, the dhcp server assigns

>> domain.com as the DNS suffix for all dhcp clients on the network. w

>

> Only because someone set it up to do that.

>

>> As

>> I mentioned before, all XP machines are able to join to the domain

>> with the Netbios name but not Vista machines (work if I use FQDN).

>>

>> We are educational organization and have a qualified class B address

>> assigned.

>

> OK, but that still doesn't mean you need them internally. I understand

> that's not your department, but it's probably a bad choice unless there's

> some compelling requirement.

>

>> I can't tell why we use public IP addresses and why there

>> have so many DNS servers as I am not the network administrator. I am

>> only responsible for the Windows servers.

>

> I'd ask them. This does impact what you work on.

>> BTY, we don't use Windows DNS server in our network, we use BIND

>> instead. Would it make a difference?

>

> You probably should be using AD-integrated DNS, but you don't necessarily

> have to, as long as your DNS server supports dynamic updates.

>

> If you open AD Domains and Trusts, what is the AD domain name listed there?

> Whatever it is, is the primary DNS suffix you should have on all servers and

> clients.

>>

>> Lanwench [MVP - Exchange] wrote:

>>> OM <om@discussions.microsoft.com> wrote:

>>>> Vista PC

>>>>

>>>> Windows IP Configuration

>>>>

>>>> Host Name . . . . . . . . . . . . : pcs05

>>>> Primary Dns Suffix . . . . . . . :

>>>> Node Type . . . . . . . . . . . . : Hybrid

>>>> IP Routing Enabled. . . . . . . . : No

>>>> WINS Proxy Enabled. . . . . . . . : No

>>>> DNS Suffix Search List. . . . . . : domain.com

>>>>

>>>> Ethernet adapter Local Area Connection:

>>>>

>>>> Connection-specific DNS Suffix . : domain.com

>>>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>>>> Connection

>>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>>> DHCP Enabled. . . . . . . . . . . : Yes

>>>> Autoconfiguration Enabled . . . . : Yes

>>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday, October

>>>> 15, 2008 8:52:53 AM

>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>> 155.50.100.68

>>>> 155.50.106.82

>>>> 155.50.127.50

>>>> 155.50.113.101

>>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>>

>>>> Windows 2003 DC

>>>>

>>>> Windows IP Configuration

>>>>

>>>> Host Name . . . . . . . . . . . . : addc

>>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>>> Node Type . . . . . . . . . . . . : Unknown

>>>> IP Routing Enabled. . . . . . . . : No

>>>> WINS Proxy Enabled. . . . . . . . : No

>>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>>> domain.com

>>>>

>>>> Ethernet adapter Local Area Connection:

>>>>

>>>> Connection-specific DNS Suffix . :

>>>>

>>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI

>>>> Fast Ethernet NIC

>>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>>> DHCP Enabled. . . . . . . . . . . : No

>>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>> 155.50.100.68

>>>>

>>> OK - you've got addomain.domain.com as the DNS suffix on your DC, but

>>> domain.com on the client.

>>> Also, why are you using public IPs on your LAN, and why so many DNS

>>> server IPs on the client?

>>>>

>>>> Lanwench [MVP - Exchange] wrote:

>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>> Hi

>>>>>>

>>>>>> I am unable to join my Vista business machine to a windows 2003

>>>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>>>> working as I can browse the domain and use net use to map network

>>>>>> drive on all DCs within the domain. Also, all Windows XP machines

>>>>>> can join to the domain with netbios name.

>>>>>>

>>>>>> Netbios over tcpip is enabled and IPV6/local firewall is disabled.

>>>>>> All client machines are on the same subnet. No WINS is used on the

>>>>>> network.

>>>>>> The error message is:

>>>>>> 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. Any idea?

>>>>>>

>>>>>> Thanks

>>>>> Please post the unedited output of an ipconfig /all from this PC

>>>>> and one of your DCs.

>

October 15, 2008

Re: unable to join to the domain with netbios name

OM <om@discussions.microsoft.com> wrote:

> If I ping the server's netbios name form its console, I got

> addc.addomain.domain.com reply. And the AD domain name listed in the

> Domain and Trust utility is addomain.adomin.com

Then change the primary DNS suffix in your DHCP scope to

addomain.domain.com.

>

> Lanwench [MVP - Exchange] wrote:

>> OM <om@discussions.microsoft.com> wrote:

>>> addomin is the netbios name of the Active Directory.

>>

>> OK.

>>

>> The DC

>>> automatically added addomain.domain.com as the primary DNS suffix

>>> when it joined to the domain.

>>

>> No, it shouldn't have. What you showed in the ipconfig /all

>> indicates that addomain.domain.com is the domain name.

>>

>> From the server itself, if you ping the server's NetBIOS name, what

>> FQDN does it return?

>>

>>> By default, the dhcp server assigns

>>> domain.com as the DNS suffix for all dhcp clients on the network. w

>>

>> Only because someone set it up to do that.

>>

>>> As

>>> I mentioned before, all XP machines are able to join to the domain

>>> with the Netbios name but not Vista machines (work if I use FQDN).

>>>

>>> We are educational organization and have a qualified class B address

>>> assigned.

>>

>> OK, but that still doesn't mean you need them internally. I

>> understand that's not your department, but it's probably a bad

>> choice unless there's some compelling requirement.

>>

>>> I can't tell why we use public IP addresses and why there

>>> have so many DNS servers as I am not the network administrator. I am

>>> only responsible for the Windows servers.

>>

>> I'd ask them. This does impact what you work on.

>>> BTY, we don't use Windows DNS server in our network, we use BIND

>>> instead. Would it make a difference?

>>

>> You probably should be using AD-integrated DNS, but you don't

>> necessarily have to, as long as your DNS server supports dynamic

>> updates. If you open AD Domains and Trusts, what is the AD domain name

>> listed

>> there? Whatever it is, is the primary DNS suffix you should have on

>> all servers and clients.

>>>

>>> Lanwench [MVP - Exchange] wrote:

>>>> OM <om@discussions.microsoft.com> wrote:

>>>>> Vista PC

>>>>>

>>>>> Windows IP Configuration

>>>>>

>>>>> Host Name . . . . . . . . . . . . : pcs05

>>>>> Primary Dns Suffix . . . . . . . :

>>>>> Node Type . . . . . . . . . . . . : Hybrid

>>>>> IP Routing Enabled. . . . . . . . : No

>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>> DNS Suffix Search List. . . . . . : domain.com

>>>>>

>>>>> Ethernet adapter Local Area Connection:

>>>>>

>>>>> Connection-specific DNS Suffix . : domain.com

>>>>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>>>>> Connection

>>>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>>>> DHCP Enabled. . . . . . . . . . . : Yes

>>>>> Autoconfiguration Enabled . . . . : Yes

>>>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday,

>>>>> October 15, 2008 8:52:53 AM

>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>> 155.50.100.68

>>>>> 155.50.106.82

>>>>> 155.50.127.50

>>>>> 155.50.113.101

>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>>>

>>>>> Windows 2003 DC

>>>>>

>>>>> Windows IP Configuration

>>>>>

>>>>> Host Name . . . . . . . . . . . . : addc

>>>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>>>> Node Type . . . . . . . . . . . . : Unknown

>>>>> IP Routing Enabled. . . . . . . . : No

>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>>>> domain.com

>>>>>

>>>>> Ethernet adapter Local Area Connection:

>>>>>

>>>>> Connection-specific DNS Suffix . :

>>>>>

>>>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI

>>>>> Fast Ethernet NIC

>>>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>>>> DHCP Enabled. . . . . . . . . . . : No

>>>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>> 155.50.100.68

>>>>>

>>>> OK - you've got addomain.domain.com as the DNS suffix on your DC,

>>>> but domain.com on the client.

>>>> Also, why are you using public IPs on your LAN, and why so many DNS

>>>> server IPs on the client?

>>>>>

>>>>> Lanwench [MVP - Exchange] wrote:

>>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>>> Hi

>>>>>>>

>>>>>>> I am unable to join my Vista business machine to a windows 2003

>>>>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>>>>> working as I can browse the domain and use net use to map

>>>>>>> network drive on all DCs within the domain. Also, all Windows

>>>>>>> XP machines can join to the domain with netbios name.

>>>>>>>

>>>>>>> Netbios over tcpip is enabled and IPV6/local firewall is

>>>>>>> disabled. All client machines are on the same subnet. No WINS

>>>>>>> is used on the network.

>>>>>>> The error message is:

>>>>>>> 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. Any idea?

>>>>>>>

>>>>>>> Thanks

>>>>>> Please post the unedited output of an ipconfig /all from this PC

>>>>>> and one of your DCs.

October 16, 2008

Re: unable to join to the domain with netbios name

I still don't understand why Vista can not resolve the netbios name of

the domain if Netbios over TCP/IP is enabled.

Lanwench [MVP - Exchange] wrote:

> OM <om@discussions.microsoft.com> wrote:

>> If I ping the server's netbios name form its console, I got

>> addc.addomain.domain.com reply. And the AD domain name listed in the

>> Domain and Trust utility is addomain.adomin.com

>

> Then change the primary DNS suffix in your DHCP scope to

> addomain.domain.com.

>>

>> Lanwench [MVP - Exchange] wrote:

>>> OM <om@discussions.microsoft.com> wrote:

>>>> addomin is the netbios name of the Active Directory.

>>> OK.

>>>

>>> The DC

>>>> automatically added addomain.domain.com as the primary DNS suffix

>>>> when it joined to the domain.

>>> No, it shouldn't have. What you showed in the ipconfig /all

>>> indicates that addomain.domain.com is the domain name.

>>>

>>> From the server itself, if you ping the server's NetBIOS name, what

>>> FQDN does it return?

>>>

>>>> By default, the dhcp server assigns

>>>> domain.com as the DNS suffix for all dhcp clients on the network. w

>>> Only because someone set it up to do that.

>>>

>>>> As

>>>> I mentioned before, all XP machines are able to join to the domain

>>>> with the Netbios name but not Vista machines (work if I use FQDN).

>>>>

>>>> We are educational organization and have a qualified class B address

>>>> assigned.

>>> OK, but that still doesn't mean you need them internally. I

>>> understand that's not your department, but it's probably a bad

>>> choice unless there's some compelling requirement.

>>>

>>>> I can't tell why we use public IP addresses and why there

>>>> have so many DNS servers as I am not the network administrator. I am

>>>> only responsible for the Windows servers.

>>> I'd ask them. This does impact what you work on.

>>>> BTY, we don't use Windows DNS server in our network, we use BIND

>>>> instead. Would it make a difference?

>>> You probably should be using AD-integrated DNS, but you don't

>>> necessarily have to, as long as your DNS server supports dynamic

>>> updates. If you open AD Domains and Trusts, what is the AD domain name

>>> listed

>>> there? Whatever it is, is the primary DNS suffix you should have on

>>> all servers and clients.

>>>> Lanwench [MVP - Exchange] wrote:

>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>> Vista PC

>>>>>>

>>>>>> Windows IP Configuration

>>>>>>

>>>>>> Host Name . . . . . . . . . . . . : pcs05

>>>>>> Primary Dns Suffix . . . . . . . :

>>>>>> Node Type . . . . . . . . . . . . : Hybrid

>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>> DNS Suffix Search List. . . . . . : domain.com

>>>>>>

>>>>>> Ethernet adapter Local Area Connection:

>>>>>>

>>>>>> Connection-specific DNS Suffix . : domain.com

>>>>>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>>>>>> Connection

>>>>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>>>>> DHCP Enabled. . . . . . . . . . . : Yes

>>>>>> Autoconfiguration Enabled . . . . : Yes

>>>>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>>>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday,

>>>>>> October 15, 2008 8:52:53 AM

>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>> 155.50.100.68

>>>>>> 155.50.106.82

>>>>>> 155.50.127.50

>>>>>> 155.50.113.101

>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>>>>

>>>>>> Windows 2003 DC

>>>>>>

>>>>>> Windows IP Configuration

>>>>>>

>>>>>> Host Name . . . . . . . . . . . . : addc

>>>>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>>>>> Node Type . . . . . . . . . . . . : Unknown

>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>>>>> domain.com

>>>>>>

>>>>>> Ethernet adapter Local Area Connection:

>>>>>>

>>>>>> Connection-specific DNS Suffix . :

>>>>>>

>>>>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI

>>>>>> Fast Ethernet NIC

>>>>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>>>>> DHCP Enabled. . . . . . . . . . . : No

>>>>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>> 155.50.100.68

>>>>>>

>>>>> OK - you've got addomain.domain.com as the DNS suffix on your DC,

>>>>> but domain.com on the client.

>>>>> Also, why are you using public IPs on your LAN, and why so many DNS

>>>>> server IPs on the client?

>>>>>> Lanwench [MVP - Exchange] wrote:

>>>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>>>> Hi

>>>>>>>>

>>>>>>>> I am unable to join my Vista business machine to a windows 2003

>>>>>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>>>>>> working as I can browse the domain and use net use to map

>>>>>>>> network drive on all DCs within the domain. Also, all Windows

>>>>>>>> XP machines can join to the domain with netbios name.

>>>>>>>>

>>>>>>>> Netbios over tcpip is enabled and IPV6/local firewall is

>>>>>>>> disabled. All client machines are on the same subnet. No WINS

>>>>>>>> is used on the network.

>>>>>>>> The error message is:

>>>>>>>> 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. Any idea?

>>>>>>>>

>>>>>>>> Thanks

>>>>>>> Please post the unedited output of an ipconfig /all from this PC

>>>>>>> and one of your DCs.

>

October 16, 2008

Re: unable to join to the domain with netbios name

This is Vista issue as all XP machines can join to the domain with

netbios name using the domain.com DNS suffix.

Lanwench [MVP - Exchange] wrote:

> OM <om@discussions.microsoft.com> wrote:

>> If I ping the server's netbios name form its console, I got

>> addc.addomain.domain.com reply. And the AD domain name listed in the

>> Domain and Trust utility is addomain.adomin.com

>

> Then change the primary DNS suffix in your DHCP scope to

> addomain.domain.com.

>>

>> Lanwench [MVP - Exchange] wrote:

>>> OM <om@discussions.microsoft.com> wrote:

>>>> addomin is the netbios name of the Active Directory.

>>> OK.

>>>

>>> The DC

>>>> automatically added addomain.domain.com as the primary DNS suffix

>>>> when it joined to the domain.

>>> No, it shouldn't have. What you showed in the ipconfig /all

>>> indicates that addomain.domain.com is the domain name.

>>>

>>> From the server itself, if you ping the server's NetBIOS name, what

>>> FQDN does it return?

>>>

>>>> By default, the dhcp server assigns

>>>> domain.com as the DNS suffix for all dhcp clients on the network. w

>>> Only because someone set it up to do that.

>>>

>>>> As

>>>> I mentioned before, all XP machines are able to join to the domain

>>>> with the Netbios name but not Vista machines (work if I use FQDN).

>>>>

>>>> We are educational organization and have a qualified class B address

>>>> assigned.

>>> OK, but that still doesn't mean you need them internally. I

>>> understand that's not your department, but it's probably a bad

>>> choice unless there's some compelling requirement.

>>>

>>>> I can't tell why we use public IP addresses and why there

>>>> have so many DNS servers as I am not the network administrator. I am

>>>> only responsible for the Windows servers.

>>> I'd ask them. This does impact what you work on.

>>>> BTY, we don't use Windows DNS server in our network, we use BIND

>>>> instead. Would it make a difference?

>>> You probably should be using AD-integrated DNS, but you don't

>>> necessarily have to, as long as your DNS server supports dynamic

>>> updates. If you open AD Domains and Trusts, what is the AD domain name

>>> listed

>>> there? Whatever it is, is the primary DNS suffix you should have on

>>> all servers and clients.

>>>> Lanwench [MVP - Exchange] wrote:

>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>> Vista PC

>>>>>>

>>>>>> Windows IP Configuration

>>>>>>

>>>>>> Host Name . . . . . . . . . . . . : pcs05

>>>>>> Primary Dns Suffix . . . . . . . :

>>>>>> Node Type . . . . . . . . . . . . : Hybrid

>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>> DNS Suffix Search List. . . . . . : domain.com

>>>>>>

>>>>>> Ethernet adapter Local Area Connection:

>>>>>>

>>>>>> Connection-specific DNS Suffix . : domain.com

>>>>>> Description . . . . . . . . . . . : Intel® PRO/100 VE Network

>>>>>> Connection

>>>>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>>>>> DHCP Enabled. . . . . . . . . . . : Yes

>>>>>> Autoconfiguration Enabled . . . . : Yes

>>>>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>>>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday,

>>>>>> October 15, 2008 8:52:53 AM

>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>> 155.50.100.68

>>>>>> 155.50.106.82

>>>>>> 155.50.127.50

>>>>>> 155.50.113.101

>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>>>>

>>>>>> Windows 2003 DC

>>>>>>

>>>>>> Windows IP Configuration

>>>>>>

>>>>>> Host Name . . . . . . . . . . . . : addc

>>>>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>>>>> Node Type . . . . . . . . . . . . : Unknown

>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>>>>> domain.com

>>>>>>

>>>>>> Ethernet adapter Local Area Connection:

>>>>>>

>>>>>> Connection-specific DNS Suffix . :

>>>>>>

>>>>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI

>>>>>> Fast Ethernet NIC

>>>>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>>>>> DHCP Enabled. . . . . . . . . . . : No

>>>>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>> 155.50.100.68

>>>>>>

>>>>> OK - you've got addomain.domain.com as the DNS suffix on your DC,

>>>>> but domain.com on the client.

>>>>> Also, why are you using public IPs on your LAN, and why so many DNS

>>>>> server IPs on the client?

>>>>>> Lanwench [MVP - Exchange] wrote:

>>>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>>>> Hi

>>>>>>>>

>>>>>>>> I am unable to join my Vista business machine to a windows 2003

>>>>>>>> domain using netbios name, FQDN is fine. Netbios resolution is

>>>>>>>> working as I can browse the domain and use net use to map

>>>>>>>> network drive on all DCs within the domain. Also, all Windows

>>>>>>>> XP machines can join to the domain with netbios name.

>>>>>>>>

>>>>>>>> Netbios over tcpip is enabled and IPV6/local firewall is

>>>>>>>> disabled. All client machines are on the same subnet. No WINS

>>>>>>>> is used on the network.

>>>>>>>> The error message is:

>>>>>>>> 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. Any idea?

>>>>>>>>

>>>>>>>> Thanks

>>>>>>> Please post the unedited output of an ipconfig /all from this PC

>>>>>>> and one of your DCs.

>

October 17, 2008

Re: unable to join to the domain with netbios name

OM <om@discussions.microsoft.com> wrote:

> This is Vista issue as all XP machines can join to the domain with

> netbios name using the domain.com DNS suffix.

>

Sorry, but I don't know what else to tell you, dude. All I know is that your

DNS suffix is wrong, and I wouldn't expect the XP machines to be working

properly either. :-(

Try posting in microsoft.public.windows.server.dns (a new post with all the

updated info) if you want a second opinion.

> Lanwench [MVP - Exchange] wrote:

>> OM <om@discussions.microsoft.com> wrote:

>>> If I ping the server's netbios name form its console, I got

>>> addc.addomain.domain.com reply. And the AD domain name listed in the

>>> Domain and Trust utility is addomain.adomin.com

>>

>> Then change the primary DNS suffix in your DHCP scope to

>> addomain.domain.com.

>>>

>>> Lanwench [MVP - Exchange] wrote:

>>>> OM <om@discussions.microsoft.com> wrote:

>>>>> addomin is the netbios name of the Active Directory.

>>>> OK.

>>>>

>>>> The DC

>>>>> automatically added addomain.domain.com as the primary DNS suffix

>>>>> when it joined to the domain.

>>>> No, it shouldn't have. What you showed in the ipconfig /all

>>>> indicates that addomain.domain.com is the domain name.

>>>>

>>>> From the server itself, if you ping the server's NetBIOS name, what

>>>> FQDN does it return?

>>>>

>>>>> By default, the dhcp server assigns

>>>>> domain.com as the DNS suffix for all dhcp clients on the network.

>>>>> w

>>>> Only because someone set it up to do that.

>>>>

>>>>> As

>>>>> I mentioned before, all XP machines are able to join to the domain

>>>>> with the Netbios name but not Vista machines (work if I use FQDN).

>>>>>

>>>>> We are educational organization and have a qualified class B

>>>>> address assigned.

>>>> OK, but that still doesn't mean you need them internally. I

>>>> understand that's not your department, but it's probably a bad

>>>> choice unless there's some compelling requirement.

>>>>

>>>>> I can't tell why we use public IP addresses and why there

>>>>> have so many DNS servers as I am not the network administrator. I

>>>>> am only responsible for the Windows servers.

>>>> I'd ask them. This does impact what you work on.

>>>>> BTY, we don't use Windows DNS server in our network, we use BIND

>>>>> instead. Would it make a difference?

>>>> You probably should be using AD-integrated DNS, but you don't

>>>> necessarily have to, as long as your DNS server supports dynamic

>>>> updates. If you open AD Domains and Trusts, what is the AD domain

>>>> name listed

>>>> there? Whatever it is, is the primary DNS suffix you should have on

>>>> all servers and clients.

>>>>> Lanwench [MVP - Exchange] wrote:

>>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>>> Vista PC

>>>>>>>

>>>>>>> Windows IP Configuration

>>>>>>>

>>>>>>> Host Name . . . . . . . . . . . . : pcs05

>>>>>>> Primary Dns Suffix . . . . . . . :

>>>>>>> Node Type . . . . . . . . . . . . : Hybrid

>>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>>> DNS Suffix Search List. . . . . . : domain.com

>>>>>>>

>>>>>>> Ethernet adapter Local Area Connection:

>>>>>>>

>>>>>>> Connection-specific DNS Suffix . : domain.com

>>>>>>> Description . . . . . . . . . . . : Intel® PRO/100 VE

>>>>>>> Network Connection

>>>>>>> Physical Address. . . . . . . . . : 00-11-11-47-D4-68

>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes

>>>>>>> Autoconfiguration Enabled . . . . : Yes

>>>>>>> IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)

>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>>> Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008

>>>>>>> 8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday,

>>>>>>> October 15, 2008 8:52:53 AM

>>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>>> DHCP Server . . . . . . . . . . . : 155.50.100.186

>>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>>> 155.50.100.68

>>>>>>> 155.50.106.82

>>>>>>> 155.50.127.50

>>>>>>> 155.50.113.101

>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled

>>>>>>>

>>>>>>> Windows 2003 DC

>>>>>>>

>>>>>>> Windows IP Configuration

>>>>>>>

>>>>>>> Host Name . . . . . . . . . . . . : addc

>>>>>>> Primary Dns Suffix . . . . . . . : addomain.domain.com

>>>>>>> Node Type . . . . . . . . . . . . : Unknown

>>>>>>> IP Routing Enabled. . . . . . . . : No

>>>>>>> WINS Proxy Enabled. . . . . . . . : No

>>>>>>> DNS Suffix Search List. . . . . . : addomain.domain.com

>>>>>>> domain.com

>>>>>>>

>>>>>>> Ethernet adapter Local Area Connection:

>>>>>>>

>>>>>>> Connection-specific DNS Suffix . :

>>>>>>>

>>>>>>> Description . . . . . . . . . . . : Realtek RTL8139 Family

>>>>>>> PCI Fast Ethernet NIC

>>>>>>> Physical Address. . . . . . . . . : 00-16-3E-00-00-21

>>>>>>> DHCP Enabled. . . . . . . . . . . : No

>>>>>>> IP Address. . . . . . . . . . . . : 155.50.100.220

>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.224.0

>>>>>>> Default Gateway . . . . . . . . . : 155.50.100.18

>>>>>>> DNS Servers . . . . . . . . . . . : 155.50.100.19

>>>>>>> 155.50.100.68

>>>>>>>

>>>>>> OK - you've got addomain.domain.com as the DNS suffix on your DC,

>>>>>> but domain.com on the client.

>>>>>> Also, why are you using public IPs on your LAN, and why so many

>>>>>> DNS server IPs on the client?

>>>>>>> Lanwench [MVP - Exchange] wrote:

>>>>>>>> OM <om@discussions.microsoft.com> wrote:

>>>>>>>>> Hi

>>>>>>>>>

>>>>>>>>> I am unable to join my Vista business machine to a windows

>>>>>>>>> 2003 domain using netbios name, FQDN is fine. Netbios

>>>>>>>>> resolution is working as I can browse the domain and use net

>>>>>>>>> use to map network drive on all DCs within the domain. Also,

>>>>>>>>> all Windows XP machines can join to the domain with netbios

>>>>>>>>> name. Netbios over tcpip is enabled and IPV6/local firewall is

>>>>>>>>> disabled. All client machines are on the same subnet. No WINS

>>>>>>>>> is used on the network.

>>>>>>>>> The error message is:

>>>>>>>>> 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. Any idea?

>>>>>>>>>

>>>>>>>>> Thanks

>>>>>>>> Please post the unedited output of an ipconfig /all from this

>>>>>>>> PC and one of your DCs.

Sign In

unable to join to the domain with netbios name

Recommended Posts

Guest OM

Popular Days

Popular Days

Guest Lanwench [MVP - Exchange]

Guest Richard Mueller [MVP]

Guest OM

Guest Lanwench [MVP - Exchange]

Guest OM

Guest Lanwench [MVP - Exchange]

Guest OM

Guest Lanwench [MVP - Exchange]

Guest OM

Guest OM

Guest Lanwench [MVP - Exchange]

Similar Content

Can't join a domain with my VM

Error joining Active Directory domain

Cant join new Domain controller to existing domain

Are there guides available to migrate AD and DNS to a new domain name? We are having to change our domain name from example.com to test.com(used as an

Rds Gateway Domain name issues

Browse

Activity

Site Info