Windows cannot establish a connection to <domain>

  • Thread starter Thread starter martin
  • Start date Start date
M

martin

Hi!

Several laptops here are showing the follwoing event-logs:

Windows cannot establish a connection to <domain> with
(0x2733). (Event id 1000)

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. (Event id 1000)

Due to these errors, GPO's aren't applied (and thats too
bad cause we have several published applications whitch
aren't installed). I've already disabled the internal NIC
(these laptops are in docking stations) and updated the
drivers.

Does anybody have seen this (and hopefully resolved)
before??

Thanks,
martin
 
Are you able to access the sysvol share after you logon, using the domain
name and dc names?
\\domainname\sysvol
\\dcname\sysvol
Are you receiving any other errors in the application log such as 1202?
Are the laptops on the Lan or connecting remotly?
 
james,

i could access both \\domain\sysvol and \\dc\sysvol
without any problems.
nother errors are logged. Only these 2 but both of them
twice (once for NT AUTHORITY\SYSTEM, once for the user).
laptops are connected to the LAN.

regards,
martin
-----Original Message-----
Are you able to access the sysvol share after you logon, using the domain
name and dc names?
\\domainname\sysvol
\\dcname\sysvol
Are you receiving any other errors in the application log such as 1202?
Are the laptops on the Lan or connecting remotly?


--
James Brandt [MSFT]


martin said:
Hi!

Several laptops here are showing the follwoing event- logs:

Windows cannot establish a connection to <domain> with
(0x2733). (Event id 1000)

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. (Event id 1000)

Due to these errors, GPO's aren't applied (and thats too
bad cause we have several published applications whitch
aren't installed). I've already disabled the internal NIC
(these laptops are in docking stations) and updated the
drivers.

Does anybody have seen this (and hopefully resolved)
before??

Thanks,
martin
Click to expand...


.
Click to expand...
 
Back
Top