> -- --Original Message-- -- > From: Hans Forbrich [mailto:hforbric_suse@(protected)] snip > - your program talks to the listener on port 1521 using > Oracle Networking > > * the listener tells the Oracle kernel to start up a > dedicated process > * - dedicated will connect to a free port other than 1521 > - there are firewall implications to this! snip Actually, in the *nix world the connection stays on 1521. So, the only firewall issue is opening port 1521 to inbound connections. In the windows world the default behavior is to open up and switch to another free port other than 1521. BUT! In windows 2003 (and possibly Win2K) there are registry settings that you can use that will KEEP the client connected to the server via 1521, just like *nix. So, these days there isn't a need for firewalls with SQLNet proxies.
All of our Oracle servers (Windows and Linux) are configured to allow inbound traffic only on 1521 and they work perfectly with clients AND other Oracle servers.
I think you are right in that older versions of SQL*Net used extra ports besides 1521, but at least in 9i that behavior has changed. Weee! No more firewall fixup rules!
Andy
-- To unsubscribe, email: suse-oracle-unsubscribe@(protected) For additional commands, email: suse-oracle-help@(protected) Please see http://www.suse.com/oracle/ before posting
