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? 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. Are there any benefits of using one over the
other?

Isn't there an intention to do away with NetBIOS over time?

Thanks

.

Relevant Pages

  • 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)
  • Re: Active Directory Logon to attribute
    ... The "logon to" feature must use IADSNameTranslate to convert the NetBIOS ... netbios name for the workstation in abc.com. ... named xyz.org for the user authentication for internet. ...
    (microsoft.public.windows.server.active_directory)
  • 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, ... Using just the child domain name would probably work if the workstation had the parent domain suffix coded into it. ...
    (microsoft.public.windows.server.general)
  • 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)