Staging server (copy of live) trying to connect to server it was copied from!

We're having an issue as above where we're built a staging set-up be copying the live one.
For some reason the new server keeps trying to access the old one. We have no idea why this is happening.

2015-09-14 17:24:04 Deny ms-sql-s/tcp 61977 1433 4-"othersubnet" Firebox Denied 52 127 (Unhandled Internal Packet-00)  proc_id="firewall" rc="101" msg_id="3000-0148" tcp_info="offset 8 S 3452440112 win 32"       Traffic
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
"...copying the live one" - how was the "copy" done?

" server keeps trying to access the old one" if it is the SSRS - Reporting Server that was "copyed" then most likely all report server configs were copied as well therefore " server keeps trying to access the old one" so you will need to check and change all the configurations to point to whatever "new" server means/is in your environment.
wannabecraigAuthor Commented:
Apologies fro lack of clarity.

Have live servers.  To make staging environment we cloned those on ESX and renamed, reassigned IP and subnet.  All works fine except we can see connections to the server from which I made the clone from.
lcohanDatabase AnalystCommented:
I see - standard virtual environment "replication"...well can you check on the original server used to generate the close and see where the connections are coming from?
Those hosts still connecting to the original environment may have "host" files (which is not ideal) hardcoded names/IP's and I beleiev by renaming the VM computername only does not changes SQL Server name or viceversa - I forget now but rememeber we had similar issue in the past with VMware images of SQL.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Vitor MontalvãoMSSQL Senior EngineerCommented:
 To make staging environment we cloned those on ESX and renamed, reassigned IP and subnet.
So you renamed the server and how about the SQL Server? Did you perform any rename for the SQL Server instance?
What SELECT * FROM sys.servers returns?
wannabecraigAuthor Commented:
That's not my job, I just do the OS and hand it over.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Then you need to ask who manages the SQL Server to check that table. Renaming a server name has impact on SQL Server instances.
wannabecraigAuthor Commented:
Is there a command for the rename of the SQL instance?
Vitor MontalvãoMSSQL Senior EngineerCommented:
No, you can't rename a named instance but if it's a default instance you can change the servername in master.sys.servers table.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.