Hi Everyone!
I hadn't found any same situation i have, so i try to post my one.
Today we had changed a Cisco firewall for our customer. They have to connect their largest two sites with fiber cable directly, this is why new ASA was deployed. They had a VPN connection between the primary and secondary site. They have a primary and a secondary DC, the primary in the primary site, and the second in the other. If the WAN was failing the secondary DC was served all the queries for this site.
Now VPN connection is down, the fiber network is operating correctly between the two sites. PC's in the second one can ping and connect file servers in primary sites, DNS, DHCP and all services works well. But there're two virtual servers in the second site which has problems. The largest problem is an MSSQL server which serves their LOB program's databases. This is a W2003 guest computer under a W2008R2 Hyper-V machine. We can reach this VM from any workstations by RDP and ping works nicely too. But when i connect to it on RDP and try a ping from there, the VM can't ping anyone, and traceroute fails, it just doing timeovers and can't reach the default gateway too. I checked IP settings and everything is fine as it was before the firewall (gateway) change. I tried to flush the DNS, ARP and NETBIOS cache too, nothing was changed. After that tried a full restart but no change. Tried to restart the two VM's and the Hyper-V server too, no change.
The other VM on this Hyper-V is the secondary DC. From that i can ping and traceroute everywhere, so i think no problem with physical layer and cabling, no VLANs and other tricky things. We could login without trouble on clients so DCs are working, and when i tried the DNS it has resolved the SQL server's name correctly and i was able to ping it. But the LOB program trying to reach it by it's name can't connect to the DB. After some configuration in the program's ini file it can connect only with IP address and SQL authentication. So SQL connection with Windows authentication not working on every clients where we have tried.
Does anyone have a suggestion what to do next? I have no idea. I can't understand the source of this effect. Every host on the network works fine after the firewall change and client restart (arp flush), but this VM is unable to operate correctly.
Thx.