January 3, 2013 at 1:33 pm
My coworker and I have inherited a network with 2 machines, both running Server 2008 Enterprise SP2 and SQL Server 2008 R2. They are in different domains physically separated on a secure connection between 2 ASA’s.
1 week ago I came in to work to see their status showed (Mirror, disconnected). I attempted to restore the mirror using online help, but to no avail. I broke the mirror in an effort to recreate it. They are in different domains physically separated on a secure connection between 2 ASA’s.
They don’t have certificates for the mirror and they don’t have a witness.
When trying to create the mirror, whether we connect via FQDN or IP, we get this error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) (Microsoft SQL Server, Error: 11001)
Troubleshooting efforts have included:
-we were able to ping successfully between servers using both IP addresses and FQDN’s
-we ensured 1433 and 5022 ports were listening on both servers
-we initiated successful telnet sessions from both mirror computers to the other and verified they are accepting connections
-verified correct firewall rules for both ASA’s
-turned off windows firewalls for both machines and disabled McAfee
-verified both devices have entries in their etc/hosts file
-confirmed both machines have SQLServer and SQL Server Browser services were running
-run ‘sqlcmd -L’ and didn’t return either mirror computer, but I believe this is because they are on different domains
-enabled both Named Pipes and TCP/IP in the Protocols for MSSQLSERVER, making sure TCP/IP is set to 1433
-checked to make sure SQL Server allows remote connections on both machines
-added incoming/outgoing domain firewall rules to allow traffic on 1433 and 5022 on both machines. These rules were not originally in place, but we tried it for troubleshooting.
Can anyone help with some ideas? We didn’t create this connection and aren’t SQL devs, so we are stuck.
January 4, 2013 at 7:48 am
Are the domains trusted?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 4, 2013 at 8:56 am
http://madebysql.blogspot.com/2011/06/database-mirroring-between-server-in.html
Why not recreate the mirror endpoints and use certificates?
January 19, 2013 at 4:24 pm
Sorry for not getting to you guys sooner. The problem has been resolved by using just the host name to map. We didn't use TCP or the port number to map.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply