I am using SQL*Plus 3.3 to connect to Oracle 8.0.4 server on WinNT 4.0.
QUESTION:
Due to security reasons, the network traffic is restricted (through an IP
gateway emulated by a Linux server), and since I used to think that SQL*Net
is using
ports 1521 or 1526, I asked the network team to release traffic between
server ports 1521, 1526 and my PC ports 1024 and above.
However, this did not work. We finally need to open the traffic between
server ports 1024 and above and my PC port 1024 and above.
INITIAL GUESS:
Is it that SQL*Net can be set to be dynamically binded? In UNIX, we see that
in /etc/services, the SQL*Net port is binded to 1521/1526, but I don't see
such an entry in any of our NT installations (maybe cos' for other
installations, we do not need to
import traffic restrictions).
Can anyone help?
Many many thanks.
Rgds.,
fan.
(Yat-Fan HO, The Kowloon-Canton Railway Corp., HONG KONG)
ps. It's best if in addition to posting a reply, also forward one copy of
the reply to
me. Many thanks again.
Yup, that's the so-called "plug-and-play listener." You can turn
that off in listener.ora so that all connections are to the
specified port.
Rick Brown
ri...@onramp.net
Hope this helps
Helmut
>Is it that SQL*Net can be set to be dynamically binded?
Port numbers for the listener (server) and SQl*Net clients is specified in
$ORACLE_HOME/network/admin directory for Oracle 7.x and in the
$ORACLE_HOME/net80/admin. Check the files listener.ora and tnsnames.ora
> In UNIX, we see that
>in /etc/services, the SQL*Net port is binded to 1521/1526, but I don't see
>such an entry in any of our NT installations
You'll find the services, host, lmhosts and other network text configuration
files on NT in the directory WINNT\SYSTEM32\DRIVERS\ETC
regards,
Billy
Thanks.
Why do we need to specify the port in UNIX /etc/services but not in NT
SERVICES file?
Thanks again.
Rgds.,
fan.
Billy Verreynne wrote in message <6nigdj$sgp$1...@hermes.is.co.za>...
> Why do we need to specify the port in UNIX /etc/services but not in NT
> SERVICES file?
You only need to specify a port in the services file if you configure the
client or server software to use the name of the service and not the actual
number of the port. (which is the "correct" way to configure network services
anyway)
For example, instead of hardcoding a port number in a config file, you
specify the name of the service. The services file is then used by the
sockets API to look up the port number to use. This way, you can reconfigure
the services port numbers quite easily. If the client/server services use
hard coded portnumbers, you have less flexibility in re-configuring your
network services.
So the answer to your question is that you do not need to touch the services
file on either Unix or NT if you're using port numbers in the Oracle config
files for the listener and SQL*Net services. However, if you're using service
names instead, you have to define that service and the service's port number
in the services file.
regards,
Billy
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
I know Oracle uses the definition port in listener.ora.
The port numbers, 1521, 1525 of /etc/services is just recommend by
Oracle Co.
But you can use any port that is not using in your system.
Check point)
First, you must change sql*net port number in listener.ora
then, restart your listener.
Second, you must chage client part.That is to say, the port number
should be changed in tnsnames.ora. This is located in your client,
PC or NT.
Centainly, you should use same port number listener.ora (server part)
and tnsnames.ora (client part)
Good luck!
Yat-Fan wrote:
> Hello all,
>
> I am using SQL*Plus 3.3 to connect to Oracle 8.0.4 server on WinNT
> 4.0.
>
> QUESTION:
> Due to security reasons, the network traffic is restricted (through an
> IP
> gateway emulated by a Linux server), and since I used to think that
> SQL*Net
> is using
> ports 1521 or 1526, I asked the network team to release traffic
> between
> server ports 1521, 1526 and my PC ports 1024 and above.
>
> However, this did not work. We finally need to open the traffic
> between
> server ports 1024 and above and my PC port 1024 and above.
>
> INITIAL GUESS:
> Is it that SQL*Net can be set to be dynamically binded? In UNIX, we
> see that
> in /etc/services, the SQL*Net port is binded to 1521/1526, but I don't
> see
> such an entry in any of our NT installations (maybe cos' for other
> installations, we do not need to
> import traffic restrictions).
>