Jimmy
As Joe pointed out, that error means that the driver went to use the TCP/IP connection only to find out the TCP/IP connection was not there.
I would try applying http://support.microsoft.com/default.aspx?scid=kb;EN-US;948496. If that doesn't work, I would start looking at network traces to identify
the misbehaving piece of hardware.
Evan
--------------------
>Thread-Topic: Problem about jdbc driver's connection reset error on Windows 2003
>thread-index: AckvY+8d2BBME+6LTJ++wTaf3Iy8lQ==
>X-WBNR-Posting-Host: 207.46.193.207
>From: =?Utf-8?B?S3VuIE5pdQ==?= <Kun...@discussions.microsoft.com>
>References: <850C56B5-0D54-4A1A...@microsoft.com>
>Subject: RE: Problem about jdbc driver's connection reset error on Windows 2003
>Date: Thu, 16 Oct 2008 00:51:01 -0700
>Lines: 22
>Message-ID: <C8F82990-BEB3-404B...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3119
>Newsgroups: microsoft.public.sqlserver.jdbcdriver
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:595
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights.