Xref: alice comp.databases.oracle.server:73540
Path: alice!news-feed.fnsi.net!netnews.com!newspeer1.nac.net!news.maxwell.syr.edu!nntp2.deja.com!nnrp1.deja.com!not-for-mail
From: Christ Follower <christ_follower@my-deja.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Remote connection through NAT
Date: Thu, 11 Nov 1999 15:01:33 GMT
Organization: Deja.com - Before you buy.
Lines: 87
Message-ID: <80eloa$s3b$1@nnrp1.deja.com>
References: <80cjo8$d2h$1@nnrp1.deja.com> <DdspOElGnVvbwNHN4+52wTMvCEQj@4ax.com>
X-Article-Creation-Date: Thu Nov 11 15:01:33 1999 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
X-Http-Proxy: 1.1 x32.deja.com:80 (Squid/1.1.22) for client 209.95.85.33
X-MyDeja-Info: XMYDJUIDchrist_follower

The Oracle version is 8.0.5 and running on Sun Solaris. The clients are
a mixed of NT and Unix. Actually I am trying to establish a remote
database link that would use one Oracle on Solaris as a client to
connect to a second Oracle on Solaris. We tested in one facility
(without NAT complication) and everything worked. However, when we try
to deploy the system, it does not work because of NAT.

I turned on tracer on server listener and the connection
was "established"! The SQLNET.LOG on the client side generate the
following error:
  VERSION INFORMATION:
        TNS for Solaris: Version 8.0.5.0.0 - Production
        TCP/IP NT Protocol Adapter for Solaris: Version 8.0.5.0.0 -
Production
  Time: 11-NOV-99 09:29:36
  Tracing not turned on.
  Tns error struct:
    nr err code: 12203
    TNS-12203: TNS:unable to connect to destination
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 148
    nt OS err code:
0

In article <DdspOElGnVvbwNHN4+52wTMvCEQj@4ax.com>,
  tkyte@us.oracle.com wrote:
> A copy of this was sent to Christ Follower <christ_follower@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@us.oracle.com
> Oracle Service Industries     Reston, VA   USA
>
> Opinions are mine and do not necessarily reflect those of Oracle
Corporation
>


Sent via Deja.com http://www.deja.com/
Before you buy.