RE: Cannot connect to my SQL 2005 server using JDBC - can any dia

That article was specific to the SQL Server 2000 JDBC driver. The SQL Server 2005 JDBC driver will talk to SQL Browser just fine (assuming the correct
ports are opened up).

Evan
--------------------
Thread-Topic: Cannot connect to my SQL 2005 server using JDBC - can any dia
thread-index: AciUfHL7n6GoC2poQGa6q15tSHrQFw==
X-WBNR-Posting-Host: 67.84.177.208
From: =?Utf-8?B?TGluY2hpIFNoZWE=?= <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <64tr2lF2coejmU1@xxxxxxxxxxxxxxxxxx> <wpsqotDlIHA.3756@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Cannot connect to my SQL 2005 server using JDBC - can any dia
Date: Tue, 1 Apr 2008 21:46:00 -0700
Lines: 77
Message-ID: <033DEBFD-87A2-4761-8547-2BFFAECCC547@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
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.2992
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:481
NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

Evan;

Do you have any references on which version of the Microsoft JDBC driver
works with SQLBrowser from Linux/Unix? I don't know if KB article
http://support.microsoft.com/kb/313225 is dated. But it says the following:

To connect to a named instance through the Microsoft SQL Server
2000 Driver for JDBC, you must specify the port number that is
associated with the named instance, instead of the name of the
named instance as shown earlier.

This seems to suggest that whatever version of the JDBC driver the article
is talking about doesn't talk to UDP 1434 to retrieve the port automatically.

Linchi

"Evan T. Basalik (MSFT)" wrote:

Hey Spin,

All JDBC drivers are limited to using TCP/IP, so if you can connect properly with a UDL specifying tcp:servername, then you should be OK.

However, I have seen some scenarios where not every JDBC drivers handles problems with the UDP broadcast from the SQL Browser service
appropriately. What driver are you using?

What happens if you hard code the port number in the connection string?

Evan


--------------------
From: "Spin" <Spin@xxxxxxxxxxx>
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Subject: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is?
Date: Tue, 25 Mar 2008 22:38:47 -0400
Lines: 15
Message-ID: <64tr2lF2coejmU1@xxxxxxxxxxxxxxxxxx>
Reply-To: "Spin" <Spin@xxxxxxxxxxx>
Mime-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Trace: individual.net /j9PrmZkEIFfhIEEN3Z2BAdFjD3GXFZeFrLt+/VLF2I8TYoW2t
Cancel-Lock: sha1:KuDO2DK97g+arT3aofLOly6EP2k=
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed-
0.progon.net!
progon.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:476
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

Gurus,

Running SQL Server 2005 SP2 and using named instances. I have an
application which uses JDBC to connect to my SQL server. Connectivity using
ODBC works just fine as I can test it successfully using a UDL file.
However, this application fails to connect to my server every time and I am
not sure what troubleshooting tool I can use to narrow the problem. To
clarify, I can connect remotely to my SQL server using a UDL file by any
combination of name or IP, named pipes or TCP/IP, SQL or Windows
Authentication. In sum, I cannot connect to my SQL 2005 server using JDBC -
can any diagnostic tool tell me what the problem is?

--
Spin



Evan T. Basalik
This posting is provided â??AS ISâ?? with no warranties, and confers no rights.





Evan T. Basalik
This posting is provided ?AS IS? with no warranties, and confers no rights.


.

Relevant Pages