• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1914
  • Last Modified:

Setting up optionalnames on Server so it has 2 alias

We have installed a new server (serverB) which replaces (serverA), the shares are exactly the same for example serverA\Share and serverB\Share

Following http://www.netbros.com/OptionalNames 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
0
David
Asked:
David
  • 2
  • 2
1 Solution
 
Darius GhassemCommented:
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
0
 
oBdACommented:
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
http://support.microsoft.com/kb/281308
0
 
DavidAuthor Commented:
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
0
 
oBdACommented:
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).
0
 
DavidAuthor Commented:
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

cheers
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now