Please wait for the group policy client - shutting down issues

Hi

I have issues with shutting down a machine. When machine is connected to company's network everything works fine. However, if machine is connected to VPN (1 hour or more) it always hangs when it is shutting down. First stage of shut down process is:

Please wait for the system Event Notification service.

This change after exactly 3 minutes. Next stage:

Please wait for the group policy client windows 7

is never timed out (even after few hours). Machine never shuts down.

In Application logs there are always these 4 events when machine is unsuccessfully shutting down:

1. 6005: The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
2. 4627: The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher  and subscriber .  The subscriber failed to respond within 180 seconds. The display name of the subscription is "ISensLogon2". The HRESULT was 80010002.
3. 6006: The winlogon notification subscriber <Sens> took 180 second(s) to handle the notification event (Logoff).
4. 6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logoff).

Sens is timed out after 3 minutes while there is no 6006 event for GPClient and machine is stuck there for ages (Please wait for the group policy client). I noticed in System logs that before machine hangs during shutting down procedure there are these errors and warnings:

• 5783: The session setup to the Windows NT or Windows 2000 Domain Controller \server for the domain X is not responsive.  The current RPC call from Netlogon on \machine to \server has been cancelled.
• 1014: Name resolution for the name server timed out after none of the configured DNS servers responded.
• 131: NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC).

There is more 1014 events for different servers and few 131 events. 5783 is always just one.

I made a group policy log because I thought I will be able to see where machine stuck. Below you can see part of GPSVC log when machine is unsuccessfully shutting down:

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe58

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls

GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(438.1a04) 21:31:24:327 Waiting for user group policy thread to terminate.

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe10

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls

GPSVC(218.c88) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525

GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls

GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xdcc

GPSVC(218.1054) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0x20cc

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xd90

GPSVC(218.1054) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2d4.1cfc) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(218.d48) 21:31:24:342 Client_CompleteNotificationCall: failed with 0x525

GPSVC(218.d48) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317

GPSVC(218.1c04) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525

GPSVC(218.1c04) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317

GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x2100

GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x1264

GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

I excluded 1 machine from GP and left it on VPN for a few hours, several times. It always shuts down successfully.

On the other hand I tried with signing out from VPN before shutting down machine, I even switched off WiFi but machine still hung. If i tried to get GP results before shutting down machine it takes ages and it is stuck in "Getting the user name" stage. Gpupdate /force never updates policy (It stops at Updating Policy...). I tired with installing different hotfixes which did not resolve the issue.

I guess there is a DNS issues while machine is on VPN which leads that GP cannot be applied. When machine is trying to shut down it is still somehow connected. There is no issues with logon, no GP scripts applying when user is logging off, no roaming profiles.

Does anyone have same issues? All machines are Dell with Juniper NC (VPN).

Thanks