Re: SQL*Net through firewall with NAT

Certain firewall products (Raptor, TIS) support SQL*Net proxies. If yours does not, you may have a difficult problem to solve.

Johannes Blankenstein (jbla_at_giraffe.snafu.de) wrote:
: In article <6jjudr$e1g$1_at_news.nacamar.de>,
: "Lutz Rabing" <lutzrab_at_omc.net> writes:
: > we just moved an oracle database behind a firewall with
: > NAT (network address translation). the firewall is completely open, but
: > does translate "real" IP's to the public address range 192.168.1.xxx
: >
: > everything works fine except SQL Net. we can't establish ODBC connections
: > to the database. I think the listener returns the public IP (192.168.1.xxx)
: > to
: > the client. Is there a way to return the real IP to the client?

: Today I returned from a SQL*NET V2 course and I learned the following: ;-)

: It seems that Oracle does some dirty hack within their implementation.
: They hide something within the TCP/IP packets which can´t be corrected by
: a normal firewall or gateway.

: May be the solution could be to install ´MultiProtocol Interchange´ on
: your firewall and define two communities (one for inside and one for
: outside your firewall). I think (hope) that MPI will translate the IP
: adresses between your two networks.

: Hannes

: --
: Johannes Blankenstein; Berlin; Germany
: Email: jbla_at_giraffe.snafu.de
: jbla_at_giraffe.in-berlin.de

--

Jared Hecker	| HWA Inc. - Oracle architecture and Administration
jared_at_hwai.com	|  ** serving NYC and New Jersey **