Setting up optionalnames on Server so it has 2 alias

Posted on 2009-04-16
Last Modified: 2013-12-23
We have installed a new server (serverB) which replaces (serverA), the shares are exactly the same for example serverA\Share and serverB\Share

Following i have setup in the registry OptionalNames and added serverA and ServerB, i have also added to the registry disablestricknamechecking

Also in DNS i have set pointers for ServerA to point to serverB IP address

ServerA is now turned off

But when i try to navigate to ServerA\Share it doesnt work

I can ping serverA and it pings the correct IP of serverB

This new ServerB is running 2003 R2 64bit

Any advice will be great
Question by:David
    LVL 59

    Expert Comment

    by:Darius Ghassem
    Why not just change the logon script to set the network drives up to the new server. If you don't have a logon script then create one. This can cause issues the way you are doing it.

    net user d: \\servername\share
    LVL 82

    Accepted Solution

    Note that the registry key is named DisableStrictNameChecking; verify the entry is there with that name, set to 1, and that the server has been rebooted since creating the entry. In addition, you'll need to delete the computer account of ServerA in AD before you'll be able to connect to ServerB using ServerA's name.
    Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name

    Author Comment

    oBdA - ok the only thing i didnt do was remove the old server from AD

    yes the reg entry was correct, but can you tell me do i use both DisableStrictNameChecking and optionalnames? or just DisableStrictNameChecking?

    If alias names dont work with shares what is the point of them?

    Im just testing now
    LVL 82

    Expert Comment

    They do work and DisableStrictNameChecking should be enough (though there shouldn't be issues when both are active); I've used the DisableStrictNameChecking entry successfully.
    For testing, you can simply create an alias of a name that's not in use, then delete the account when you're ready to get rid of the old server (make sure you know the *local* admin password, so you can rejoin it if something goes wrong).

    Author Comment

    well i have both active and it works great, i didnt even think of deleting the old server in AD but that did the trick


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now