Discussion Locked

Windows can't query for Group Policy

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a W2K Pro machine spitting back the following message in Application Log:

"Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by this policy engine."

I followed suggestions to unlink and relink the GPO from:
http://www.eventid.net/show.asp?DocId=15

It did not work. The W2K server only shows one error.

Event Source: MRxSmb
Event Category: None
Event ID: 8003

The master browser has received a server announcement from the computer FF3000 that believes that it is the master browser for the domain on transport NwlnkNb. The master browser is stopping or an election is being forced.

This client has 1 W2K PDC, and 1 Novell 5 server.
This clienthas 29 other identical PCs, of which only 1 other displays this error.

Environment also includes Symantec Velociraptor Firewall. Primary DNS for workstations is PDC address, secondary is Velociraptor. PDC is running Exchange 2000. No useage errors have been reported by other user with error message

10 replies

by cj_mcnix

PC was originally named FF37. However, opening a web browser resulted in Error 403: Forbidden for any web page. I deleted the Computer Account from PDC, and added a new one called FF3000. I then set the PC to join the "NONE" WORKGROUP. I also changed the computer name to FF3000. I rebooted it and rejoined the domain. The ID Wizard informed me that a Computer Account was found, and will be used.

by joseph moore

Did you look up error 8003 at eventid.net for this suggestion:

"In order to stop this error from occuring, use Regedit and set the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList from Auto to FALSE

This will prevent the computer from attempting to become a Domain Master Browser and compete with Domain Controllers."

But before you do this on your Win2K server, I would get a copy of BROWSTAT.EXE from the Resource Kit. Browstat is the computer browser tool. You can use it to get the status of the computer browser service running on your LAN. YOu can use it to check to see who is the master browser, and what backup browsers there are.

I just ran it on my LAN, and here is what I get using its Status switch:

C:\>browstat status

Status for domain MYDOMAIN on transport \Device\NetBT_Tcpip_{AB43C4CD-28EF-4231-90
0B-20B79420901A}
Browsing is active on domain.
Master browser name is: MYPDC
Master browser is running build 1381
3 backup servers retrieved from master CHMSNTP01
\\SERVER2
\\SERVER3
\\SERVER4
There are 65 servers in domain MYDOMAIN on transport \Device\NetBT_Tcpip_{AB43
C4CD-28EF-4231-900B-20B79420901A}
There are 14 domains in domain MYDOMAIN on transport \Device\NetBT_Tcpip_{AB43
C4CD-28EF-4231-900B-20B79420901A}

hope this helps

by cj_mcnix

Thanks for responding, however, I have seen the 8003 error elsewhere at this client without the issue at hand, which is:

"Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by this policy engine."

I simply added the 8003 error to be as complete as possible.

by ctmoore1998

A master browser election usually points to a incorrect TCP/IP subnet configuration. If a workstation or another server has a subnet mask larger than the PDC it will force a master browser election verify that all TCP/IP configurations are correct.

by cj_mcnix

Thanks for responding, but we've seemed to go off track. The actual issue is:

"Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by this policy engine."

I have done some research, but I haven't come across any mention of this error in conjunction with the 8003 error which would indicate that as the issue.

by wburrows

Have you tried running the netdiag resource kit utility on the computer having the problem? While it may not fix the problem it tends to point out problems that may be preventing the download of group policy. Group policy is primarily DNS based soI would expect a failure of GP to be a DNS problem not a WINS/Browsing problem. I could be wrong though.

by cj_mcnix

Turns out that the 403 Forbidden error was a result of a problem with the firewall reaching it's license limit. The Event Viewer issues may have been related.

This discussion is closed to new replies.