From owner-ssh@clinet.fi  Tue Mar 25 00:23:52 1997
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by hutcs.cs.hut.fi (8.8.5/8.7.3) with ESMTP id AAA26803; Tue, 25 Mar 1997 00:23:51 +0200 (EET)
Received: (daemon@localhost) by hauki.clinet.fi (8.8.5/8.6.4) id AAA09903 for ssh-outgoing; Tue, 25 Mar 1997 00:06:51 +0200 (EET)
Received: from nukkekoti.cs.hut.fi (nukkekoti.cs.hut.fi [130.233.40.128]) by hauki.clinet.fi (8.8.5/8.6.4) with ESMTP id AAA09894 for <ssh@clinet.fi>; Tue, 25 Mar 1997 00:06:44 +0200 (EET)
Received: from hiekkalaatikko.cs.hut.fi (hiekkalaatikko.cs.hut.fi [130.233.40.178])
	by nukkekoti.cs.hut.fi (8.8.5/8.8.5/1.15) with ESMTP id AAA04964
	for <ssh-mailgate@niksula.hut.fi>; Tue, 25 Mar 1997 00:06:42 +0200 (EET)
Received: (from news@localhost)
	by hiekkalaatikko.cs.hut.fi (8.8.5/8.8.5/1.8) id XAA19883
	for ssh-mailgate@niksula.hut.fi; Mon, 24 Mar 1997 23:45:55 +0200 (EET)
Received: from GATEWAY by news.cs.hut.fi with netnews
	for ssh-mailgate@niksula.hut.fi (ssh@clinet.fi)
To: ssh@clinet.fi
Date: Mon, 24 Mar 1997 15:41:21 -0600
From: tpb@leland.stanford.edu
Message-ID: <859238326.29596@dejanews.com>
Organization: Deja News Usenet Posting Service
Reply-To: tpb@leland.stanford.edu
Subject: SSH software
Sender: owner-ssh@clinet.fi
Precedence: bulk

Help!

Our Technical support contact at Data Fellows suggested we write a note to
this e-mail address. We are having trouble configuring (or using) the SSH
software to work with our Sybase database.

We are running Sybase on a Sun Unix machine. This machine is running
version 5.5.1 of Sun OS.
The database is Sybase 10/11. We are attempting to connect from a Windows
95 system.

We have the F-Secure SSH 1.0 software on the Windows system configured as
follows:
Forwarding Window:
Source Port 1025 (port on the Windows desktop system)
Destination Host 36.54.0.57 (the Unix system where Sybase is running)
Destination Port 1025 (the port on the Unix system where Sybase is
listening for connections)

Our SQL.INI file has an entry for "datasec". Within this file the entry
for datasec looks like this:
[datasec]
win3_query=WNLWNSCK,127.0.0.1,1025 (127.0.0.1 is the port on the Windows
client system)

We run SQLEDT version 10.0.4 and can "ping" something. SQLEDT responds:
Open connection to server 'datasec' (127.0.0.1) succeeds. I believe that
we are only pinging the Windows client desktop system and not the database
on the unix server.

We run WISQL version 10.0.4 and can only connect to the database after
several minutes. We get several messages when attempting to issue the
command SP_HELP:

Open Client Error: ct_connect(): user api layer: internal Client Library
error: Read from the server has timed out.
Changed database content to 'master'
Changed database content to 'odtxnprd'
Open Client Error ct_cmd_drop(): user api layer: external error: This
routine can be called only if the command structure is idle.

WISQL will then allow the SQL command to be executed. This is only after
several minutes but we do eventually get the desired output.

What do I need to change, or do, to be able to connect?
Are there any other tools that we can use to encrypt Sybase - Open client
data?


Please, if there is any information you can provide, send me a note:

Thanks!

Thomas Baker

tpb@stanford.edu

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet
