SQL Server Performance Forum – Threads Archive
SQL SERVER 2005 SSL ISSUE – PLZ HELPHi Masters ,<br /><br />Please have a look on the following issue :<br /><br />We have a MS – SQL Server 2005 Server which is accessed through<br />many client machines . We use JSQLConnect to communicate with<br />the server from client machine. Problem is when we enable SECURITY<br />on the server machine , the communication fails with the following error :<br /><br />Log:Cannot connect to database, reason:com.jnetdirect.jsql.JSQLException:<br />Failed Logon:com.jnetdirect.jsql.JSQLException: DBComms.error reading input. Context:Read packet header, Unexpected end of stream, readBytes:-1, negative read result, PktNumber:0, ReadThisPacket:0, PktDataSize:4096 url:jdbc:JSQLConnect://localhost/database=master/user=sa/password=<<img src=’/community/emoticons/emotion-4.gif’ alt=’;P’ />assword><br /><br /><br />Any Idea why it is failing ? Do I need to install a certificate on my SQL Server , if<br />Yes KINDLY LET ME KNOW THE PROCEDURE. I tried installing certificate<br />Through MMC but an erro message appears saying â€œ No certification authority foundâ€<br />We don#%92t have a certification authority , so please let me know an alternate solution for<br />This.<br /><br />My Environment is as follows :<br /><br />JDK 1.5<br />Platform : HP-UX & Windows 2000<br />JSQLConnect 5.5<br /><br /><br />Second Part of my story comes here :<br /><br />I wrote a program in VB 2005 and tried to connect to SQL Sever 2005 using OLEDB driver. Surprisingly , I was able to connect to SQL Server but it gave a SSL Handshake<br />Error when â€œ Data Encryption on Client as Trueâ€. Any idea about this discrepancy<br />In this two cases?<br /><br />Thanks to you all in advance , Any response is most welcome<br /><br /><br />Thanks & Regards,<br /><br />Sudhansu Tiwari<br />
As you are using JDBC I would suggest to check whether you have upto date driver in place,http://msdn.microsoft.com/data/jdbc/ andhttp://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-4474-a44a-22b6ae2c4e17 fyi. For that handshake error refer whether Named pipes is enabled or not:
You might need explicitly to use "namedpipes:"prefix which ask for connect through named pipe and specify FQDN/LoopbackIP/IPAddress as server name in the connection string.
2) You might use FQDN/IPAddress/LoopbackIP to connect to the server. To resolve 1) and 2), you can specify <machinename> instead of FQDN/IPADress/LoopbackIP. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.