I have configured several SQL boxes and SQL mirroring scenarios but this one has me going round in circles.
The result I get is that the principal cannot talk to the mirror and gives the error TCP://MYSERVER.DOMAIN.LOCAL:5022 cannot be contacted when trying to start mirroring from SQL management studio.
Both servers are Win Server 2008 R2 running MS SQL 2008 R2 on VM Ware ESXi 4.1, as separate entities the servers are running without issue - both the OS and SQL installations are patched to the same level, the servers are on the same domain but different subnets and different AD sites.
On both servers the SQL server instance is running as the same user with domain admin privs.
To configure mirroring I have:
1) backed up and restored the relevant database to the mirror with no recovery
2) Configured security on the prinicpal with NO witness
3) Left the ports for both servers on 5022 (this is what SQL management studio had as default)
4) use the same account that SQL is currently running as for the mirroring service accounts.
Windows Firewall is off on both machines, there are not other firewalls inbetween the two devices, DNS resolves both FQDN and hostname.
When I try to start mirroring the principal cannot contact the mirror.. I'm sure I have missed something...