| How protect unauthorised Users [message #367786] |
Sat, 17 June 2000 08:43  |
Rajesh Matkar
Messages: 20
Registered: September 1999
|
Junior Member |
|
|
Hello,
How can protect Oracle (Oracle 8.0.5 on Windows NT) database to connect with unauthorised m/c or IP ? Is there any way to protect or allow selected users to connect with Oracle database ? I really appriciate your valuable answer .
Thanx
|
|
|
|
|
|
| Re: How protect unauthorised Users [message #367788 is a reply to message #367786] |
Thu, 22 June 2000 04:40  |
Pete Shaw
Messages: 4
Registered: June 2000
|
Junior Member |
|
|
Rajesh,
You can utilise the protocol.ora file (lives in $ORACLE_HOME/network/admin) to allow only certain IP address. After entry to this file you must bounce the Listener for the changes to take affect. Here is an example of a protocol.ora file...
TCP.validnode_checking=yes
TCP.invited_nodes=(172.31.16.144, # A.User
172.31.15.139, # P.Shaw(DBA)
20.9.189.195) # A.User
|
|
|
|
| Re: How protect unauthorised Users [message #367802 is a reply to message #367788] |
Sun, 20 August 2000 20:29 |
Mitch Shields
Messages: 2
Registered: August 2000
|
Junior Member |
|
|
running Oracle 8.1.6 on Linux
I have created a protocol.ora file in that directory and it is not found by the listener (or at least that is what the trace file says )
ntvllt: No PROTOCOL.ORA file is found
I have tried numerous spellings and capitalizations of the filename with no luck. It is sitting right next to the listener.ora..
Any thoughts would be appreciated.
|
|
|
|
| Re: How protect unauthorised Users [message #367803 is a reply to message #367788] |
Mon, 21 August 2000 03:23 |
Pete Shaw
Messages: 4
Registered: June 2000
|
Junior Member |
|
|
Mitch,
Could be a number of things, Assuming you are not using the Advanced Networking Option then set sqlnet.authentication_services=(none)
in sqlnet.ora file, this will disable SQL*Net authentication services while still allowing normal SQL*Net connections.
There did seem to be a couple of bugs around in 8.1.5 (not sure if they are fixed in 8.1.6), one
workaround somebody had was to rename the protocol.ora to .protocol.ora (note the dot prefix), sorry I can't be of more help.
Pete.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
