| Author |
JDBC for SQL 2000 Service Pack 4?
|
|
|
| Am I knuts, or does SQL2k SP4 break the latest set of JDBC drivers? Can
anyone confirm?
oleitch-AT-locustcreek-DOT-com
| |
| Alin Sinpalean 2005-06-02, 7:23 am |
| And by "break" you mean?
Alin.
| |
| end-user 2005-06-02, 8:23 pm |
| "Fail to work with"
JDBC will not connect (gives the 'End of stream was detected on a read'
error). Was working fine before SP4 (previously SP3).
| |
| Gert E.R. Drapers 2005-06-03, 3:23 am |
| Works fine for me. What is the exact error? Can you connect using OSQL.EXE?
GertD@SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"end-user" <end-user@discussions.microsoft.com> wrote in message
news:A01EF57B-01C3-4B84-A9CB- 1D3E22E6BE42@microso
ft.com...
> "Fail to work with"
>
> JDBC will not connect (gives the 'End of stream was detected on a read'
> error). Was working fine before SP4 (previously SP3).
| |
| end-user 2005-06-03, 11:23 am |
| The exact error is " java.sql.SQLException: [Microsoft][SQLServer 2000 Driver
for JDBC]End of stream was detected on a read."
On the SQL server, I get a "Connection opened but invalid login packet(s)
sent. Connection closed".
I can't run osql.exe as I'm connecting from a linux box.
| |
| end-user 2005-06-03, 11:23 am |
| Can someone confirm that the JDBC drivers (for sp3) can successfully connect
to SQL Server w/ SP4 *when the "force protocol encryption" option is enabled*?
| |
|
| end-user wrote:
> Can someone confirm that the JDBC drivers (for sp3) can successfully connect
> to SQL Server w/ SP4 *when the "force protocol encryption" option is enabled*?
Anyone?
| |
| Alin Sinpalean 2005-06-10, 3:23 am |
| Anyone what?
| |
|
| Alin Sinpalean wrote:
> Anyone what?
>
Can someone confirm that the JDBC drivers (for sp3) can successfully
connect to SQL Server w/ SP4 *when the "force protocol encryption"
option is enabled*?
| |
| Alin Sinpalean 2005-06-11, 7:23 am |
| "Force protocol encryption" enabled? The MS driver never did support
SSL encryption. Use jTDS ( http://jtds.sourceforge.net ) or one of the
commercial drivers for that.
Disclaimer: I'm a jTDS developer.
Alin.
| |
| Kamil Sykora [MSFT] 2005-06-14, 11:23 am |
| The Microsof SQL Server 2000 Driver for JDBC does not support SSL
encryption.
There was an issue prior to Service Pack 4 for SQL Server 2000 where the
JDBC driver was able to connect to a SQL Server database even though the
"force protocol encryption" option was set on the server. The SQL Server
would incorrectly allow an unencrypted connection with the JDBC driver.
In Service Pack 4 for SQL Server 2000 this was fixed so that only clients
that support SSL can connect to the server if the "force protocol
encryption" option is set on the server. This will exclude the JDBC driver
since it does not support SSL and you will receive an error on the client.
Thanks,
Kamil
Kamil Sykora
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/secur_ity.
--------------------
| Date: Fri, 10 Jun 2005 10:34:59 -0400
| From: News < nooneherereally@hotm
ail.com>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Subject: Re: JDBC for SQL 2000 Service Pack 4?
|
| Alin Sinpalean wrote:
| > Anyone what?
| >
|
|
| Can someone confirm that the JDBC drivers (for sp3) can successfully
| connect to SQL Server w/ SP4 *when the "force protocol encryption"
| option is enabled*?
|
| |
|
| Well, that would explain it. Is there a way to "force encryption
execept for certain clients"?
Kamil Sykora [MSFT] wrote:
> The Microsof SQL Server 2000 Driver for JDBC does not support SSL
> encryption.
>
> There was an issue prior to Service Pack 4 for SQL Server 2000 where the
> JDBC driver was able to connect to a SQL Server database even though the
> "force protocol encryption" option was set on the server. The SQL Server
> would incorrectly allow an unencrypted connection with the JDBC driver.
>
> In Service Pack 4 for SQL Server 2000 this was fixed so that only clients
> that support SSL can connect to the server if the "force protocol
> encryption" option is set on the server. This will exclude the JDBC driver
> since it does not support SSL and you will receive an error on the client.
>
> Thanks,
> Kamil
| |
| Kamil Sykora [MSFT] 2005-06-21, 11:23 am |
| There is no way to selectively allow some clients to connect unencrypted.
If the setting is set on the server, all clients have to connect with SSL.
Kamil Sykora
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/secur_ity.
--------------------
| Date: Fri, 17 Jun 2005 11:44:50 -0400
| From: News < nooneherereally@hotm
ail.com>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Subject: Re: JDBC for SQL 2000 Service Pack 4?
|
| Well, that would explain it. Is there a way to "force encryption
| execept for certain clients"?
|
| Kamil Sykora [MSFT] wrote:
| > The Microsof SQL Server 2000 Driver for JDBC does not support SSL
| > encryption.
| >
| > There was an issue prior to Service Pack 4 for SQL Server 2000 where
the
| > JDBC driver was able to connect to a SQL Server database even though
the
| > "force protocol encryption" option was set on the server. The SQL
Server
| > would incorrectly allow an unencrypted connection with the JDBC driver.
| >
| > In Service Pack 4 for SQL Server 2000 this was fixed so that only
clients
| > that support SSL can connect to the server if the "force protocol
| > encryption" option is set on the server. This will exclude the JDBC
driver
| > since it does not support SSL and you will receive an error on the
client.
| >
| > Thanks,
| > Kamil
|
| |
| Michael Chan 2005-08-24, 8:23 pm |
| Just noticed this thread and an omission from Kamil. If the client is using
the client network utility and turns on "Force Protocol Encryption" option,
the communication between the server and that client only will be encrypted
via SSL.
"Kamil Sykora [MSFT]" wrote:
> There is no way to selectively allow some clients to connect unencrypted.
> If the setting is set on the server, all clients have to connect with SSL.
>
> Kamil Sykora
> Microsoft Developer Support - Web Data
>
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/securĀ_ity.
>
>
>
> --------------------
> | Date: Fri, 17 Jun 2005 11:44:50 -0400
> | From: News < nooneherereally@hotm
ail.com>
> | Newsgroups: microsoft.public.sqlserver.jdbcdriver
> | Subject: Re: JDBC for SQL 2000 Service Pack 4?
> |
> | Well, that would explain it. Is there a way to "force encryption
> | execept for certain clients"?
> |
> | Kamil Sykora [MSFT] wrote:
> | > The Microsof SQL Server 2000 Driver for JDBC does not support SSL
> | > encryption.
> | >
> | > There was an issue prior to Service Pack 4 for SQL Server 2000 where
> the
> | > JDBC driver was able to connect to a SQL Server database even though
> the
> | > "force protocol encryption" option was set on the server. The SQL
> Server
> | > would incorrectly allow an unencrypted connection with the JDBC driver.
> | >
> | > In Service Pack 4 for SQL Server 2000 this was fixed so that only
> clients
> | > that support SSL can connect to the server if the "force protocol
> | > encryption" option is set on the server. This will exclude the JDBC
> driver
> | > since it does not support SSL and you will receive an error on the
> client.
> | >
> | > Thanks,
> | > Kamil
> |
>
>
| |
|
|
|
|