Group policy error, loss of access rights?

February 23, 2010 at 05:31:54
Specs: Windows server 2003
Hello all,
Recently I’ve been working with a team to develop a small network to test the security of a new firewall. Inside the network we have a computer running windows server 2003 as well as some client computers. A few days ago one of the teammates installed some hotfixes and made some changes to the server to try and make it more secure, but it seems to have messed up our group policy somehow. Even though we are logged in as administrator it seems to either have the incorrect access rights, or is having trouble with the DNS.
First, when we try to open up the domain security policy or the default security policy we get this error message.
http://s11.photobucket.com/albums/a...
After closing it the policy window will come up, but we can’t do anything with it.
http://s11.photobucket.com/albums/a...
Now as far as rights go we’re pretty sure the account we’re logged in on should work. We were able to make changes to the policies in the past and we’ve confirmed it is a member of all of the administrator groups in the network. It might be a DNS problem, since the first error message says its network related, but I can’t think of anything we’ve changed in that regard recently.
Another problem we’ve found is when we try to open up the WSUS server to push updates to the client machines. When we do we get this error message.
http://s11.photobucket.com/albums/a...
We’ve also confirmed that the file does exist in that path in the picture. Which makes me think this may be a rights problem after all. I don’t have a lot of experience with server so sorry if I haven’t been clear enough. I can try and get more screenshots if you need more specifics. Thanks.

See More: Group policy error, loss of access rights?

Report •

#1
February 23, 2010 at 07:22:12
Each of your links opens a page that says, "The action that you were trying to perform has failed."

Have you researched these errors on MS's "knowledge base" and on google?

If not, start there.

Personally, if it were me, considering this is a lab environment, I wouldn't waste any time trying to fix this issue. I would redo the server from scratch. I wouldn't trust any fix to fix everything.


Report •
Related Solutions


Ask Question