Well, someone finally hit the nail on the head. Sorry, but I've been too busy to read & reply. VPN software makers normally block telnet traffic and Sql*Net is something like Telnet traffic as I understand from my network engineer. But they also each have a way to recognize & permit Sql*Net traffic as a subset of telnet, without opening up telnet. Have your network guru look at the software & set it up accordingly. It's what we had to do with Neoteris.=20 Dick Goulet Senior Oracle DBA Oracle Certified 8i DBA -----Original Message----- From: Shrek [mailto:shrekdba@xxxxxxxxx]=20 Sent: Thursday, December 16, 2004 10:53 AM To: Carol.Bristow@xxxxxxxx Cc: mzito@xxxxxxxxxxx; Oracle-L (E-mail) Subject: Re: [Q] sqlplus through VPN not work, but tnsping work On Thu, 16 Dec 2004 09:27:13 -0600, Carol Bristow <Carol.Bristow@xxxxxxxx> wrote: > As mentioned in an earlier message (I forget by who at the moment), only > the initial SQL*Plus connection goes through port 1521 (or whichever > port your listener is listening on). Once the initial connection is > made, a different port number is dynamically assigned to the session. > There is a way to force all traffic to go through a single port, but I > had problems when I tried to set it up in version 8. Check the > Netowking documentation. most firewalls have modules that will direct SQL*Net traffic through one port. you need to get the firewll admin to look into getting and configuring the SQL*Net proxy for whatever firewall you have. that way they only have to open one port for all the traffic. --=20 -- Bill "Shrek" Thater ORACLE DBA =20 shrekdba@xxxxxxxxx=20 ------------------------------------------------------------------------ I am my beloved's, and my beloved is mine (Song of Solomon 6:3) -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l