> Hi All,
> I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> can connect to a MS SQL Server.  Could someone give me a hint as to how this
> is done?
> Thanks.
> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Hi All,

> I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> can connect to a MS SQL Server.  Could someone give me a hint as to how this
> is done?

> Thanks.

> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Example entry of sql.ini for MSSQL:

> [TESTSQLSERVER]
> query=NLWNSCK,mymssql.test.com,1433

> > Hi All,

> > I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> > can connect to a MS SQL Server.  Could someone give me a hint as to how this
> > is done?

> > Thanks.

> > --
> > Robert A. Nurse

> > ICQ Network Number 207692
> > http://www.cudbytech.net/

> Hi Ivan,
> I gave this a try.  But I still can't connect.  I checked the events on the MS SQL
> Server machine and I saw the following event:
> "Connection opened but invalid login packet(s) sent.  Connection closed."
> It sounds like the client is trying to communicate with a different protocol.

>> Example entry of sql.ini for MSSQL:

>> [TESTSQLSERVER]
>> query=NLWNSCK,mymssql.test.com,1433

>> > Hi All,

>> > I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
>> > can connect to a MS SQL Server.  Could someone give me a hint as to how this
>> > is done?

>> > Thanks.

>> > --
>> > Robert A. Nurse

>> > ICQ Network Number 207692
>> > http://www.cudbytech.net/
> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Have you applied service pack on your MSSQL7?

> > Hi Ivan,

> > I gave this a try.  But I still can't connect.  I checked the events on the MS SQL
> > Server machine and I saw the following event:

> > "Connection opened but invalid login packet(s) sent.  Connection closed."

> > It sounds like the client is trying to communicate with a different protocol.

> >> Example entry of sql.ini for MSSQL:

> >> [TESTSQLSERVER]
> >> query=NLWNSCK,mymssql.test.com,1433

> >> > Hi All,

> >> > I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> >> > can connect to a MS SQL Server.  Could someone give me a hint as to how this
> >> > is done?

> Hi Ivan,

> I gave this a try.  But I still can't connect.  I checked the events on the MS SQL
> Server machine and I saw the following event:

> "Connection opened but invalid login packet(s) sent.  Connection closed."

> It sounds like the client is trying to communicate with a different protocol.

> > Example entry of sql.ini for MSSQL:

> > [TESTSQLSERVER]
> > query=NLWNSCK,mymssql.test.com,1433

> > > Hi All,

> > > I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> > > can connect to a MS SQL Server.  Could someone give me a hint as to how this
> > > is done?

> > > Thanks.

> > > --
> > > Robert A. Nurse

> > > ICQ Network Number 207692
> > > http://www.cudbytech.net/

> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Robert,

> You can get it from the FTP site.

> File Location

> ftp://ftp.microsoft.com/bussys/sql/transfer/sql70/sqlservr/s70723i.exe -
> Intel
> ftp://ftp.microsoft.com/bussys/sql/transfer/sql70/sqlservr/s70723a.exe -
> Alpha

> Bugs Fixed

> 55964   7.0 ODS does not send back login response to TDS 5.0 clients exactly
> as 6.5 ODS

> You may need the password to extract the files from this file

> s70723i.exe -s<passwd>

> You can call MS Support for the password.

> Ivan Santhumayor
> Firmwide database Support
> Goldman Sachs & Co.

> > -----Original Message-----

> > Sent: Friday, February 11, 2000 12:38 PM
> > To:   Santhumayor, Ivan
> > Subject:      Re: Configuring SQL.INI For Connection To MS SQL Server

> > Hi Ivan,

> > You wouldn't still happen to have that hotfix would you?  I'm searching
> > M$'s site now and they seem to have everything but this.

> > Robert,
> > Its because in addition to the Service Pack 1 for MSSQL7, you need the
> > hotfix s70723I
> > to be applied. It needs to copy a bunch of OPENDS60 DLLS to make the TDS
> > layer
> > compatible with open client.
> > I had got the very similar message, and it went away with the hotfix
> > apply.

> >  <http://www.cudbytech.net/>

> > --
> > Robert A. Nurse
> > Web Development
> > RCN Corporation

> > ICQ Network Number 15566746
> > <http://members.tripod.com/~rnurse>

> Robert,
> Its because in addition to the Service Pack 1 for MSSQL7, you need the hotfix s70723I
> to be applied. It needs to copy a bunch of OPENDS60 DLLS to make the TDS layer
> compatible with open client.
> I had got the very similar message, and it went away with the hotfix apply.

> > Hi Ivan,

> > I gave this a try.  But I still can't connect.  I checked the events on the MS SQL
> > Server machine and I saw the following event:

> > "Connection opened but invalid login packet(s) sent.  Connection closed."

> > It sounds like the client is trying to communicate with a different protocol.

> > > Example entry of sql.ini for MSSQL:

> > > [TESTSQLSERVER]
> > > query=NLWNSCK,mymssql.test.com,1433

> > > > Hi All,

> > > > I'm trying to configure my Sybase SQL.INI file so that my DB-LIB applications
> > > > can connect to a MS SQL Server.  Could someone give me a hint as to how this
> > > > is done?

> > > > Thanks.

> > > > --
> > > > Robert A. Nurse

> > > > ICQ Network Number 207692
> > > > http://www.cudbytech.net/

> > --
> > Robert A. Nurse

> > ICQ Network Number 207692
> > http://www.cudbytech.net/

> Ivan,

> You've been a big help with this problem.  But my connection issues still remain.  I
> installed the S70723I patch and when I try to connect to SQL Server from Sybase Central, I
> get the error:

> ct_cursor(): user api layer: external error: The connection's capabilities do not support
> this type of request.

> At first I was getting incorrect login errors.  Then I figured out that the login info that
> Sybase Central is sending is not an NT user but an SQL Server login.  So I created a
> matching SQL Server user and that's when I get this error.  I tried connecting with both
> named pipes and TCP/IP.  Here are my SQL.INI settings just in case:

> [MS_SQLNAMEDPIPES]
> query=NLMSNMP,\\SERVERNAME\pipe\sql\query
> win3_query=NLMSNMP,\\SERVERNAME\pipe\sql\query

> [MS_SQLTCPIP]
> query=NLWNSCK,SERVER_IP_ADDRESS,1433
> win3_query=NLWNSCK,SERVER_IP_ADDRESS,1433

> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Ivan,
> You've been a big help with this problem.  But my connection issues still remain.  I
> installed the S70723I patch and when I try to connect to SQL Server from Sybase Central, I
> get the error:
> ct_cursor(): user api layer: external error: The connection's capabilities do not support
> this type of request.
> At first I was getting incorrect login errors.  Then I figured out that the login info that
> Sybase Central is sending is not an NT user but an SQL Server login.  So I created a
> matching SQL Server user and that's when I get this error.  I tried connecting with both
> named pipes and TCP/IP.  Here are my SQL.INI settings just in case:
> [MS_SQLNAMEDPIPES]
> query=NLMSNMP,\\SERVERNAME\pipe\sql\query
> win3_query=NLMSNMP,\\SERVERNAME\pipe\sql\query
> [MS_SQLTCPIP]
> query=NLWNSCK,SERVER_IP_ADDRESS,1433
> win3_query=NLWNSCK,SERVER_IP_ADDRESS,1433
> --
> Robert A. Nurse

> ICQ Network Number 207692
> http://www.cudbytech.net/

> Does anyone have the password for the patch

> allows Sybase clients to connect to MS SQL

> wading through the M$ support cesspool.