XPPro Client Problems in a domain

[Chunkee]

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 12/5/2005
Time: 2:25:10 PM
User: NT AUTHORITY\SYSTEM
Computer: MLINE01
Description:
Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1065
Date: 12/5/2005
Time: 2:25:10 PM
User: NT AUTHORITY\SYSTEM
Computer: MLINE01
Description:
Windows cannot perform filter check for Group Policy object CN={2C7336FD-90E3-4733-8223-67F79328232F},CN=Policies,CN=System,DC=FCM,DC=local. Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 11/4/2005
Time: 11:26:31 AM
User: N/A
Computer: MLINE01
Description:
The Security System could not establish a secured connection with the server ldap/fcmXXXXXXXXXl@FXXXXXX.local. No authentication protocol was available.


I can manage the PC, telent, map unc path shared drives, but cannot RDP into this client nor use the Remote Assistant. This is a SBS2003 domain with XP PRO client.

Any hints...I am exhausted searching, many possibilities it seems.

thanks

JC

 

[spyordie007]

but cannot RDP into this client nor use the Remote Assistant

RDP/Remote assistance are independant of the domain client functionality.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 12/5/2005
Time: 2:25:10 PM
User: NT AUTHORITY\SYSTEM
Computer: MLINE01
Description:
Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

What is the previous error that is logged?

Even without the error definetly ensure internal DNS is functioning correctly. I see a lot of SBE users configuring the clients to use their ISP's DNS servers for the client machines rather than their DC and this can cause all sorts of problems.

-Erik

 

[Chunkee]

Hi Erik, thanks for posting. The DNS appears to be fine. I know that the alternate DNS entries are of the ISP Bellsouth DSL, but does that matter if the first DNS resolved is the servers?

thanks so much for replying.

JCoria

 

[TG2]

I think the clients should *only* have the active directory DNS server entries.

 

[spyordie007]

Originally posted by: TG2
I think the clients should *only* have the active directory DNS server entries.

This is correct, in most deployments you arent going to want your clients going to external DNS servers for host resolution.

but cannot RDP into this client nor use the Remote Assistant

What happens when you try and connect using the remote desktop client?

 

[Chunkee]

Originally posted by: spyordie007

Originally posted by: TG2
I think the clients should *only* have the active directory DNS server entries.

This is correct, in most deployments you arent going to want your clients going to external DNS servers for host resolution.

but cannot RDP into this client nor use the Remote Assistant

What happens when you try and connect using the remote desktop client?

says standard stuff, cannot connect ...client may be busy..yada yada

can connect via telnet however.

jC

 

[spyordie007]

Can you telnet in to it on the RDC port (3389)? Should give you a blank telnet screen you should not be seeing:
Connecting To [host]...Could not open connection to the host, on port 3389:
Connect failed