Nevermind. There are apparently several ways to do it, including DFS (http://support.microsoft.com/kb/829885) and simply adding an OptionalNames value to the lanmanserver (server) service combined with appropriate DNS records.
RS -----Original Message----- From: Richard Stovall [mailto:[email protected]] Sent: Tuesday, May 19, 2009 2:10 PM To: NT System Admin Issues Subject: Multiple network names on non-clustered server? I'm working on a project to 'un-cluster' some services from a Windows Server 2003 cluster running on aging hardware. I've figured out how to do everything I need to except I haven't determined if I can somehow recreate or mimic the multiple network name resources. For example, the active node's machine name is NodeA, but there are network name resources called MgmtFileServer, MktgFileServer, and SalesFileServer. (Hey, I didn't set it up...) People and business processes hit shares on the server using each of the network names. If I get rid of the cluster and take it down to just one machine, is there a way to seamlessly keep all of the existing client connections without modifying them to the actual machine name? I know I can get the clients to the machine with CNAME or A records, but can I make the machine listen on those names? Thanks, Richard Stovall ~ 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/> ~
