Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1027
  • Last Modified:

Windows domain logoff takes 20 minutes on Windows Vista

Hi,

I've got a DC setup at this location and Windows Vista Ultimate x86 (SP1) takes appx. 20 minutes to logoff. Once the logoff process completes, the machine shuts down quickly as normal.

I have no logoff scripts. Folder redirection and roaming profiles are enabled.

Any idea what's going on?
0
Pugglewuggle
Asked:
Pugglewuggle
  • 9
  • 6
1 Solution
 
McKnifeCommented:
Did you make sure it's not the case when logged on locally? Do so. If it ain't, unjoin from the domain, retry and rejoin. You can also try logging with MS procmon, quote:
--
Boot Logging
Process Monitor can log activity from a point very early in the boot process during the initialization of boot-start device drivers. Configure Process Monitor to log the next boot by selecting Enable Boot Logging from the Options menu. Process Monitor's driver will log activity at the next boot into a file in the %Windir% directory and will continue logging through the shutdown or until you run Process Monitor again.
--
You see, it can also log the shutdown process.
0
 
PugglewuggleAuthor Commented:
Hi,

Sorry about the slow response - I've been busy.

I took the computer off the domain and then rejoined it. No difference.

With the computer off the network, however, the shutdown was normal, taking about 1 minute total to logoff and shutdown.

Any ideas?
0
 
eatmeimadanishCommented:
A couple of things could cause this issue.  One is improper setup of DNS records.  Does the computer take a long time logging in? In any case make sure that on the workstation it does not have any internet DNS records and is only pointing to the Domain Controller.  Does the event log show any error messages or warnings?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
PugglewuggleAuthor Commented:
Hi, thanks for responding. Login time is normal. No issue there. The only DNS record on the PC is the one for the DC - I actually checked that already.

There are no errors for the DNS service, but the Application log shows a lot of the following, but I don't know if this is related or not...

I appreciate any help!
Event Type:	Error
Event Source:	Userenv
Event Category:	None
Event ID:	1054
Date:		6/30/2008
Time:		11:44:45 PM
User:		NT AUTHORITY\SYSTEM
Computer:	SERVER_NAME
Description:
Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted. 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
 
eatmeimadanishCommented:
http://www.eventid.net/display.asp?eventid=1054&eventno=1393&source=Userenv&phase=1

There is some good content in that thread.  It looks like the client is not actually talking to the DC properly.  Can you nslookup the DC and ping its FQDN?
0
 
PugglewuggleAuthor Commented:
That's interesting... here is the nslookup and ping from the client machine... it looks like it's showing two NS records for the same IP, but one is unknown... I wonder what that means. The ping works fine.

That is a lot on info on that error, but I couldn't really gather anything useful from it... sounds like a lot of people are getting it though.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
 
C:\Users\xxx.xxx>ping dc.xxx.com
 
Pinging dc.xxx.com [10.10.10.254] with 32 bytes of data:
Reply from 10.10.10.254: bytes=32 time<1ms TTL=128
Reply from 10.10.10.254: bytes=32 time<1ms TTL=128
Reply from 10.10.10.254: bytes=32 time<1ms TTL=128
Reply from 10.10.10.254: bytes=32 time<1ms TTL=128
 
Ping statistics for 10.10.10.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
C:\Users\xxx.xxx>nslookup dc.xxx.com
Server:  UnKnown
Address:  10.10.10.254
 
Name:    dc.xxx.com
Address:  10.10.10.254
 
 
C:\Users\xxx.xxx>

Open in new window

0
 
eatmeimadanishCommented:
When you use NSLOOKUP the first entry is the domain server it is communicating with, the second entry is the machine name IP that the DNS record contains.  What I see here is that you are not talking to the DC properly, which means your reverse lookup is not setup properly.  Add a PTR record for your Domain Server in DNS.  
0
 
PugglewuggleAuthor Commented:
Okay, I added the PTR record and a reverse lookup zone and NSLOOKUP now displays both IP addresses with the correct lookup.

I restarted the server and then restarted the computer a few times. Same issue. Takes forever to logoff... any ideas as to what's going on?
0
 
eatmeimadanishCommented:
Have you tried rejoining the machine to the domain?
0
 
PugglewuggleAuthor Commented:
Yes I have. In fact, I'm currently installing a new DC with Server 2008 on it, so I'll try that and see if that solves this crazy problem.
0
 
eatmeimadanishCommented:
I was also going to suggest you check your DHCP settings to make sure it is pushing the right network setup.
0
 
PugglewuggleAuthor Commented:
The client has a static address with correctly defined WINS, DNS, and all other values.
0
 
PugglewuggleAuthor Commented:
Anybody have any ideas?
0
 
eatmeimadanishCommented:
Are you still getting the DNS event log warnings?
0
 
PugglewuggleAuthor Commented:
Let me check when I get back. I have the WS 2008 server in place but haven't transferred the domain stuff yet.
0
 
PugglewuggleAuthor Commented:
Okay, now that I have WS 2003 running as a VM on Windows Server 2008, the logoff/shutdown process takes no longer than 45 seconds. I don't really understand why as nothing was changed except virtual hardware. Oh well... It works! I appreciate the input and thanks for the help!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now