Re: NetBIOS name doesn't work when joining a workstation to domain
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 19 Mar 2008 12:53:33 -0400
Umma Gumma <UmmaGumma@xxxxxxxxxxxxxxxxxxxxxxxxx> 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.
.
- Follow-Ups:
- Re: NetBIOS name doesn't work when joining a workstation to domain
- From: Umma Gumma
- Re: NetBIOS name doesn't work when joining a workstation to domain
- References:
- NetBIOS name doesn't work when joining a workstation to domain
- From: Umma Gumma
- NetBIOS name doesn't work when joining a workstation to domain
- Prev by Date: NetBIOS name doesn't work when joining a workstation to domain
- Next by Date: Network share: What causes " ~ $files" temp files?
- Previous by thread: NetBIOS name doesn't work when joining a workstation to domain
- Next by thread: Re: NetBIOS name doesn't work when joining a workstation to domain
- Index(es):
Relevant Pages
|