Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!newsfeed.news2me.com!cyclone1.gnilink.net!ngpeer.news.aol.com!uunet!dca.uu.net!prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr14.news.prodigy.com.POSTED!34d3422d!not-for-mail From: Karsten Farell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.databases.oracle.server Subject: Re: Connecting to server using SQLPlus through a gateway References: <4ae06f4d.0210071300.5d2bc6be@posting.google.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lines: 35 Message-ID: NNTP-Posting-Host: 67.117.210.172 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr14.news.prodigy.com 1034263844 ST000 67.117.210.172 (Thu, 10 Oct 2002 11:30:44 EDT) NNTP-Posting-Date: Thu, 10 Oct 2002 11:30:44 EDT Organization: Prodigy Internet http://www.prodigy.com X-UserInfo1: [[PAPDCAO@U_RITXYRHNO_TDFZ\@@FXLM@TDOCQDJ@_@FN@ANVUEAE[YETZPIWWI[FCIZA^NBFXZ_D[BFNTCNVPDTNTKHWXKB@X^B_OCJLPZ@ET_O[G\XSG@E\G[ZKVLBL^CJINM@I_KVIOR\T_M_AW_M[_BWU_HFA_]@A_A^SGFAUDE_DFTMQPFWVW[QPJN Date: Thu, 10 Oct 2002 15:30:44 GMT Xref: newsfeed1.easynews.com comp.databases.oracle.server:163735 X-Received-Date: Thu, 10 Oct 2002 08:31:02 MST (news.easynews.com) Jake wrote: > I've heard this before, that the client starts the conversation on port > 1521, but then is given a new, random port for the duration of the session. > > BUT, my real setup contradicts that: > > ---DSL---Linksys Router + Switch ----Oracle server > > On my linksys router I forward port 1521 to the IP of my Oracle server and > all is OK. I can connect via sqlplus from the other side of the internet > (i.e. externally). > > Maybe it's the port forwarding that is helping me out? > > Jay > I am not sure why your setup works. It doesn't take long for me to get way over my head in the networking world. :) I only found out about the random port assignment after looking at a rather verbose net8 trace file (after consulting with oracle tech support). The trace file clearly (if that's possible for a trace file) pointed to the error ... a failure after the dispatcher took over on the new port. I know that our net admin blocks all ports except those he knows about. Do you block all unknown ip addresses on your router? I have the Linksys router/switch at home, but don't block everything (should I admit that in a public ng?) so I can connect to the database from home. At work, we implemented MTS to force (ask nicely) the dispatcher to use one of 3 "known" ports that our net admin allowed to be opened through the firewall to our oracle server (but only from that ip).