Ok here is one for the MS SQL gurus.
Two servers. Identical hardware, Operating systems and software. One server in Dallas, another in Houston. VPN is open to allow the whole subnet (192.168.200.xx in Houston, 192.168.99.xx in Dallas) to talk to each other. So I can ping from any of the 4 VMs in both physical servers to the other with zero loss of packets.
The Operating systems are Server 2012 and the SQL is MS SQL 2012 Enterprise
The Router in Houston is a Cisco 5000 series and the Router in Dallas is a Cisco Small Business RV042
Now, here is what is happening.
I can open SQL Server Management Studio in Houston and connect to the local database with zero issues (of course) and when I go to connect to the Dallas SQL server I can connect with only about a 3-5 second delay and the folders expand quickly.
Now, if I open the SQL Server Management Studio in Dallas I can connect to the local database with zero issues but when I try and connect to the Houston SQL server it takes at least 15-20 seconds and it take another 30 seconds minimum to expand all the folders (in fact it even causes the Management Console to go to Not Responding).
At first I thought it was because the DC was in Houston, so I created another DC in Dallas and got it all synced up (I tested the Dallas SQL server to make sure it was logging on to the Dallas DC by running Set LogonServer and it showed the Dallas DC as its logon server)
So now I am stumped as to what or where the problem is. I can ping both names and IP's from both locations and get zero loss. 10ms roundtrip on the pings is average
I have turned on SQL Browser and SQL Agent on both servers, and I enabled all the communication pathways. Named Pipes, IP etc.
PS Oh, btw, the whole idea of trying to get each to communicate to each other is to setup Peer to Peer replication. A subscriber and a publisher on both servers