| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle versus MS Sql Server
Maybe its time to ask what 'does not work' in your connect example means..
( without NTS)..
also,
Here are some details about SQLNET.AUTHENTICATION_SERVICES from the on-line docs:
Default:
None
Values:
Authentication Available with Net8:
NONE - No authentication methods are used. A valid user name and password can be used to access the database.
ALL - Enables all authentication methods to be used
BEQ - Uses the Bequeath protocol
NDS - Uses NDS authentication
NTS - Uses Windows NT native authentication
Authentication Available with Oracle Advanced Security:
KERBEROS5 - Uses Kerberos authentication
SECURID - Uses SecurID authentication
CYBERSAFE - Uses Cybersafe authentication
IDENTIX - Uses Identix authentication
RADIUS - Uses RADIUS authentication
DCEGSSAPI - Uses DCE GSSAPI authentication
See Also: Oracle Advanced Security Administrator's Guide
Example:
sqlnet.authentication_services=(beq, kerberos5, cybersafe)
John G
"Michael G. Schneider" <mgs_at_mgs-software.de> wrote:
>"Mark Townsend" <markbtownsend_at_home.com> schrieb im Newsbeitrag
>news:B7F5C9B0.3C65%markbtownsend_at_home.com...
>> in article 9qpf4o$tb4$03$1_at_news.t-online.com, Michael G. Schneider at
>> mgs_at_mgs-software.de wrote on 10/19/01 7:59 AM:
>>
>> > [6] One more piece of information, which I cannot interpret correctly.
>When
>> > connecting to the database, I will fail if I connect as "SYS" or
>"SYSTEM"
>> > with the "AS SYSDBA" option. The "AS SYSDBA" can only be used with
>> > "INTERNAL". Does this give any hint or information to an expert Oracle
>DBA?
>>
>> This is a symptom of you disabling the OS authentication in SQLNET.ORA.
>All
>> your problems stem back to some common root cause - and I'm absolutely
>> convinced that there is an issue with your PDC - either it's not working
>> correctly, has been changed half way during the install, or something
>> similar.
>>
>> For instance, I have seen all your problems when a user on a network
>(logged
>> on under a given domain) has installed on a laptop. While on the network,
>> everything works. When the user disconnects from the network, but still
>logs
>> on to the same domain all these problems occur. Logging on the the actual
>> laptop domain solves the problem. Hopefully you can relate this back to
>your
>> own configuration for similarities.
>>
>
>Of course, one can never be sure. But this is a freshly installed Windows
>2000 Server. And it has no obvious problems at all. Let me try to explain,
>what the SQLNET.AUTHENTICATION_SERVICE is used for. Please correct me, where
>I am wrong.
>
>The SQLNET.AUTHENTICATION_SERVICE setting is used for describing the
>authentication schema. My original setting (as done by the SETUP) has been
>NTS, which means that the account of the logged on user plays a role in the
>authentication process. By clearing this value, I told Oracle not to use the
>currect user account. The complete information for authentication (name +
>password) would be sent in a connection attempt.
>
>So if I perform a logon
>
> - as user SYS
> - with password given
> - AS SYSDBA
>
>and it does not work, I do not yet understand what my PDC and it's Directory
>has to do with this.
>
>If I were connecting with the NTS setting without giving a password, then
>Oracle would have to "talk" to the PDC. Under this setting problems might
>arise, if the PDC is not working correctly.
>
>Michael G. Schneider
>
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! Check out our new Unlimited Server. No Download or Time Limits! -----== Over 80,000 Newsgroups - 19 Different Servers! ==----- Received on Fri Oct 19 2001 - 15:17:49 CDT
 |
 |