Results 1 to 3 of 3

Thread: Slow logon with XP on Windows 2003 Server AD

  1. #1
    Join Date
    Nov 2005
    Posts
    17

    Slow logon with XP on Windows 2003 Server AD

    HI, Before I ask my question, let tell you more about my situation. I’m running a new DELL Server with 2003 Standard Edition upgraded to DC + DNS Server (no DHCP, router does it). And as client workstations I’m using DELL XP pro SP2 Laptop (D510) with McAfee Internet Security. Other information related to these setup is as follows:
    Server
    First DNS = server IP
    2nd DNS = none
    Laptop
    IP Address is via DHCP
    First DNS = server IP
    2nd DNS= none
    For the ISP DNS, I have created a forwarder.

    I have configured both of these devices in my own network (192.168.10.xx) and I did not noticed any slow logon. Then I have brought both machines by my customer (Server IP changed to 10.9.156.xx) and since this time the logon takes about 4 minutes (no server profile).

    There are also some Event IDs listed in my Event Viewer which is as follows:

    Event number 1030:
    Querying the list of group policy objects failed. Such a failure has been already found in Policy module.

    Event number 1006:
    It was not possible to connect to domain GRIMM.local (timeout). Processing Group policy has been aborted.


    As per my experience, I’m sure that there would be something messing up I the policies but I have no idea what exactly I should start from. Hence, need you guys help.

  2. #2
    Join Date
    Jan 2006
    Posts
    3,792

    Re: Slow logon with XP on Windows 2003 Server AD

    Hello,Big Fish

    I cannot trace the problem as per the information you provided. Hence will suggest you to Run a "tracert IP_OF_YOUR_DC -d" on a PC and post results.After this, also try running"dcdiag /c" on your domain controller and post results.

  3. #3
    Join Date
    Oct 2004
    Posts
    1,342

    Re: Slow logon with XP on Windows 2003 Server AD

    Hey guys, as far as I know Event ID 1030 and 1006 occurs when UDP packets gets dropped when your client workstation authenticates with the server using Kerberos. Many times if we force Kerberos to use TCP instead of UDP as per article M244747, it use to work fine. So you should try out the same as well. If you don’t know how to it, just follow the below steps:

    1. Start Registry Editor.
    2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters.
    Note If the Parameters key does not exist, create it now.
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. Type MaxPacketSize, and then press ENTER.
    5. Double-click MaxPacketSize, type 1 in the Value data box, click to select the Decimal option, and then click OK.
    6. Quit Registry Editor.
    7. Restart your computer.

    I don't quite understand why other PCs don't need that, but it works...

Similar Threads

  1. Slow Responses/ Windows Server 2003
    By Erasmo in forum Windows Server Help
    Replies: 7
    Last Post: 23-11-2010, 01:14 AM
  2. Replies: 5
    Last Post: 20-08-2010, 11:07 PM
  3. Replies: 5
    Last Post: 19-03-2010, 01:17 AM
  4. Windows 2003 Server Slow Network Throughput
    By drew.flint@gmail.com in forum Windows Server Help
    Replies: 3
    Last Post: 06-05-2008, 08:31 PM
  5. Vista is VERY Slow with Remote Desktop to Windows 2003 server
    By counselor in forum Windows Vista Network
    Replies: 4
    Last Post: 16-10-2007, 08:29 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,582,476.11734 seconds with 17 queries