September 15, 2009 at 7:54 am
Hi 🙂
I'm having a weird problem with SSMS. I am using it to connect to a remote SQL Server instance. As soon as SSMS makes the connection, the network connection between the two machines is dropped/becomes unusable (I cannot even ping the server). I get authenticated, but the connection doesn't last long enough to populate Object Explorer. Other workstations can still talk to the server though.
This only happens when
1) using SSMS
2) to connect to that specific server
3) from my specific workstation -
I can connect using sqlcmd, no problems and no connection dropping.
I can connect to other servers from my workstation using SSMS.
Other workstations can connect to that server using SSMS.
About 10 minutes after dropping, the network connection is restored.
The server is Windows Server 2008 SP1 running SQL Server 2008 SP1; my workstation is Windows 7 RTM with SQL Server 2008 SP1.
I am at a loss where to even begin looking for the problem. I would appreciate your help, thank you.
September 15, 2009 at 8:28 am
My only guess would be that in establishing the connection through SSMS it is triggering a firewall/AV rule at either end that is then blocking further connections for 10 minutes.
I've had a similar problem before with an Symantec antivirus rule that was designed to prevent SQL Injection attacks in that I got booted off the connection the second I issued a particular command ("drop table" in my case).
September 15, 2009 at 9:37 am
Well that should have been an obvious place to look :-
Disabling my firewall solves the problem. Adding exceptions and rules for ports and SSMS does not, however, which makes me wonder what's special about connecting with SSMS. It is also puzzling that it only happens when connecting to that one server.
You've narrowed the search though, thank you.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply