dns >> repointing old sevrer to existing server

by TWFyY3VzIERlbXBzZXk » Wed, 08 Aug 2007 16:16:11 GMT


I'm looking into decomissioning one of our old file servers and redirecting
anything that accesses its dns name to our new file server (due to hard coded
links in excel), so for example all links accessing filer1 are pointed to
filer2 via DNS.

I have tried creating a CNAME DNS entry with the old sever name pointing to
the new server name, however I recieve an error message saying there are
duplicate enteries on the network when trying to access any shares on the new

Can anyone recommend, or suggest what I'm doing wrong here?


dns >> repointing old sevrer to existing server

by Anthony » Thu, 09 Aug 2007 00:36:08 GMT

Try this one: http://support.microsoft.com/default.aspx?scid=kb ;en-us;281308

dns >> repointing old sevrer to existing server

by TWFyY3VzIERlbXBzZXk » Thu, 09 Aug 2007 15:36:02 GMT

Thanks Antony that helps me with my testing. My actual re-pointing is going
to go to a netapp filer, so I don't suppose you know if using a CNAME DNS
entry has any issues?


Similar Threads

1. Upgrade from win2k server to 2003 sevrer

Hello there,

Hopefully someone out there will be able to give me some pointers on what we 
are trying to do.

We are a smallish school who have a network consisting of about 200 clients 
and about 600 users, all of which have their userdrives stored on the central 
server (total storgae used is about 120 Gig).  The  2000 server is very slow 
at the moment so we are about to purchase a new server with 2003 
preinstalled, but we are looking for the best way to get everything off one 
server and onto the other.  We have spoken to quite a few people, all of 
which have given conflicting views on how to go about this.  Some people have 
advised using tools such as adduser and xcacls for populating AD on the 2003 
server and assigning user permissions for homedrives etc (obviously after 
running adprep and forestprep), but some have mentioned other tools by Hyena 
that do the same thing (amongst other things)

What we really want to know is how to go about this in the most 
less-complicated way.  We are also aware that we have to transfer FSMO roles 
amongst other things, and we are assuming that we can jsut create a new scope 
once up and running for DHCP and that DNS and WINS will just work once 
installed.  Are we corect in thinking this?

Myself and my colleagues have tried looking through TEchnet and other 
resources online but all the help seems to be conflicting and there doesnt 
seem to be anywhere that tells you exactly how to do what we want to do in 
meaningful steps.  Surely thousands of people have had to do this since 2003 
server was released, but no-one's seemed to have documented the best 
practices involved!??!

I would really appreciate some help or pointers to any other online 
resources or texts.

many thanks

2. Re-Connecting old AD server to an existing 2000 Domain

3. New Server Old Name, keep old server?

4. Add an existing SQL 2000 server to an existing Win 2k3/SQL2k C

5. Add an existing SQL 2000 server to an existing Win 2k3/SQL2k Clust

Can I do this? I have a 2 node SQL cluster running Windows 2003, and another 
SQL 2000 server running Windows 2003 (all Enterprise). Can I add the stand 
alone box to my existing cluster, so the passive node can take over for 
either of the active nodes?

6. Win 2003 Sevrer netlogon problem

7. Exchange sevrer Failed Mail Folder

We are running SBS 2003 R2 with exchange server 2003
We are using the POP3 conenctor to retreive our mail from our ISP using a 
global mailbox.
Normal mail is coming and gioing OK
We do however have a number of read receipts in the 'Failed Mail Folder' 
that have 'Undisclosed recipients' in to To address.

Is this  a problem we can fix on our mail server or is this a problem with 
the recipients mail server.

I have read the relevant articles on exchange and bcc but wondered is there 
was some other issues that can cause or overcome this problem.

We do get some read receipts back in that are addressed properly so I though 
that it might be the recipiets mail server or client rather than ours.

Many thansk for reading this post hope you can help.

8. Windows 2003 terminal sevrer, clients cant log on and a useren