Our team has SQL Server databases on two separate hosts (test and prod) provided by corporate IT.
Working on and running a tool that does a lot of database-oriented work from my Windows 7 machine, I am suddenly unable to connect to the test database or test database host after a period of interaction.
What I mean is that I will suddenly get errors in logs:
ERROR o.h.e.j.s.SqlExceptionHelper // The connection to the host TESTHOST, named instance TEST failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host.
I am unable to ping
TESTHOST ("General Failure" is the only error message displayed) nor telnet (to 1979) nor tracert (also "General Failure" - immediately).
While this is happening, I can ping, tracert, telnet as well as connect using SQL Server Management Studio to the
PRODHOST/PROD database instance without a problem. Other people on my team can connect to
TESTHOST\TEST just fine during this 'blackout period' for me. After a period of time (without even restarting my PC) I can resume connecting to test both via telnet and via SQL Server Management Studio or the tool itself.
Windows Firewall is disabled by IT. There is a McAfee Agent installed as well as McAfee Virus Security. I can't do anything about those. Any more "it don't work!" to IT and I'm just going to have my machine re-imaged and that wont even necessarily fix it (objections to not bothering to understand root cause notwithstanding), but it will obstruct me from working on any number of other things that aren't being impacted by this one particular tool not being able to be further developed.
I'm perplexed: I am not a very super user, but can anyone help me even start investigating what is happening? The evidence suggests, to me, that this is an issue with my system exclusively (so, maybe a re-image would be fine). I've tried random things like installing the newest drivers for my Intel 82578DM Gigabit Network Adapter, disabling IPv6, as well as
netsh int ip reset (which did not allow me to start connecting again, only time or a reset does).