Try this in the registry and reboot, works for us, we use aliases for failover:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters] "DisableStrictNameChecking"=dword:00000001 Regards Tony Patton Desktop Operations Cavan Ext 8078 Direct Dial 049 435 2878 email: [EMAIL PROTECTED] "Kennedy, Jim" <[EMAIL PROTECTED]> 14/11/2008 15:14 Please respond to "NT System Admin Issues" <[email protected]> To "NT System Admin Issues" <[email protected]> cc 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/> ~ ==================================================================== http://www.quinn-insurance.com This e-mail is intended only for the addressee named above. The contents should not be copied nor disclosed to any other person. Any views or opinions expressed are solely those of the sender and do not necessarily represent those of Quinn-insurance, unless otherwise specifically stated . As internet communications are not secure, Quinn-insurance is not responsible for the contents of this message nor responsible for any change made to this message after it was sent by the original sender. Although virus scanning is used on all inbound and outbound e-mail, we advise you to carry out your own virus check before opening any attachment. We cannot accept liability for any damage sustained as a result of any software viruses. ==================================================================== QUINN-Life Direct Limited and QUINN-Insurance Limited are regulated by the Financial Regulator. QUINN-Insurance Limited is authorised by the Financial Regulator and regulated by the Financial Services Authority for the conduct of UK business. ==================================================================== QUINN-life direct Limited is registered in Ireland, registration number 292374. QUINN-insurance Limited is registered in Ireland, registration number 204768. QUINN-life direct Limited is a private company limited by shares Both companies have their head office at Dublin Road, Cavan, Co. Cavan. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
