Those are bizarzare problems and hard to troubleshoot without being there.
Make sure you are using a firewall. It almost sounds as somebody [remotely]
or some program has control of your computer. You could try sfc /scannow to
activate System File Checker to check system files but if it was my
computer, I would back up all my important data [including our user profile
under documents and settings] and configuration information such as tcp/ip
config, mail/newsgroup accounts, favorites, etc and format drive and
reinstall being sure not to connect to the internet until I had a firewall
in place either hardware or software and virus scan installed, updated, and
used for email also. --- Steve
http://www.microsoft.com/security/protect/
"Peter" <(E-Mail Removed)> wrote in message
news:718c01c3b401$239b67a0$(E-Mail Removed)...
> I log on as administrator and always have access to the
> local security settings and group policy just after the
> computer has started up. Then after some time (from a few
> minutes to an hour) I'm denied access. And therefore also
> get problems with writing temp files to the harddrive -
> and get errors returned, that I don't have rights to write
> files. This happens although I'm logged on as
> administrator and otherwise don't have any problems
> accessing all folders and change settings.
>
> - The computer is set as member of a workgroup, not of a
> domain. I tried working without virus scan, which didn't
> make any change. The problem also occur after a while even
> if I don't run any programs on the computer.
>
> - Sometimes when accessing Local security policy is seems
> the computer is first scanning all the harddrive and cd-
> rom drive before opening the policies, possibly searching
> the file, eventhough it is in winnt\security.
>
> - The logbook earlier gave error event 1202. I recreated
> the local Group policy using article 278316. This solved
> the event 1202 problem. But somehow the access to the
> security policy is still denied after the computer has
> been running for a while.
>
> I hope someone has ideas on what could be wrong.
>
> Peter