locked
Adding Computer to Domain using NETBIOS name. RRS feed

  • Question

  • When trying to add a computer to the domain Win xp or Win 7 clients using just the Netbios name for the domain we get "An Active DIrectory Domain Controller (AD DC) for the domain "Domain" could not be contacted.  But if we use the FQDN (domain.local) it works fine.  My environment is below.

    I have a Windows 2003 Forest/domain level Domain.  I am running a mixure of Win 2003 and Windows 2008 domain controllers.  We are not using WINS.  THe DHCP scope is hading out the DNS suffix domain.local.

    To use the netbios name for the domain to add a computer do you need WINS? 

    Thanks,

    Steve 


    Steve

    Tuesday, July 16, 2013 7:46 PM

Answers

  • The reason is broadcasting name resolution doesn't works with the router as router doesn't allow broadcast traffic. So, the name resolution will work only if the DC is present in the local site where domain joined has performed using netbios name. This can be achieved by introducing WINS server in the domain for the client to directly contact for the resolution using WINS server.

    http://www.techrepublic.com/article/how-netbios-name-resolution-really-works/


    Awinish Vishwakarma - MVP

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Proposed as answer by Meinolf Weber Wednesday, July 17, 2013 6:07 AM
    • Marked as answer by Steve Acx Wednesday, July 17, 2013 1:55 PM
    Wednesday, July 17, 2013 1:15 AM

All replies

  • Could you try adding .local as an additional DNS suffix in DHCP settings (Option 119)?
    Tuesday, July 16, 2013 7:51 PM
  • The reason is broadcasting name resolution doesn't works with the router as router doesn't allow broadcast traffic. So, the name resolution will work only if the DC is present in the local site where domain joined has performed using netbios name. This can be achieved by introducing WINS server in the domain for the client to directly contact for the resolution using WINS server.

    http://www.techrepublic.com/article/how-netbios-name-resolution-really-works/


    Awinish Vishwakarma - MVP

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Proposed as answer by Meinolf Weber Wednesday, July 17, 2013 6:07 AM
    • Marked as answer by Steve Acx Wednesday, July 17, 2013 1:55 PM
    Wednesday, July 17, 2013 1:15 AM
  • Thanks Awinish, I just needed confirmation that a WINS server was needed.  Using the netbios name is not a requirement just a convenience for my desktop support techs.  Also, I noticed that the Computer Browser service on the WIN 2008 DC's which are my primary DNS servers is disabled by default.  SO I am wondering if turing that on would help?

    Thanks,

    Steve


    Steve

    Wednesday, July 17, 2013 2:01 PM
  • Thanks Tomas, I believe that windows clients do not request option 119.  You have to push that via group policy, but in my case GP's will not be applied until the computer is added to the domain.

    Steve


    Steve

    Wednesday, July 17, 2013 2:05 PM
  • Browser is not related with the name resolution, instead its used for listing windows network devices in the my network place. Netbios are no more used & its replace by GlobalzoneDNS. WINS were used by legacy application which do not support FQDN are were only designed for netbios name support. I would suggest let computer browser service is set to be enabled and automatic.

    http://technet.microsoft.com/en-us/library/cc787537%28v=ws.10%29.aspx

    http://technet.microsoft.com/en-us/library/cc731744.aspx


    Awinish Vishwakarma - MVP

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Thursday, July 18, 2013 12:36 AM