My Windows7 firewall is blocking access to a SQL Server database on a remote server via SQL Server Management Studio. I'm VPN'd to the network the server is on, I can ping it, and I can transfer files to/from it.
"Cannot connect" 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...."
I can connect to another remote SQLS DB, on a public server (i.e., no VPN in my way), and to the DB on my localhost server.
I can connect like the good old days (early June and before) if I
- turn off the win7 firewall in the "Private" profile; or more specifically,
- Allow (all) inbound connections on the Private profile firewall
(And once I've connected, turning the firewall back on w/defaults doesn't prevent me from talking to the DB in SSMS via the connection made.)
Inbound and Outbound Rules are set default, to block the former, and allow the latter unless excluded. I see nothing in either list for ports 1433 and 1434, or with a name related to SSMS. Tried adding inbound rules to specifically allow all of TCP 1433-4 and UDP 1433-4 (on my side, "any" on the remote), and no joy.
Logging dropped packets, I see that incoming traffic to UDP port 1434 is being dropped:
2011-08-29 11:12:37 DROP UDP 10.1.1.240 10.1.1.242 1434 59228 152 - - - - - - - RECEIVE
EVEN AFTER I SET AN INBOUND RULE TO ALLOW TRAFFIC ON THAT PORT!
This problem is very strange, very specific. Hope someone can see what I'm missing here.