- isql -v my400db
ISQLERROR: Could not SQLConnect
We have a Linux computer (i.e. 188.8.131.52), a firewall computer (i.e. 184.108.40.206), and an AS/400 computer (i.e. 220.127.116.11) that is behind the firewall computer. We are attempting to make the connection through an SSH tunnel, from the Linux client computer, through the firewall computer, and finally to the AS/400 computer, as pictured below.
Linux <--> Firewall <-->
(18.104.22.168) (22.214.171.124) (126.96.36.199)
We are using the following command on the Linux computer to create the SSH tunnel. SSH on the firewall is set to port 1815. We assume that traffic for the iSeries Access for Linux goes over port 8471 (is this correct?), so we have included that. 188.8.131.52 is the AS/400 computer. We assume that the traffic should be directed to port 446 on the AS/400 (is this correct?). 184.108.40.206 is the firewall computer.
/usr/bin/ssh -p 1815 -N -L8471:220.127.116.11:446 email@example.com
The odbc.ini content appears below.
Description = iSeries Access ODBC Driver DSN for iSeries
Driver = iSeries Access ODBC Driver
System = localhost
UserID = example
Password = example
Naming = 0
DefaultLibraries = QGPL
ConnectionType = 0
CommitMode = 2
ExtendedDynamic = 0
DefaultPkgLibrary = QGPL
DefaultPackage = A/DEFAULT(IBM),2,0,1,0,512
AllowDataCompression = 1
LibraryView = 0
AllowUnsupportedChar = 0
ForceTranslation = 0
Trace = 0
We currently have an older Linux computer that successfully connects to the same AS/400 using an SSH tunnel, but it is using old DB2 Version 8 Client Connect software. That old Linux computer is successfully using the following command to create the SSH tunnel.
/usr/bin/ssh -p 1815 -N -L5001:18.104.22.168:446 firstname.lastname@example.org
Thanks for any help.
Message was edited by: chrisa2