All remote authentication fails on server 2003

I have a system with Windows Server 2003 standard with an installation
of SQL server 2000, Sharepoint Services and various other web sites and
shares. Today I am not able to access any web site, share or sql, even
with the domain admin password. I can log into the server using remote
desktop and access everything fine locally. If I go into the local
policy, I noticed that the allow remote access to this computer was
blank, so I added some names and everything seemed to work normally
again. However in a few minutes everything began being denied once
again, even though the names are still listed in the policy. If I then
removed a name from the list, the other names began working again for a
short period. I haven't been able to nail down to exactly how long
before it stops, but it is at least 4-5 minutes.

This may be related:
Another IT member was looking at some things on this server, and said
he checked and then unchecked Enable DCOM in component services to test
something. On this server, the registry entry to enable DCOM already
has 'Y' as it's value, however the box has never been checked before.

Does anyone here have ideas of what else we can check to get this
computer to allow remote access again?

Did you ever get this resolved? I have a similar situation, but not
exactly. When you say you are unable to access the server, what indication
do you get of this? Does it tell you shares don't exist, or the computer
cannot be found, or what?

Marc

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have a system with Windows Server 2003 standard with an installation
> of SQL server 2000, Sharepoint Services and various other web sites and
> shares. Today I am not able to access any web site, share or sql, even
> with the domain admin password. I can log into the server using remote
> desktop and access everything fine locally. If I go into the local
> policy, I noticed that the allow remote access to this computer was
> blank, so I added some names and everything seemed to work normally
> again. However in a few minutes everything began being denied once
> again, even though the names are still listed in the policy. If I then
> removed a name from the list, the other names began working again for a
> short period. I haven't been able to nail down to exactly how long
> before it stops, but it is at least 4-5 minutes.
>
> This may be related:
> Another IT member was looking at some things on this server, and said
> he checked and then unchecked Enable DCOM in component services to test
> something. On this server, the registry entry to enable DCOM already
> has 'Y' as it's value, however the box has never been checked before.
>
> Does anyone here have ideas of what else we can check to get this
> computer to allow remote access again?
>