Re: Remote connection through NAT

A copy of this was sent to Christ Follower <christ_follower_at_my-deja.com> (if that email address didn't require changing) On Wed, 10 Nov 1999 20:15:09 GMT, you wrote:

>In our environment, we have a remote db that the db server can be
>reached only through SISCO NAT TCP forward. The listener on that server
>is running on a different (internal) IP that NAT would forward traffic
>to. I am not able to use SQL*Plus to connect to that server. What
>configuration change do I need to do? Thanks.
>
>Danny
>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.

platform?
versions?

I'll guess as to the platform -- NT.

The listener recieves a connection from sqlplus. This works. The listener by default will generate a wild card port number on the NT box and redirect the client to connect to a specific (wrong as far as the client is concerned) IP-Address and portno (a redirection). The client gets this info back from the listener, disconnects from the listener and the tries to connect to this new ip/port. That fails (since the ip address the listener has is not visible to the client).

The solution lies in the version of products. need to know that.

--
See http://osi.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Wed Nov 10 1999 - 14:55:04 CST