Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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: " 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).

share|improve this question
I will not jump to conclusion/suggestion about driver or hardware issue for now, as you can access other machines when this happen. (1) Does this always happen when you doing the same task? (2) Is/Are the task very heavy in terms of network traffic? (3) Do you have access to TESTHOST event log? That may provide hint. – John Siu Jan 22 '13 at 20:06
Yes, it happens when I do the same task (though that is rather high level, it's running a tool that reads data from a database, performs some external calculations, then attempts to write new rows to another table). It has always happened during a select (but the selects also outweigh the inserts) I wouldn't say that it is a large amount of traffic - just a consistent number of say, 3-5 queries per second. I've requested the event log. – Doug Jan 22 '13 at 21:22
I kind of feel the server(TESTHOST) is shuting your machine out for some reason. But we will wait for the event log. – John Siu Jan 22 '13 at 21:48
So this tool runs inside TomEE - I just copied the TomEE installation as well as the WAR to another machine and it is running fine. – Doug Jan 22 '13 at 22:34
What about the jre? Are they the same version? – John Siu Jan 22 '13 at 23:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.