To use a CNAME to connect to a share you must disable strict name checking - do a search and find the MS KB article to find the registry hack.
-Brian -----Original Message----- From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 9:12 AM To: NT System Admin Issues Subject: RE: Problems using alias for server? Currently fighting the same issue, with no luck. Thankfully this is just a server we host installation packages on. OldServer and NewServer. I have static dns and wins entries for OldServer pointing to the IP address of NewServer. \\OldServer from start run on any desktop usually brings up 'You were not connected because a duplicate name exists on the network. If joining a domain, go to system in control pane to change.....' other times it won't connect. Very odd and what you describe and what I have done should work. I suggest testing it as much as you can before you pull the trigger. And tell me how it goes :) > -----Original Message----- > From: John Hornbuckle [mailto:[EMAIL PROTECTED] > Sent: Friday, November 14, 2008 10:07 AM > To: NT System Admin Issues > Subject: Problems using alias for server? > > We're using a combination of folder redirection and roaming profiles, > with users' data stored somewhere like \\oldserver\sharename. That > server has an external PowerVault RAID system attached to it, and > that's where "sharename" is located. > > "Oldserver" is at the end of its lifecycle and needs to be > decommissioned. This means I need to move the PV to the new server, > which means that \\oldserver\sharename won't work anymore--it'll need > to be something like \\newserver\sharename. > > So here's what I was thinking of doing... I'd like to create a DNS > record for a new, generic server name--maybe "profiles"--and point it > to the IP address of oldserver. Then I'd reconfigure users' accounts / > AD settings to point to \\profiles\sharename. After giving that some > time to make sure it works and everyone's account is looking for that > new, generic server name and their profiles and redirected folders are > working fine on the old server, I would move the PV over to the new > server and change the DNS entry for "profiles" to point to the IP > address of the new server. The idea is that the move would be > transparent to the users and their computers. And a few years from now > when I need to once again relocate their stuff, I would again just > change the DNS entry to keep the change transparent. > > Is there any reason this shouldn't work? Or that it's just not a good > way of accomplishing what I want? > > > > John Hornbuckle > MIS Department > Taylor County School District > 318 North Clark Street > Perry, FL 32347 > > www.taylor.k12.fl.us > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
