We are transitioning from PostgreSQL running on CentOS servers to Microsoft SQL Server 2008 R2 on Windows Server 2008 R2. Our web application, residing on a separate CentOS server, continues to operate without issues. All servers are provided by a third-party host and are on the same domain. Previously, our local development machines accessed the PostgreSQL database via a VPN without issue. However, we are now unable to connect or even ping the SQL Server 2008 R2 from our development machines, despite maintaining an active VPN. Our connection code works when executed on the CentOS server but fails remotely. Are there specific Windows firewall configurations to enable remote connectivity? Additionally, is there a reason we cannot even ping the SQL Server 2008 R2 from our remote clients?
Sounds like it could also be an issue at the network level, especially if you can’t ping it. Double check that ICMP is allowed through the firewall. Sometimes it’s disabled by default. Plus, ensure your SQL server is listening on the right interfaces and the ports are open.