Discussion Locked

NetBIOS Logon Please Help!

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

have seen this question posted all over the web and on every forum I frequent and I have yet to see someone conclusively answer it! I have a new 2003 domain with AD configured. I cannot logon to the domain unless I use the NETBIOS domain name or by cheating and using the USER@SOMEDOMAIN.COM.
DNS was configured by DCPROMO at the time AD was installed and I have created a reverse lookup pointer for the server. The only answer I have seen posted to this apparently common problem is that it is probably some kind of DNS error and its left at that!!! ARGHH! Someone please help me! I have read every tech book and website I can get my hands on and I cannot resolve this. Thanks, in advance!

10 replies

by cg it

are you talking about the domain name thats listed in the drop down box, when you click options on the log on screen, and the prompt says Log on to:? Gives you a choice of local machine or a domain?

If so, this is by design and is for backward compatibility with W9X and NT clients that use NetBIOS over TCP/IP to locate domain controllers. Here is a Microsoft KB that discusses the flat NetBIOS name and backward compatibility.

This is an article on how to disable NetBIOS name resolution in DNS. http://support.microsoft.com/default.aspx?scid=kb;en-us;137368

http://support.microsoft.com/default.aspx?scid=kb;en-us;247811

by cg it

well the links didn't come out right. The second link KB 247811 is for the flat NetBIOS name used to locate DNS servers in older clients.

by cg it

ok so what your saying is that you can only log on using the UPN?

or is it you can not log on using the UPN?

there is a problem using a all numeric UPN and is fixable with a hotfix.

it's possible the UPN suffix isn't recognizable in AD.

Could use a little more info on exactly whats happening.

by jpatterson

Thank you so much... I don't know why I couldnt find that myself! However, I still cannot logon to the domain unless I use the USER@SOMEDOMAIN.COM login. Merely using the AD user name and password with the domain name selected at the lgin screen generates an error "The system could not log you on. Make sure you have the correct user name and password". Any thoughts?

by jpatterson

Ok, let me back up a bit then. First of all, joining a client to the domain works with no problems. Trouble begins when a client attempts to logon to the domain from their machine. The domain drop down window shows the NETBIOS domain name, as previously mentioned. The users must either use the NETBIOS user name or the UPN name to logon.

by jpatterson

I just noticed something else... all the permissions in my files reference the NETBIOS name (i.e. SOMEDOMAIN\ACCOUNTING) rather then the domain name.. is this by design also?

by jpatterson

When I disabled Global Catalog server, I was able to login with the 2003 domain name listed... however the server still treats it like a netbios login. I am currently logged into it as DOMAIN\USER rather then USER@DOMAIN.COM. This is so frustrating

by jpatterson

I should add that I have run DCDiag, netdiag and nslookup and all check out ok... sorry I thought I had posted that earlier.

by curlergirl

Are all of your users having the same problem? I have seen some similar behavior in cases where the Account information in the User Properties in AD is not filled in properly. Check to be sure that the "User login name" and the "User login name (pre-Windows 2000)" fields on the Account tab in the User properties are both filled in and that they contain the same name. That is, if the User login name is JDoe, then the pre-Windows 2000 field should also be "JDoe."

Hope this helps!

This discussion is closed to new replies.