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


"Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:e95rbEfiIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
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.

.

Relevant Pages

  • Re: Workstation Authentication
    ... When I log on from a workstation, should it make any difference if I use the NetBIOS name vs. the FQDN? ... I get to the same user profile on the workstation, but the workstation seems to operate a little differently when I chose one over the other. ... I always assumed that the shorter name goes back to an older version of Microsoft that may not have allowed longer domain names. ...
    (microsoft.public.windows.server.security)
  • Re: NetBIOS name doesnt work when joining a workstation to domain
    ... workstation to our domain using its NetBIOS name, ... If I use the FQDN instead, ... DNS problem, most likely - try posting an unedited ipconfig /all from your ...
    (microsoft.public.windows.server.general)
  • Re: Use of NetBIOS vs FQDN
    ... the workstation may see a server ... NetBIOS name vs. the FQDN as the domain? ...
    (microsoft.public.windows.server.security)
  • Use of NetBIOS vs FQDN
    ... When I log on from a workstation, should it make any difference if I use the ... NetBIOS name vs. the FQDN as the domain? ... Isn't there an intention to do away with NetBIOS over time? ...
    (microsoft.public.windows.server.security)
  • Re: Active Directory Logon to attribute
    ... We are not able to ping the workstation in the ... I have checked and found that netbios resolves the host name using broadcast ... for this reason I wanted to understand how the "logon to" works. ... named xyz.org for the user authentication for internet. ...
    (microsoft.public.windows.server.active_directory)
Quantcast