Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
I'm using a windows 2000 network running in native mode. MY question is why does the netbios name have to be used when adding computers to a domain. For example, if your domain is test.com in order to add to domain you must simpley put in test not test.com.
It's not a NetBIOS name (although the netBIOS name may infact be that). What it is, is the computer name. The client then appends the rest of the FQDN. It makes things easier.
It isn't the Netbios name you are entering.. you are getting it to work by using the hidden backwards compatible domain naming scheme of Windows 2000 domain.
You may also put test.com and it should work for you. There is an option to select what your Non-Win2k or beyond clients will see the domain as since Win9x/ME do not use FQDN as their Domain structure they use a single domain name so this is more or less a backwards compatible option you are using not the netbios name.
You technically <should> put Test.com when you're adding to the domain. Win2k likes you to use FQDNs wherever possible because is saves on lookups. That said, it'll work either way because of the backwards-compatibility thing santa mentioned.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.