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

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

Thanks


"ChuckN" <Chuck@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:50315009-07C0-4BCE-9D69-242B54BE4A4D@xxxxxxxxxxxxxxxx
Thanks for your help.



"S. Pidgorny <MVP>" <slavickp@xxxxxxxxx> wrote in message news:%23VseiqUOIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Windows NT 3.1 legacy is the reason. For every "long" (fully-qualified domain) name a unique NetBIOS name is created. You can still use FQDN in all applications and scripts

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *

"ChuckN" <Chuck@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:299D40EC-4806-43D2-8062-0D54E616FD7C@xxxxxxxxxxxxxxxx
Thank you Svyatoslav

TO help me understand, why doesn't it just use / respond to the longname?


"S. Pidgorny <MVP>" <slavickp@xxxxxxxxx> wrote in message news:e1nAH0LOIHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
Yes - that is the machine's NetBIOS name, so everything's legit.

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *

"ChuckN" <Chuck@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0977F607-7E7B-4C0D-9E57-C2014EAED522@xxxxxxxxxxxxxxxx
Thanks

Our domain name is 0123456789ABCDEFGH.COM

When we enter that name, our DC will come back with the account found was
0123456789ABCDE

Last last 3 characters and the .com are left off.

I assumed this might be a NetBIOS or WINS shortened name the server is
using. Quite often, the DC seems to use the terms interchangeably. I most
often try to join the domain using the longname, but have found that
sometimes it will respond that the longname was not found and suggests says
that the short name was found and asks if I want to use that. If I say yes
and proceed, it joins me to the domain using the short name.

I hope this helps.






"S. Pidgorny <MVP>" <slavickp@xxxxxxxxx> wrote in message news:OgdeiJyNIHA.484@xxxxxxxxxxxxxxxxxxxxxxx
Please elaborate?

Your domain is 0123456789ABCDEFzz.com, and you see workstations using 0123456789ABCDE.com? Where?

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *

"ChuckN" <Chuck@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:218EC512-AEE5-4FE8-BB05-9370A0C1A8B3@xxxxxxxxxxxxxxxx
I have not been able to understand how W2K3 Server Enterprise uses domain names.

Our domain name is an 18 character.com name. I noticed that often, only the first 15 characters are used, excluding the last three characters + the .com.

Usually the names are used interchangeably. Once in awhile, that does not seem to be the case.

When I authenticate as the shorter name, the server seems to automatically use the longer name.

I always assumed that the shorter name goes back to an older version of Microsoft that may not have allowed longer domain names.

Is there a potential problem using the names interchangeably?

Thanks for your help.














.

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: 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: NetBIOS name doesnt work when joining a workstation to domain
    ... workstation to our domain using its NetBIOS name, ... Is this Server 2003 SP2? ... W2k and later use DNS to find the ...
    (microsoft.public.windows.server.general)