You might not ever be able to get this working...

SQLNet v2, depending on how the listener is configured, will send the IP
address of the DB server as part of the connection protocol.
The client then uses the IP addresses given to it as the IP address to
connect to. The IP address that the listener sends, (you guessed it)
is the IP address on the local DB server. I.E. the internal non-routable IP.

Now with that being said...

You should be able to, in theory, do the following:
Suppose client ABC wants to connect to the database DB1 at company XYZ,
hosted on dbserver.xyz.com:
dbserver.xyz.com has an internal IP of 10.1.1.1, it is NATTED externally to
209.82.9.10.
dbserver.x.y.z.com has a DNS entry already pointing to the external IP
209.82.9.10.

1) configure your client tnsnames.ora file to point to the EXTERNAL
Hostname/IP of the DB server: I.E. 209.82.9.10.

DB1 =
  (description =
     (address_list =
        (address =
           (protocol = tcp)
           (host = dbserver.x.y.z.com)
           (port = 1521)
        )
     )
     (connect_data =
        (sid = DB1)
     )
  )

2) Configure the listener.ora file on the DB server to use the EXTERNAL IP
of the database. Not the internal one.

LISTENER =           # Listener name is LISTENER
  (address_list =
     (address=
        (protocol=ipc)
        (key=DB1)
     )
     (address=
        (protocol = tcp)
        (host = 209.82.9.10)
        (port = 1521)
     )
  )
  STARTUP_WAIT_TIME_LISTENER = 0
  CONNECT_TIMEOUT_LISTENER = 10
  TRACE_LEVEL_LISTENER = ON
  TRACE_FILE_LISTENER = $ORACLE_HOME/network/trace/listener.trc
  SID_LIST_LISTENER =
    (SID_LIST=
       (SID_DESC=
          (SID_NAME=DB1)
          (ORACLE_HOME=$ORACLE_HOME)
       )
    )

If a conflict arises with local vs. external IPs.. you can always setup the
listener to use the local IP on one port, and the external IP on another.
The Firewall that does the NAT should then be able to take care of any/all
NAT.

Disclaimer: This is all theory. I have not actually done the above. It is
based on my somewhat limited knowledge of SQLNet.


--
The early bird gets the worm, but the second mouse gets the cheese..

Trevor Paquette              |    AT&T Canada     |Work:(403)705-6390
[EMAIL PROTECTED]|600, 205 5th Ave SW | Fax:(403)705-9601
http://www.attcanada.com     |Calgary, AB, Canada |ICBM:51'03"N/114'05"W
Senior Unix Network Architect|       T2P 2V7      |Mind:In the Rockies

> -----Original Message-----
> From: Joe Delsol [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 09, 2000 4:20 PM
> To:   FW-1 List (E-mail)
> Subject:      [FW1] SQLnet over NAT issue..
> 
> 
> Our database is on a non-routable address and we are allowing connections
> from the outside to it via the SQLnet protocol.
> 
> The clients connection is received by the server, but the client claims it
> was not able to establish the connection. 
> 
> Any ideas? 
> 


================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to