Re: Tunneling SQLPlus with ssh

I think using the USE_SHARED_SOCKET option in the listener.ora file could help.

From the Oracle Net8 config giude:

USE_SHARED_SOCKET You can set the USE_SHARED_SOCKET parameter to TRUE to enable the use of shared sockets. It this parameter is set to TRUE, the network listener passes the socket descriptor for a client connections to the database thread. The result is the client does not need to establish a new connection to the database thread,
and database connection time improves. Also, all database connections share the port number used by the network listener, and
this may be useful if you are setting up third-party proxy servers.
In article <slrn97p0to.500.chch_at_freesbee.wheel.dk>,   chch_at_freesbee.wheel.dk (Christian Dueholm Christensen) wrote:
> Hi All
>
> I have an Oracle 8.0.5.0.0 database running on NT4 (not my choice of
> platform but thats the small blows life gives you) and I have a number
> of off-site developers that needs to make a connection with a sqlplus
> client.
> Instead of punching great big holes in my firewall I would prefer
> to use ssh to tunnel the connection. I have tried forwarding port 1521
> which does make tnsping work, but the sqlplus connection fails with
> error code 12203.
> After looking at the output from netstat -a on a machine at the same
> network as the Oracle server it seems that the server opens a
 connection
> back to the client on a more or less random port.
> Is there a way for the client to request a specific port on the server
> when the connection is set up?
>
> Has anbody done anything like this before?
>
> --
> Christian D. Christensen
>
> "I think the sum of intelligence on the internet is constant. Only the
> number of lusers grows..." - Uwe Ohse in the monastery
>

Sent via Deja.com
http://www.deja.com/ Received on Mon Feb 12 2001 - 05:56:54 CST