Re: Oracle and Firewall

2003-11-23 Thread Tanel Poder
If you specify USE_SHARED_SOCKET in registry for your Oracle home and restart the listener, the 1521 port can be shared between both listener and database connections (in case of dedicated server). That way you won't have port problems with firewall. Tanel. - Original Message - To:

Oracle and Firewall

2003-11-21 Thread Seema Singh
Hi, We are using Oracle817 on Windows with netscreen firewall.I have been noticing after some times applications start connecting form 1521 to 1034 and so.IS this normal ?I want port 1521 Only in use. How to fix this problem? thx -Seema

RE: Oracle and Firewall

2003-11-21 Thread Luc . Demanche
Hi Seema, Take a look on this document #131524.1 on Metalink. You will have to add an entry in the registry to force the connection to only use the port 1521 USE_SHARED_SOCKET=TRUE Luc -Original Message- Sent: November 21, 2003 11:21 AM To: Multiple recipients of list ORACLE-L Hi, We

Re: Oracle and Firewall

2003-11-21 Thread Arup Nanda
Seema, This is a typical misconception on the workings of Net8. Port 1521 is only used to contact the listener, after that the listener might: a) create a server process which listens on a port other than 1521 OR b) pass the connection to a prespawned server process, again on a different port.

RE: Oracle and Firewall

2003-11-21 Thread Thater, William
Arup Nanda scribbled on the wall in glitter crayon: (1) use firewall around the subnet where both app/web server and db server exist; not a firewall between them. (2) Use TCP Node checking to restrict Net8 traffic to the db server only from the app server. (3) Use Connection Manager. USing