NetBIOS name doesn't work when joining a workstation to domain

March 19, 2008

I've done a few searches in the past on this and have found the opposite of

the problem I'm having: When I attempt to join an XP SP2 workstation to our

domain using its NetBIOS name, the process times out and a message comes up.

Something to the effect of the domain cannot be located. If I use the FQDN

instead, the domain can be contacted and I get prompted for the credentials

to join the workstation. This is also a FQDN for a child domain:

child.parent.com Not sure if it makes a difference or not but I'm throwing

in as many details as possible.

If anyone has run into this problem and has found a solution or suggestions,

I would greatly appreciate it!

Thanks!

March 19, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

Umma Gumma <UmmaGumma@discussions.microsoft.com> wrote:

> I've done a few searches in the past on this and have found the

> opposite of the problem I'm having: When I attempt to join an XP SP2

> workstation to our domain using its NetBIOS name, the process times

> out and a message comes up. Something to the effect of the domain

> cannot be located. If I use the FQDN instead, the domain can be

> contacted and I get prompted for the credentials to join the

> workstation. This is also a FQDN for a child domain:

> child.parent.com Not sure if it makes a difference or not but I'm

> throwing in as many details as possible.

>

> If anyone has run into this problem and has found a solution or

> suggestions, I would greatly appreciate it!

>

> Thanks!

DNS problem, most likely - try posting an unedited ipconfig /all from your

DC and from the offending client workstation. AD uses DNS, not NetBIOS, but

if you have server01.domain.com you ought to be able to ping server01 (the

hostname) and get the FQDN in return.

March 19, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

>I've done a few searches in the past on this and have found the opposite of

>the problem I'm having: When I attempt to join an XP SP2 workstation to our

>domain using its NetBIOS name, the process times out and a message comes up.

>Something to the effect of the domain cannot be located. If I use the FQDN

>instead, the domain can be contacted and I get prompted for the credentials

>to join the workstation. This is also a FQDN for a child domain:

>child.parent.com Not sure if it makes a difference or not but I'm throwing

>in as many details as possible.

>

>If anyone has run into this problem and has found a solution or suggestions,

>I would greatly appreciate it!

>

>Thanks!

Is this Server 2003 SP2? Check out the following KB article:

http://support.microsoft.com/kb/875441

Anything in the Event Viewer that might give more clues?

How about using nbstat to do some diagnostics?

http://support.microsoft.com/kb/323388

You could always install the current hotfix for the NetBIOS driver and

see if it helps:

http://support.microsoft.com/kb/948354

- Thee Chicago Wolf

March 19, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

Thee Chicago Wolf <.@.> wrote:

>> I've done a few searches in the past on this and have found the

>> opposite of the problem I'm having: When I attempt to join an XP SP2

>> workstation to our domain using its NetBIOS name, the process times

>> out and a message comes up. Something to the effect of the domain

>> cannot be located. If I use the FQDN instead, the domain can be

>> contacted and I get prompted for the credentials to join the

>> workstation. This is also a FQDN for a child domain:

>> child.parent.com Not sure if it makes a difference or not but I'm

>> throwing in as many details as possible.

>>

>> If anyone has run into this problem and has found a solution or

>> suggestions, I would greatly appreciate it!

>>

>> Thanks!

>

> Is this Server 2003 SP2? Check out the following KB article:

> http://support.microsoft.com/kb/875441

>

> Anything in the Event Viewer that might give more clues?

> How about using nbstat to do some diagnostics?

> http://support.microsoft.com/kb/323388

>

> You could always install the current hotfix for the NetBIOS driver and

> see if it helps:

> http://support.microsoft.com/kb/948354

>

> - Thee Chicago Wolf

....this won't be a NetBIOS issue :-)

March 19, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

"Lanwench [MVP - Exchange]"

<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message

news:e95rbEfiIHA.3400@TK2MSFTNGP03.phx.gbl...

> Thee Chicago Wolf <.@.> wrote:

>>> I've done a few searches in the past on this and have found the

>>> opposite of the problem I'm having: When I attempt to join an XP SP2

>>> workstation to our domain using its NetBIOS name, the process times

>>> out and a message comes up. Something to the effect of the domain

>>> cannot be located. If I use the FQDN instead, the domain can be

>>> contacted and I get prompted for the credentials to join the

>>> workstation. This is also a FQDN for a child domain:

>>> child.parent.com Not sure if it makes a difference or not but I'm

>>> throwing in as many details as possible.

>>>

>>> If anyone has run into this problem and has found a solution or

>>> suggestions, I would greatly appreciate it!

>>>

>>> Thanks!

>>

>> Is this Server 2003 SP2? Check out the following KB article:

>> http://support.microsoft.com/kb/875441

>>

>> Anything in the Event Viewer that might give more clues?

>> How about using nbstat to do some diagnostics?

>> http://support.microsoft.com/kb/323388

>>

>> You could always install the current hotfix for the NetBIOS driver and

>> see if it helps:

>> http://support.microsoft.com/kb/948354

>>

>> - Thee Chicago Wolf

>

> ...this won't be a NetBIOS issue :-)

>

Not unless the OP is still running NT! W2k and later use DNS to find the

logon server. Using just the child domain name would probably work if the

workstation had the parent domain suffix coded into it. The DNS query would

then add the suffix to form the FQDN.

March 19, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

"Bill Grant" <not.available@online> wrote in message

news:OInzZKhiIHA.4080@TK2MSFTNGP03.phx.gbl...

>

> "Lanwench [MVP - Exchange]"

> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in

> message news:e95rbEfiIHA.3400@TK2MSFTNGP03.phx.gbl...

>> Thee Chicago Wolf <.@.> wrote:

>>>> I've done a few searches in the past on this and have found the

>>>> opposite of the problem I'm having: When I attempt to join an XP SP2

>>>> workstation to our domain using its NetBIOS name, the process times

>>>> out and a message comes up. Something to the effect of the domain

>>>> cannot be located. If I use the FQDN instead, the domain can be

>>>> contacted and I get prompted for the credentials to join the

>>>> workstation. This is also a FQDN for a child domain:

>>>> child.parent.com Not sure if it makes a difference or not but I'm

>>>> throwing in as many details as possible.

>>>>

>>>> If anyone has run into this problem and has found a solution or

>>>> suggestions, I would greatly appreciate it!

>>>>

>>>> Thanks!

>>>

>>> Is this Server 2003 SP2? Check out the following KB article:

>>> http://support.microsoft.com/kb/875441

>>>

>>> Anything in the Event Viewer that might give more clues?

>>> How about using nbstat to do some diagnostics?

>>> http://support.microsoft.com/kb/323388

>>>

>>> You could always install the current hotfix for the NetBIOS driver and

>>> see if it helps:

>>> http://support.microsoft.com/kb/948354

>>>

>>> - Thee Chicago Wolf

>>

>> ...this won't be a NetBIOS issue :-)

>>

>

> Not unless the OP is still running NT! W2k and later use DNS to find the

> logon server. Using just the child domain name would probably work if the

> workstation had the parent domain suffix coded into it. The DNS query

> would then add the suffix to form the FQDN.

>

>>>When I attempt to join an XP SP2...

....but they're not running NT. Back to looking at DNS,

/kj

March 20, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

Thanks to all who've given all their input about this. I will definitely

check out the articles that TCW posted. Our DCs are running Server 2003

Standard w/SP2. Workstations are XP Pro SP2. Also, our DCs are VMWare

virtual servers. Not sure if that complicates things or not. This problem

only recently started up. Maybe an update caused the problem?

It's sounding like this is more of a DNS issue but initially I wasn't sure.

Like I had stated originally, I can join a workstation with:

child.parent.com

but not:

CHILD

Below are ipconfigs from both our parent DC and child DC

Windows IP Configuration

Host Name . . . . . . . . . . . . : CORPDCAERO

Primary Dns Suffix . . . . . . . : av.com

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

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

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

DNS Suffix Search List. . . . . . : av.com

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . : av.com

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-34-8B-BB

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

IP Address. . . . . . . . . . . . : 192.168.8.104

Subnet Mask . . . . . . . . . . . : 255.255.252.0

Default Gateway . . . . . . . . . : 192.168.8.1

DNS Servers . . . . . . . . . . . : 192.168.8.104

192.168.20.104

192.168.7.72

192.168.32.104

Windows IP Configuration

Host Name . . . . . . . . . . . . : CORPDCAV

Primary Dns Suffix . . . . . . . : avpclan.av.com

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

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

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

DNS Suffix Search List. . . . . . : avpclan.av.com

av.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : avpclan.av.com

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-D2-4A-4E

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

IP Address. . . . . . . . . . . . : 192.168.8.105

Subnet Mask . . . . . . . . . . . : 255.255.252.0

Default Gateway . . . . . . . . . : 192.168.8.1

DNS Servers . . . . . . . . . . . : 192.168.8.104

192.168.32.104

192.168.20.104

"Lanwench [MVP - Exchange]" wrote:

> Umma Gumma <UmmaGumma@discussions.microsoft.com> wrote:

> > I've done a few searches in the past on this and have found the

> > opposite of the problem I'm having: When I attempt to join an XP SP2

> > workstation to our domain using its NetBIOS name, the process times

> > out and a message comes up. Something to the effect of the domain

> > cannot be located. If I use the FQDN instead, the domain can be

> > contacted and I get prompted for the credentials to join the

> > workstation. This is also a FQDN for a child domain:

> > child.parent.com Not sure if it makes a difference or not but I'm

> > throwing in as many details as possible.

> >

> > If anyone has run into this problem and has found a solution or

> > suggestions, I would greatly appreciate it!

> >

> > Thanks!

>

> DNS problem, most likely - try posting an unedited ipconfig /all from your

> DC and from the offending client workstation. AD uses DNS, not NetBIOS, but

> if you have server01.domain.com you ought to be able to ping server01 (the

> hostname) and get the FQDN in return.

>

March 20, 2008

Re: NetBIOS name doesn't work when joining a workstation to domain

Umma Gumma <UmmaGumma@discussions.microsoft.com> wrote:

> Thanks to all who've given all their input about this. I will

> definitely check out the articles that TCW posted. Our DCs are

> running Server 2003 Standard w/SP2. Workstations are XP Pro SP2.

> Also, our DCs are VMWare virtual servers. Not sure if that

> complicates things or not. This problem only recently started up.

> Maybe an update caused the problem?

>

> It's sounding like this is more of a DNS issue but initially I wasn't

> sure. Like I had stated originally, I can join a workstation with:

>

> child.parent.com

>

> but not:

>

> CHILD

But CHILD is not necessarily a NetBIOS thing in this context. CHILD is a

hostname on the parent.com network.

>

> Below are ipconfigs from both our parent DC and child DC

You didn't mention a parent/child setup initially, and I'm not sure why (or

whether it's relevant- I don't work with that setup much), so I may be off

base with some of my replies. If we can't make any headway in here, compose

a brand-new/updated post with all the relevant detail to

microsoft.public.windows.server.dns. That's where the gurus hang out

>

> <PARENT DC>

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : CORPDCAERO

> Primary Dns Suffix . . . . . . . : av.com

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

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

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

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

>

> Ethernet adapter Local Area Connection 3:

>

> Connection-specific DNS Suffix . : av.com

> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet

> Adapter Physical Address. . . . . . . . . : 00-0C-29-34-8B-BB

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

> IP Address. . . . . . . . . . . . : 192.168.8.104

> Subnet Mask . . . . . . . . . . . : 255.255.252.0

> Default Gateway . . . . . . . . . : 192.168.8.1

> DNS Servers . . . . . . . . . . . : 192.168.8.104

> 192.168.20.104

> 192.168.7.72

> 192.168.32.104

Are these DNS IPs correct? Are all four of these DNS servers in use for

av.com?

>

> <CHILD DC>

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : CORPDCAV

> Primary Dns Suffix . . . . . . . : avpclan.av.com

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

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

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

> DNS Suffix Search List. . . . . . : avpclan.av.com

> av.com

>

> Ethernet adapter Local Area Connection 2:

>

> Connection-specific DNS Suffix . : avpclan.av.com

> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet

> Adapter Physical Address. . . . . . . . . : 00-0C-29-D2-4A-4E

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

> IP Address. . . . . . . . . . . . : 192.168.8.105

> Subnet Mask . . . . . . . . . . . : 255.255.252.0

> Default Gateway . . . . . . . . . : 192.168.8.1

> DNS Servers . . . . . . . . . . . : 192.168.8.104

> 192.168.32.104

> 192.168.20.104

What server (or servers) handles DNS for avpclan.av.com ?

What about the *client* ipconfig /all? That's what matters here.

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Umma Gumma <UmmaGumma@discussions.microsoft.com> wrote:

>>> I've done a few searches in the past on this and have found the

>>> opposite of the problem I'm having: When I attempt to join an XP SP2

>>> workstation to our domain using its NetBIOS name, the process times

>>> out and a message comes up. Something to the effect of the domain

>>> cannot be located. If I use the FQDN instead, the domain can be

>>> contacted and I get prompted for the credentials to join the

>>> workstation. This is also a FQDN for a child domain:

>>> child.parent.com Not sure if it makes a difference or not but I'm

>>> throwing in as many details as possible.

>>>

>>> If anyone has run into this problem and has found a solution or

>>> suggestions, I would greatly appreciate it!

>>>

>>> Thanks!

>>

>> DNS problem, most likely - try posting an unedited ipconfig /all

>> from your DC and from the offending client workstation. AD uses DNS,

>> not NetBIOS, but if you have server01.domain.com you ought to be

>> able to ping server01 (the hostname) and get the FQDN in return.

March 21, 2008

RE: NetBIOS name doesn't work when joining a workstation to domain

Hi,

Is NetBios over TCP/IP enabled? Also is there any name in the "Primary DNS

suffix" on the workstation - My Computer Properties - Computer Name (Advanced

or Change). Sorry I am running Vista so the tabs are a bit different.

Cheers,

Lara

"Umma Gumma" wrote:

> I've done a few searches in the past on this and have found the opposite of

> the problem I'm having: When I attempt to join an XP SP2 workstation to our

> domain using its NetBIOS name, the process times out and a message comes up.

> Something to the effect of the domain cannot be located. If I use the FQDN

> instead, the domain can be contacted and I get prompted for the credentials

> to join the workstation. This is also a FQDN for a child domain:

> child.parent.com Not sure if it makes a difference or not but I'm throwing

> in as many details as possible.

>

> If anyone has run into this problem and has found a solution or suggestions,

> I would greatly appreciate it!

>

> Thanks!

>

Sign In

NetBIOS name doesn't work when joining a workstation to domain

Recommended Posts

Guest Umma Gumma

Popular Days

Popular Days

Guest Lanwench [MVP - Exchange]

Guest Thee Chicago Wolf

Guest Lanwench [MVP - Exchange]

Guest Bill Grant

Guest kj [SBS MVP}

Guest Umma Gumma

Guest Lanwench [MVP - Exchange]

Guest lforbes

Browse

Activity

Site Info