Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ADS over SSH: error 6097

4 posts in Networking Last posting was on 2006-06-22 07:57:54.0Z
Brian Loney Posted on 2006-06-21 04:55:02.0Z
Date: Wed, 21 Jun 2006 00:55:02 -0400
From: Brian Loney <brianl@caveo.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: advantage.networking
Subject: ADS over SSH: error 6097
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 72.137.236.179
Message-ID: <4498d20d@solutions.advantagedatabase.com>
X-Trace: 20 Jun 2006 22:58:53 -0700, 72.137.236.179
Lines: 24
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!72.137.236.179
Xref: solutions.advantagedatabase.com Advantage.Networking:615
Article PK: 1132034

Hi all, hope you can shed some light.

Trying to get ADS Client 7.10.0.15 to make a connection to the server
over an SSH tunnel.

Using UNC connection string (\\servername\sharename) with an ADS.INI to
avoid discovery problems. ADS.INI file specifies:
[servername]
LAN_IP=127.0.0.1
LAN_PORT=6262

But the client returns an Error 6097: Bad IP address

I have found misc articles that the client does not like using
127.0.0.1, however one referred to the ability to use "localhost"
instead. Tries that but the client skipped the ADS.INI file altogether.

Is there anyway (or fix) that would allow the client to connect to a
loopback address (does not have to be 127.0.0.1)

Thanks,

Brian


Mark Wilkins Posted on 2006-06-21 15:04:27.0Z
From: "Mark Wilkins" <tired@of.spam>
Newsgroups: advantage.networking
References: <4498d20d@solutions.advantagedatabase.com>
Subject: Re: ADS over SSH: error 6097
Date: Wed, 21 Jun 2006 09:04:27 -0600
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.161
Message-ID: <44995f22@solutions.advantagedatabase.com>
X-Trace: 21 Jun 2006 09:00:50 -0700, 10.24.38.161
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.161
Xref: solutions.advantagedatabase.com Advantage.Networking:616
Article PK: 1132035

Hi Brian,

I think that if you are trying to use the loopback adapter, you will have to
specifically tell Advantage Database Server to bind to that address. Look
up "LAN IP Address" in the help file. Basically, you need to create a
registry entry of the form LAN_IP_ADDRESS=127.0.0.1 on the server. Without
that (and assuming there is another network adapter enabled), ADS will bind
to the other address and will not respond to the client correctly.

However, I think this will prevent clients that are not on the same machine
from connecting to ADS. Or I may simply be revealing my total lack of
knowledge about SSH tunneling. It's not clear to me why you are trying to
use the loopback address. Is that somehow necessary with an SSH tunnel? Or
are you just setting up a test environment on a single PC to try things out?

Mark Wilkins
Advantage R&D

"Brian Loney" <brianl@caveo.ca> wrote in message
news:4498d20d@solutions.advantagedatabase.com...
> Hi all, hope you can shed some light.
>
> Trying to get ADS Client 7.10.0.15 to make a connection to the server over
> an SSH tunnel.
>
> Using UNC connection string (\\servername\sharename) with an ADS.INI to
> avoid discovery problems. ADS.INI file specifies:
> [servername]
> LAN_IP=127.0.0.1
> LAN_PORT=6262
>
> But the client returns an Error 6097: Bad IP address
>
> I have found misc articles that the client does not like using 127.0.0.1,
> however one referred to the ability to use "localhost" instead. Tries
> that but the client skipped the ADS.INI file altogether.
>
> Is there anyway (or fix) that would allow the client to connect to a
> loopback address (does not have to be 127.0.0.1)
>
> Thanks,
>
> Brian
>


Brian Loney Posted on 2006-06-22 00:44:19.0Z
Date: Wed, 21 Jun 2006 20:44:19 -0400
From: Brian Loney <brianl@caveo.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: advantage.networking
Subject: Re: ADS over SSH: error 6097
References: <4498d20d@solutions.advantagedatabase.com> <44995f22@solutions.advantagedatabase.com>
In-Reply-To: <44995f22@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 72.137.236.179
Message-ID: <4499e8cb@solutions.advantagedatabase.com>
X-Trace: 21 Jun 2006 18:48:11 -0700, 72.137.236.179
Lines: 79
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!72.137.236.179
Xref: solutions.advantagedatabase.com Advantage.Networking:617
Article PK: 1132036

Hi Mark,

Thanks for the quick reply.

It's not the Database Server that I want to bind to 127.0.0.1. It is
bound to a real IP. So there should not be any impact to "normal clients".

It's the client where I want to do this. The way an ssh tunnel works is
that a local listener/server is established on a certain port (ie 6262)
on the client. Upon accepting a connection locally it in turn makes a
connection "through the tunnel" to a predetermined host on the other end
on a specified port (in this case the Advantage Database Server port 6262).

So, in essence you configure your client to connect to 127.0.0.1, which
is really a connection to the remote server, but secured through the tunnel.

For example:

Client Machine Internet ADS Server
-------------------------------- ----------------------------------
| client app --> localhost:6262 | --> | SSH client --> xx.xx.xx.xx:6262|
-------------------------------- ----------------------------------

I can't see any reason why this would not work, except for the fact that
the client sems to have some built-in code that rejects outright a
connection to 127.0.0.1, without even trying to connect.

Brian

Mark Wilkins wrote:
> Hi Brian,
>
> I think that if you are trying to use the loopback adapter, you will have to
> specifically tell Advantage Database Server to bind to that address. Look
> up "LAN IP Address" in the help file. Basically, you need to create a
> registry entry of the form LAN_IP_ADDRESS=127.0.0.1 on the server. Without
> that (and assuming there is another network adapter enabled), ADS will bind
> to the other address and will not respond to the client correctly.
>
> However, I think this will prevent clients that are not on the same machine
> from connecting to ADS. Or I may simply be revealing my total lack of
> knowledge about SSH tunneling. It's not clear to me why you are trying to
> use the loopback address. Is that somehow necessary with an SSH tunnel? Or
> are you just setting up a test environment on a single PC to try things out?
>
> Mark Wilkins
> Advantage R&D
>
> "Brian Loney" <brianl@caveo.ca> wrote in message
> news:4498d20d@solutions.advantagedatabase.com...
>
>>Hi all, hope you can shed some light.
>>
>>Trying to get ADS Client 7.10.0.15 to make a connection to the server over
>>an SSH tunnel.
>>
>>Using UNC connection string (\\servername\sharename) with an ADS.INI to
>>avoid discovery problems. ADS.INI file specifies:
>>[servername]
>>LAN_IP=127.0.0.1
>>LAN_PORT=6262
>>
>>But the client returns an Error 6097: Bad IP address
>>
>>I have found misc articles that the client does not like using 127.0.0.1,
>>however one referred to the ability to use "localhost" instead. Tries
>>that but the client skipped the ADS.INI file altogether.
>>
>>Is there anyway (or fix) that would allow the client to connect to a
>>loopback address (does not have to be 127.0.0.1)
>>
>>Thanks,
>>
>>Brian
>>
>
>
>


Joachim Duerr (ADS Support) Posted on 2006-06-22 07:57:54.0Z
From: "Joachim Duerr (ADS Support)" <jojo.duerr@gmx.de>
Subject: Re: ADS over SSH: error 6097
Newsgroups: Advantage.Networking
References: <4498d20d@solutions.advantagedatabase.com> <44995f22@solutions.advantagedatabase.com> <4499e8cb@solutions.advantagedatabase.com>
Organization: iAnywhere
User-Agent: XanaNews/1.18.1.2
X-Face: ,QMv7[luB)BpWAQ~:"kw6n%0ieY63.:g2K3n~8ky0;||5Xle*Xq+=~<Fy:0CVC2nx@8~vZ
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 195.2.185.25
Message-ID: <449a3f72@solutions.advantagedatabase.com>
Date: 22 Jun 2006 00:57:54 -0700
X-Trace: 22 Jun 2006 00:57:54 -0700, 195.2.185.25
Lines: 22
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!195.2.185.25
Xref: solutions.advantagedatabase.com Advantage.Networking:618
Article PK: 1132037


Brian Loney wrote in <4499e8cb@solutions.advantagedatabase.com>:

> Client Machine Internet ADS Server
> --------------------------------
> ---------------------------------- | client app --> localhost:6262 |
> --> | SSH client --> xx.xx.xx.xx:6262|
> --------------------------------
> ----------------------------------
>
> I can't see any reason why this would not work, except for the fact
> that the client sems to have some built-in code that rejects outright
> a connection to 127.0.0.1, without even trying to connect.

the client gets back a packet which also includes the server's IP
address. Since the clients sends the packet to 127.0.0.1 and gets back
a reply with the server's IP address it doesn't accept the packet.

--
Joachim Duerr
Senior Product Support Analyst (Advantage Database Server)
iAnywhere Solutions / Extended Systems
advantage[AT]extendsys.de