Cheating by DNS pointing old server name to new server name - File shares

[googlemad]

We had a couple of really old SQL servers, SQL1 and SQL2 so have built a brand new SQLSERVER 2016 server and then migrate the databases and file shares across.

 

Having done SQL1, we then pointed SQL1 in DNS to the SQLSERVER IP address and all seemed fine SQL wise, but I've just noticed when starting to try and do the same with SQL2 when you try and access the file shares a error message pops up

 

"The specified network name is no longer available"

 

Is there any way to resolve this? The reason we have to cheat is because we have 100 or so SQL applications hard coded to the old server names and the developer left years ago!

[AlanD]

Is it possible that the coding actually has a fixed IP address? I know the error says "specified network name" - but I think it would say that if the name was an ip address.

 

..and id you have already used that IP address - for SQL1 you can always put 2 x IP addresses on the same network card.

Edited June 23, 2017 by AlanD

[googlemad]

I was being thick...had a DNS A record for the old server pointing to the new server IP so got rid of that and created a CNAME record instead, then noticed in Active Directory the old server still had a computer object present so removed that and everything works fine, the old server UNC path now brings up the contents of the new server