Takes a long time to login to Windows 2008 Terminal Server

Make sure you have the mosted updated NIC driver installed on the system. Can you post a ipconfig /all.

Try using the Servers IP address instead of the computer name to connect via RDP as well and see if that goes any faster for you.  Could be DNS issue

Here is another post that I was involved with.

https://www.experts-exchange.com/questions/23802534/Windows-Server-2008-Long-Boot-Time-The-winlogon-notification-subscriber-GPClient-took-505-second-s-to-handle-the-notification-event-CreateSession.html

Yes I am using RDP to connect to the Server (using the ip address rather than the CN)... and even after removing  all the checks from the settings in Remote Desktop Connection preferences "Experience" tab...It still takes 120 seconds to login without any time outs or errors.


I havent updated any firmware on the NIC cards, but here are the ipconfig results:
********************************************************************************************************************
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.CIU>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : x-TS1
   Primary Dns Suffix  . . . . . . . : x.Local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : x.Local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Ad
apter #2
   Physical Address. . . . . . . . . : 00-23-7D-A0-26-2A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::359b:bf08:324f:8009%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.66.29(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.66.1
   DNS Servers . . . . . . . . . . . : 192.168.66.25
                                       192.168.66.26
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{8336035E-76B2-498C-9609-B30A07589
ABE}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
********************************************************************************************************************

Disable IPv6. Also, go into your properties of your Local Area Connection click configure then click the Advance Tab. Look for TCP Checksum, IP Checkcum, TCP Offload, IP Offload disable these if they are enabled and see if they help.

Update the firmware and drivers.

If it's 120 seconds exactly sounds like a timeout on a service or something similar.  

This isn't your exact problem but it maybe it may help out...

http://www.symantec.com/connect/forums/cant-rdp-server-2003-server-w-endpoint-protection-manager-11xx-installed

Also found this in another post...

https://www.experts-exchange.com/questions/23687746/Remote-Desktop-Connection-Slow-to-Establish-Initial-Connection-Normal-After-Login.html

I disable IPv6 by removing the tick, but in the advanced tab here is what I have (see attched)

Thanks
nic.bmp

IP Checksum disable
IP Large Send Offload Disable

So just to be clear I need to set >
IPv4 Checksum Offload to "None"
IPv4 Large Send Offload to "Disable"

Yes.

Thanks dariusg, I logged on and off and it still takes long to login

Re-enable those and make sure you update the drivers and firmware. Can you post the Event ID that you are getting?

dariusg, I am in the process of running the driver and firmware updates... I will post you the Event ID shortly after the updates have completed - Thanks Glen

After the Firmware updates I logged off and back on ... it still took 120 Seconds....

Here are some Event ID's from the Application Log in order
9003
6006
6005
1
4101
9009

Check this out.

http://www.eventid.net/display.asp?eventid=9009&eventno=10141&source=Desktop%20Window%20Manager&phase=1

http://technet.microsoft.com/en-us/library/cc756372.aspx

http://social.technet.microsoft.com/Forums/en-US/itprovistanetworking/thread/56310e15-32df-457a-bc38-4cc2fce0a5e5/

I think that this issues could perhaps be related to the AD on the Domain Controller..

I tried logging straight onto the console (not via RD) and it still took approx 120  seconds to login using the Administrator account.

........Any ideas?

 

Can you run a netdiag on the DC?

I downloaded the Network Diagnostics Tool (Netdiag.exe) - But am not sure how to run it, or use it?

(( Sorry ))

Go to the command prompt then run netdiag but you are running 2008 so I don't think it will run. I have gotten it to run on 2008 before but sometimes it doesn't. I meant for you to run a dcdiag on the system unless your DC is a 2003 server. What verison is your DC running?

It is 2003...  I tried running it from a command prompt but it didnt work.

Do you have the support tools installed?

http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&displaylang=en

I get an error 1311 when I try to install it

error attached
temp.bmp

Did you save to your desktop then run the setup?

yeah, thats what I did

Re-download the software and save it to your c: drive.

Its very strange- same thing

That is strange.

You are downloading and installing on your 2003 Server?

Yes.