4 replies
by duwaned
Hi.
I managed to find an MS Technet Article Q251398 which relates to this exact problem. From what the article says, this behaviour is by design in Windows 2000 and should not be. Previous versions of Windows never had this reaction.
I hope this helps you.
Regards.
Duwane
by duwaned
Hi.
I managed to find an MS Technet Article Q251398 which relates to this exact problem. From what the article says, this behaviour is by design in Windows 2000. Previous versions of Windows never had this reaction.
I hope this helps you.
Regards.
Duwane
by mdsnitc
Yes, we have seen this issue in our environment. As stated already, this is by design and MS Technicians were no help to us. Our work-around was to assign a NetBIOS alias "software.mydomain.com" and allow wins to manage the name. The result for you would look something like this:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
GRIFFIN <00> UNIQUE Registered
DOMIAN <00> GROUP Registered
GRIFFIN <03> UNIQUE Registered
GRIFFIN <20> UNIQUE Registered
SOFTWARE.MYDOMAIN.COM <20> UNIQUE Registered
HKEY_Local_Machine\System\CurrentControlSet\Services\LanmanServer\Parameters
Add Value: OptionalNames REG_SZ String: "Alias"
If you make it a type REG_MULTI_SZ, you can add multiple alsiases.
w2k is very dns dependant, it won't work fine without a correct dns resolution. Previous versions can use netbios to resolve the name, but not in the same order as win2k
Sp2 is supposed to solve this order.
Hope it helps!!
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending