unable to access share after fileserver migration
Hi,
I just did file server migration from 2003 to 2016 using the following guide
https://community.spiceworks.com/how_to/75097-replace-an-old-file-server-with-a-new-file-server-using-the-same-ip-same-name-same-shares
All is working well as i am able to access the shares from computer with appropriate permission, however some of the shares had an alias for example \\servername\files\123 was called \\filestore\files\123. I am not able to accesss those shares,whenever i click on it i get a prompt that says you were not connected because duplicate name exist on the network.
I have renamed the old server, re IP'd it and even turned it off. Nothing in DNS records pointing to the old server. Any suggestions?
I just did file server migration from 2003 to 2016 using the following guide
https://community.spiceworks.com/how_to/75097-replace-an-old-file-server-with-a-new-file-server-using-the-same-ip-same-name-same-shares
All is working well as i am able to access the shares from computer with appropriate permission, however some of the shares had an alias for example \\servername\files\123 was called \\filestore\files\123. I am not able to accesss those shares,whenever i click on it i get a prompt that says you were not connected because duplicate name exist on the network.
I have renamed the old server, re IP'd it and even turned it off. Nothing in DNS records pointing to the old server. Any suggestions?
Ben Personick (Previously QCubed)
really? if it was a CNAME or A record tou wouldn't get the duplicate name issue, so it sounds like you might have had a dfs root that you need to take care of as well
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
really? if it was a CNAME or A record tou wouldn't get the duplicate name issue, so it sounds like you might have had a dfs root that you need to take care of as well
Sorry but how do i fix that? the way i migrated the file server, i disconnected the individual VMDKS files and connected to new server.
After that run the registry information that i copied from old server.
I will appreciate if you can tell me what else needs to be done
ASKER
setspn -Q host/filestore
setspn -Q host/filestore.domain.com
When i ran these from new server, i got existing SPN fpund!
FYI, it doesn't matter where it's run really, as it's querying domain information.
The commands should have told you which account they were attached to. If it's not the new file server, then you need to remove the SPNs from the other account, and then add them to the new account for the new server. setspn /? will show you the syntax.
The commands should have told you which account they were attached to. If it's not the new file server, then you need to remove the SPNs from the other account, and then add them to the new account for the new server. setspn /? will show you the syntax.
Use NETDOM and add old computer name as an additional name
NETDOM COMPUTERNAME servername /ADD oldname.domain.comASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
registry needed to be edited.