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 xxx.xxx.39.24 xxx.xxx.34.24 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
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 xxx.xxx.39.24 xxx.xxx.34.24 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
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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?
ASKER
That's not my job, I just do the OS and hand it over.
Then you need to ask who manages the SQL Server to check that table. Renaming a server name has impact on SQL Server instances.
ASKER
Is there a command for the rename of the SQL instance?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"....new 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 "...new 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.