C
chris.baker
Hi,
We need to get the server to respond to a netbios name that is not it's primary name this is accomplished using the OptionalNames registry key we have successfully implemented this on a file and print server that is not a domain controller, but when we use it on a server that is a domain controller the netlogon service removes any additional netbios names we assign when it starts. If we stop the netlogon service and restart the server service we see the OptionalNames we entered registered in the Netbios cache and in WINS, but as soon as we start the netlogon service these entries are removed.
This functionality is required to allow us to perform replacement of existing File and Print servers with new names but also ensure that legacy clients do not require updates to access to the new server and can continue to use the old server name.
Has anyone used this on a domain controller or does anyone have any ideas as to why this does not work.
Many thanks
Chris
We need to get the server to respond to a netbios name that is not it's primary name this is accomplished using the OptionalNames registry key we have successfully implemented this on a file and print server that is not a domain controller, but when we use it on a server that is a domain controller the netlogon service removes any additional netbios names we assign when it starts. If we stop the netlogon service and restart the server service we see the OptionalNames we entered registered in the Netbios cache and in WINS, but as soon as we start the netlogon service these entries are removed.
This functionality is required to allow us to perform replacement of existing File and Print servers with new names but also ensure that legacy clients do not require updates to access to the new server and can continue to use the old server name.
Has anyone used this on a domain controller or does anyone have any ideas as to why this does not work.
Many thanks
Chris