This is a standing bug: the Oracle will assign client a ramdon port without
definit bondary. You have to run Oracle in singl session mode or you have to
open all the ports. Firwall-1 do not understand Oracle's propietary
algorithm on multi-session management.
-----Original Message-----
From: Patti Johnson [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 10:43 AM
To: '[EMAIL PROTECTED]'
Subject: [FW1] Oracle
I am never gonna get this client install done... *sigh*
My client (customer) is running oracle behind the brand new firewall. From
inside, they can use their Oracle client software (I think it's SQL*net).
>From the outside of the firewall, they run the software, but they get a
message back that they couldn't be authenticated. When I run a TCPdump on
the firewall, I see their client communicate with port 1521 of the Oracle
server, and the server communicates back to their software. When I look at
the log, I see an entry for SQL*net, and the connection was accepted. This
software runs perfectly fine on the inside, we just can't get it to run
outside. Other than 1521, are there any other ports that I need to
specifically enable.... does SQL*net have problems dealing with NAT
addresses?
--patti
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
