Windows XP cant get \ apply Windows 2000 GPOs

[bowwow]

We are doing testing with GPOs within an Windows 2000 Server evironment with XP clients. Using a basic Default Domain GPO clients are unable to access the GPO template Sys file. Servers apply the GPO no problem.

Errors received on the XP client are 1030 and 1058. The USERENV file suggests that it may be a problem with DNS, however the servers A and SVR records are registered correctly. The following registry entries have been checked:

SMB signing issue address via Hotfix Q329170\331519
DFS enabled on client, see Q314494

Have any of you come across this issue?
Any help much appreciated, were in the middle of Proof of Concept and time is tight !!!

 

[senwebtek]

I'm experiencing the same problem on Dell 2350 XPPro sp1 in a Windows 2000 domain; I get 'unable to find Domain Controller' group policy processing aborted. I've applied the SMB signing workaround to the DC GPO and also set the clients to 'always wait for network' in the local policy. This problem only seems to occur with the built in Broadcomm 10/100 NIC; If I put an Intel NIC in a PCI slot, everything works fine and GPO are processed normally. I tried updating the drivers for the internal NIC, but get the same results. Anybody have any ideas? This is driving me nuts

 

[bcastner]

semwebtek,

Try forcing the NIC to 20-half in the Properties, Configure page for the adapter.

Often the NIC does not autonegotiate successfully, the error becoming more apparant in traffic dealing with the credentials of the remote user.

 

[senwebtek]

Thanks bcastner... I assume you mean 10 or 100 Mbs and half-duplex in your message. Not sure what you meant by 20-half. Anyway, I've tried forcing 10 Mbs and 100 Mbs in both full and half duplex with the same results. But I'll try again.

 

[bcastner]

sorry, meant 10 half. My touch typing left pinky failed me.

I should warn you that Microsoft discourages what you want to do from XP clients. This has to do with the extensions that XP carries with it for GPOs. Most have found that as a practical matter things work out a lot better using Win2k clients for this management task.

Make sure that there are no permission issues. The user must have local administrative rights as well as be authenticated as a member of the Domain Controller Administrator group.