Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: changing workgroup corrupts autostart service on windows 2000?

Re: changing workgroup corrupts autostart service on windows 2000?

From: FC <flavio_at_tin.it>
Date: Mon, 19 Jan 2004 15:51:09 GMT
Message-ID: <N1TOb.113646$VW.4630290@news3.tin.it>

"FC" <flavio_at_tin.it> wrote in message
news:LuXNb.129596$_P.4632654_at_news4.tin.it...
> Hi all,
> I am experiencing problems with the autostart setting of a database
service
> and instance, after changing the workgroup.
> This happens on Windows 2000 server + SP3 and Oracle 9.2.0.1.0.
> I found a message suggesting to recreate the service using ORADIM but it
> didn't work.
> The event viewer does not show any entry for oracle unlike normally
happens
> upon booting up the machine and also the ALRTxxxx.log file doesn't record
> anything.
> It looks like the service doesn't start at all.
> All Oracle registry setting seem ok, I didn't change them since the db
> installation.
> If I start the db manually, it works fine.
> I am going to reinstall Oracle from scratch unless someone comes up with a
> solution first.
>
> Any ideas?
> Bye,
> Flavio
>
> --
>

While looking for possible reasons, I came across a detailed post in a forum stating that NT authentication on a standalone machine is implemented via NTLM when Kerberos is not installed, so I started reading another document describing NTLM authentication protocol and I started to realize why a workgroup name change might cause such mess. I say "might" because I couldn't find a specific document mentioning the windows workgroup as a piece of information actually involved in the message exchange between the server and the client, the machine name and the domain name are cited instead, so I am just assuming that on a domainless machine, the workgroup could replace the domain.

However, I'd expect that deinstalling Oracle and cleansing the registry and reinstalling everything would do the trick, but with deep surprise it doesn't.
I am still wondering which part of the registry needs to be deleted other than HKLM/Software/ORACLE in order to make it work again. Of course commenting out SQLNET.AUTHENTICATION_SERVICES is still an option, but as I said in another post, I love connecting as sysdba using "/ as sysdba" from a command line.
I'd really like to cure the disease rather than alleviate the pain.

Bye,
Flavio Received on Mon Jan 19 2004 - 09:51:09 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US