Home > Win Xp > Win Xp - 2000 Domain Slow Logon

Win Xp - 2000 Domain Slow Logon

Basically the data output is the same as the output from the above KB article once it is converted from the binary output. Send me notifications when members answer or reply to this question. We'll email youwhen relevant content isadded and updated. Once I enable the Home Folder for the user account I am testing with, the logon to a usable desktop takes approx. 30-35 seconds. Check This Out

by R. More reading here! On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone (".") present on the It was only recently that we decided that as it was no longer needed they could be shut down and that’s where the problems started. http://www.cnet.com/forums/discussions/slow-logon-in-windows-2000-domain-96463/

I havent been able to find any documentation outlining why the delay occurs. Related Articles Get rid of IM and no slow OE startup Slow network access not always due to Scheduled tasks check Very Slow boot when networking Shutdown XP using your keyboard! President 05-13-2005, 12:10 PM #5 scuzz Registered Member Join Date: Apr 2005 Posts: 14 OS: XP No sir. 05-13-2005, 02:22 PM #6 Skooter Registered Member Join the community here, it only takes a minute.

By submitting you agree to receive email from TechTarget and its partners. Please try again later. You will have to reboot several times during this process to be confident that you have discovered the cause. Wednesday, September 14, 2011 8:55 PM Reply | Quote Answers 0 Sign in to vote Just thought I would post to explain what this turned out to be, it was

Marked as answer by BocaIT Thursday, September 15, 2011 10:34 AM Unmarked as answer by BocaIT Friday, September 16, 2011 8:27 AM Thursday, September 15, 2011 2:26 AM Reply | Quote Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced It is EXTREMELY slow. Thanks again for you help The group Policy settings was, User configuration->Administrative Templates->Desktop->Desktop Wallpaper Marked as answer by BocaIT Friday, September 16, 2011 2:05 PM Edited by BocaIT Tuesday, September

You must always configure the DNS client settings on each domain controller's network interface to use the alternative DNS server addresses in addition to the primary DNS server address. Get the answer AnonymousFeb 17, 2005, 12:23 AM Archived from groups: microsoft.public.win2000.active_directory (More info?)Thanks, I'll try that!barry wrote:> amitos wrote:> > Hi!> >> >> > I am having a longstanding problem Check that the Active Directory is functioning properly. Check that the Active Directory is functioning properly and repeatenumeration of the zone.

Answer: Check for a disjointed namespace, and then run Netdiag.exe /fix. https://blogs.technet.microsoft.com/askds/2009/09/24/so-you-have-a-slow-logon-part-2/ Test and see if the boot time is the same or not. We do however have some production scenarios in which we do have home folders with romaing profiles and this information will be beneficial for those cases. UDP and TCP Port 53 should be open on the proxy server or firewall.

Bob Drake 7 years ago Geemail_1 Bob, Thank you for the reply. http://yellowproductions.net/win-xp/win-xp-logon-screen-unread-mail-messages.php However, such will take much longer than a wired connection. In most environments there will be numerous policies applied, so how do you rule them out as being an issue? Ensure the win2k server points to itself as a DNS server using 127.0.0.1 as the DNS address. 3.

Question: What should I do if the domain controller points to itself for DNS, but the SRV records still do not appear in the zone? Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Home > Forums > Desktop Software > PC Operating Systems In Windows Server 2003, the recommended DNS configuration is to configure the DNS client settings on all DNS servers to use themselves as their own primary DNS server, and to use http://yellowproductions.net/win-xp/win-xp-novell-netware-domain-controller-problem.php Other Windows 2000-based and Windows Server 2003-based computers do not query WINS to find Active Directory-related information.

NOTE: Some antivirus applications will still load filter level drivers even though their services are disabled from starting with MSCONFIG. AnonymousFeb 9, 2005, 3:36 PM Archived from groups: microsoft.public.win2000.active_directory (More info?)Hi!I am having a longstanding problem with XP Pro clients trying to logonto windows 2003 domain controller. This is the state of the art.To wit, I'd take this issue to your IT staff and ask them to fix it or fire them.

Ensure DNS server on win2k is configured to permit dynamic updates.

Join thousands of tech enthusiasts and participate. Question: If I remove the ISP's DNS server settings from the domain controller, how does it resolve names such as Microsoft.com on the Internet? All went well however whenever I shutdown the 2003 (Old DC now member server) XP users experience really slow login (20 mins) when I power back on the old 2003 server Can you share whichGPO setting it was and how it was configured regarding a "desktop image?" It may benefit others having a similar problem.

Lucky for me one of my co-workers has already written a blog on how to interpret the output (find more in his two part section: Section 1 Section 2). Answer: The most common mistakes are: • The domain controller is not pointing to itself for DNS resolution on all network interfaces. • The "." zone exists under forward lookup zones This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. navigate here We'll send you an e-mail containing your password.

This is done by selecting the “Link an Existing GPO” as seen in above picture. We'll email youwhen relevant content isadded and updated. In Windows Server 2003, the recommended DNS configuration is to configure the DNS client settings on all DNS servers to use themselves as their own primary DNS server, and to use Thank you, AceAce Fekay MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer

Answer: A Windows 2000 or Windows Server 2003 domain controller does not register Active Directory-related information with a WINS server; it only registers this information with a DNS server that supports You enable the network capture utility from one and filter for the other’s IP address. And you can't just "shutdown" a DC. This can be accomplished by monitoring the computer with another computer that is plugged in to the same hub or switch (port mirroring).

DNS servers along with other hardware (like switches, routers) could also be the source of the problem.