Just a thought, turn auditing on for logon failure. You might garner some
helpful information from the audit log.
Ted
"Walter T Rejuney" <BlueSax_at_Unforgetable.com> wrote in message
news:39B15EB4.BDEC4EC3_at_Unforgetable.com...
> Sybrand Bakker wrote:
>
> > AFAIK
> >
> > you need to have
> > sqlnet.authentication_services=(NTS)
> >
> > in your sqlnet.ora
> >
> > Your sqlnet docs you definitely contain info about this.
> > In the past it was necessary to actually login on the server, this was
> > accomplished by sharing out a drive on the database server. The
sqlnet.ora
> > mechanism should have replaced that.
> >
>
> I took at my sqlnet.ora and that line was in there but commented out. I
> uncommented it and for good measure I bounced the database. Still no luck.
>
> I finally opened a TAR and got back a reply that configuring this on NT is
> tricky because it doesn't work in a manner similar to UNIX. I tried the
> various things they suggested and none of them have worked.
>
> Apparently on NT, the domain name comes into play, but the information I
> received in the TAR response was a bit hazy because it tended to suggest
that
> there isn't any particular way that you can really discover what username
will
> be passed in by the OS. The response was further confusing because it
implied
> that when OPS$ is set for os_authent_prefix it changes the way that the os
> passes the userid in - and if that is true then the database is changing
the
> way that the os operates just by changing the value of an oracle
parameter.
>
> I'm still waiting for a further reply on the TAR, but this has become very
> disconcerting since there doesn't seem to be any real answer and I could
spend
> the rest of my life experimenting with it and never come up with the right
> combination because I'd never be guaranteed to make the one correct guess
that
> would be correct.
>
>
Received on Sun Sep 03 2000 - 03:30:12 CDT
