RDP slow to connect to 2003 Term Server.

J

Jeff

I just built a new W2K3 Term server and I'm noticing much longer RDP
connection times than on my W2K term server.

Does anyone have any idea what may cause this?

The two servers are similar models. The W2K machine has 4GB RAM, the new
server has 3.5GB RAM.

Thanks,

Jeff
 
V

Vera Noest [MVP]

Which part of the logon process takes more time?
Before you get to the login window, or after you have entered your
username and password (when the server is loading your profile)?
Which type of user profiles do you have? TS-specific profiles?
Different profiles for the W2K and the 2003 TS? Roaming or local?

You can get more info about the logn process by enabling logging:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

Interpreting Userenv log files
http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
99a5-40fd-b68a-6c1979e565a21033.mspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 10
jul 2007 in microsoft.public.windows.terminal_services:

> I just built a new W2K3 Term server and I'm noticing much longer
> RDP connection times than on my W2K term server.
>
> Does anyone have any idea what may cause this?
>
> The two servers are similar models. The W2K machine has 4GB RAM,
> the new server has 3.5GB RAM.
>
> Thanks,
>
> Jeff
 
J

Jeff

Getting to the login window is what is taking much longer. When connecting to
the W2K server it's almost instantaneous. With the new server it takes 30 -
60 seconds. (approx)

The user profiles are local on each server.

Thanks,

Jeff

"Vera Noest [MVP]" wrote:

> Which part of the logon process takes more time?
> Before you get to the login window, or after you have entered your
> username and password (when the server is loading your profile)?
> Which type of user profiles do you have? TS-specific profiles?
> Different profiles for the W2K and the 2003 TS? Roaming or local?
>
> You can get more info about the logn process by enabling logging:
>
> 221833 - How to enable user environment debug logging in retail
> builds of Windows
> http://support.microsoft.com/?kbid=221833
>
> Interpreting Userenv log files
> http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
> 99a5-40fd-b68a-6c1979e565a21033.mspx
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 10
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > I just built a new W2K3 Term server and I'm noticing much longer
> > RDP connection times than on my W2K term server.
> >
> > Does anyone have any idea what may cause this?
> >
> > The two servers are similar models. The W2K machine has 4GB RAM,
> > the new server has 3.5GB RAM.
> >
> > Thanks,
> >
> > Jeff
>
 
V

Vera Noest [MVP]

Mm, that shouldn't be the case.
Is there any difference between making a connection to the NetBIOS
name of the server and to the IP number?
Is your DNS working OK?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 11
jul 2007 in microsoft.public.windows.terminal_services:

> Getting to the login window is what is taking much longer. When
> connecting to the W2K server it's almost instantaneous. With the
> new server it takes 30 - 60 seconds. (approx)
>
> The user profiles are local on each server.
>
> Thanks,
>
> Jeff
>
> "Vera Noest [MVP]" wrote:
>
>> Which part of the logon process takes more time?
>> Before you get to the login window, or after you have entered
>> your username and password (when the server is loading your
>> profile)? Which type of user profiles do you have? TS-specific
>> profiles? Different profiles for the W2K and the 2003 TS?
>> Roaming or local?
>>
>> You can get more info about the logn process by enabling
>> logging:
>>
>> 221833 - How to enable user environment debug logging in retail
>> builds of Windows
>> http://support.microsoft.com/?kbid=221833
>>
>> Interpreting Userenv log files
>> http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
>> 99a5-40fd-b68a-6c1979e565a21033.mspx
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on
>> 10 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > I just built a new W2K3 Term server and I'm noticing much
>> > longer RDP connection times than on my W2K term server.
>> >
>> > Does anyone have any idea what may cause this?
>> >
>> > The two servers are similar models. The W2K machine has 4GB
>> > RAM, the new server has 3.5GB RAM.
>> >
>> > Thanks,
>> >
>> > Jeff
 
J

Jeff

DNS seems to be working fine. Both TS servers reside on the same subnet, but
on different domains. I will try setting up a connection via IP address
rather than NetBIOS name and see if there's a difference. I'll keep you
posted.

Thanks,

Jeff

"Vera Noest [MVP]" wrote:

> Mm, that shouldn't be the case.
> Is there any difference between making a connection to the NetBIOS
> name of the server and to the IP number?
> Is your DNS working OK?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 11
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Getting to the login window is what is taking much longer. When
> > connecting to the W2K server it's almost instantaneous. With the
> > new server it takes 30 - 60 seconds. (approx)
> >
> > The user profiles are local on each server.
> >
> > Thanks,
> >
> > Jeff
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Which part of the logon process takes more time?
> >> Before you get to the login window, or after you have entered
> >> your username and password (when the server is loading your
> >> profile)? Which type of user profiles do you have? TS-specific
> >> profiles? Different profiles for the W2K and the 2003 TS?
> >> Roaming or local?
> >>
> >> You can get more info about the logn process by enabling
> >> logging:
> >>
> >> 221833 - How to enable user environment debug logging in retail
> >> builds of Windows
> >> http://support.microsoft.com/?kbid=221833
> >>
> >> Interpreting Userenv log files
> >> http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
> >> 99a5-40fd-b68a-6c1979e565a21033.mspx
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on
> >> 10 jul 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > I just built a new W2K3 Term server and I'm noticing much
> >> > longer RDP connection times than on my W2K term server.
> >> >
> >> > Does anyone have any idea what may cause this?
> >> >
> >> > The two servers are similar models. The W2K machine has 4GB
> >> > RAM, the new server has 3.5GB RAM.
> >> >
> >> > Thanks,
> >> >
> >> > Jeff
>
 
J

Jeff

No Vista boxes in my shop. We don't have the hardware to support it. (And
probably won't have for a long time)

It's mostly thin clients running Windows CE connecting to the term servers.

Thanks,

Jeff

"ThePro" wrote:

> "Jeff" <Jeff@discussions.microsoft.com> wrote
> news:DA86A83D-56B2-4DD8-9D20-F9CA9A573D41@microsoft.com...
> >I just built a new W2K3 Term server and I'm noticing much longer RDP
> > connection times than on my W2K term server.
> >
> > Does anyone have any idea what may cause this?
> >
>
> If you client runs Vista have a look at
> http://mytechweblog.blogspot.com/2007/06/rdp-from-vista-slow-after-windows-2003.html
>
> ThePro
>
 
J

Jeff

I figured it out. Our dns server resides in the same domain that the W2K TS
server is in. I just added an A record in DNS under that domain and that sped
things up nicely.

Thanks,

Jeff

"Vera Noest [MVP]" wrote:

> Mm, that shouldn't be the case.
> Is there any difference between making a connection to the NetBIOS
> name of the server and to the IP number?
> Is your DNS working OK?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 11
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Getting to the login window is what is taking much longer. When
> > connecting to the W2K server it's almost instantaneous. With the
> > new server it takes 30 - 60 seconds. (approx)
> >
> > The user profiles are local on each server.
> >
> > Thanks,
> >
> > Jeff
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Which part of the logon process takes more time?
> >> Before you get to the login window, or after you have entered
> >> your username and password (when the server is loading your
> >> profile)? Which type of user profiles do you have? TS-specific
> >> profiles? Different profiles for the W2K and the 2003 TS?
> >> Roaming or local?
> >>
> >> You can get more info about the logn process by enabling
> >> logging:
> >>
> >> 221833 - How to enable user environment debug logging in retail
> >> builds of Windows
> >> http://support.microsoft.com/?kbid=221833
> >>
> >> Interpreting Userenv log files
> >> http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
> >> 99a5-40fd-b68a-6c1979e565a21033.mspx
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on
> >> 10 jul 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > I just built a new W2K3 Term server and I'm noticing much
> >> > longer RDP connection times than on my W2K term server.
> >> >
> >> > Does anyone have any idea what may cause this?
> >> >
> >> > The two servers are similar models. The W2K machine has 4GB
> >> > RAM, the new server has 3.5GB RAM.
> >> >
> >> > Thanks,
> >> >
> >> > Jeff
>
 
V

Vera Noest [MVP]

OK, I'm glad that your problem is solved, and thanks for reporting
the results back here!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 13
jul 2007 in microsoft.public.windows.terminal_services:

> I figured it out. Our dns server resides in the same domain that
> the W2K TS server is in. I just added an A record in DNS under
> that domain and that sped things up nicely.
>
> Thanks,
>
> Jeff
>
> "Vera Noest [MVP]" wrote:
>
>> Mm, that shouldn't be the case.
>> Is there any difference between making a connection to the
>> NetBIOS name of the server and to the IP number?
>> Is your DNS working OK?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on
>> 11 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Getting to the login window is what is taking much longer.
>> > When connecting to the W2K server it's almost instantaneous.
>> > With the new server it takes 30 - 60 seconds. (approx)
>> >
>> > The user profiles are local on each server.
>> >
>> > Thanks,
>> >
>> > Jeff
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Which part of the logon process takes more time?
>> >> Before you get to the login window, or after you have
>> >> entered your username and password (when the server is
>> >> loading your profile)? Which type of user profiles do you
>> >> have? TS-specific profiles? Different profiles for the W2K
>> >> and the 2003 TS? Roaming or local?
>> >>
>> >> You can get more info about the logn process by enabling
>> >> logging:
>> >>
>> >> 221833 - How to enable user environment debug logging in
>> >> retail builds of Windows
>> >> http://support.microsoft.com/?kbid=221833
>> >>
>> >> Interpreting Userenv log files
>> >> http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b4
>> >> 30- 99a5-40fd-b68a-6c1979e565a21033.mspx
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote
>> >> on 10 jul 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I just built a new W2K3 Term server and I'm noticing much
>> >> > longer RDP connection times than on my W2K term server.
>> >> >
>> >> > Does anyone have any idea what may cause this?
>> >> >
>> >> > The two servers are similar models. The W2K machine has
>> >> > 4GB RAM, the new server has 3.5GB RAM.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Jeff
 
You must log in or register to reply here.

Similar threads

N
RDP to Windows Server 2022
Replies
0
Views
1
Nacho_SPA
N
S
File Server running on Windows Server 2003 unable to connect via Palo Alto - Global Protect VPN.
Replies
0
Views
55
SafiAhmed
S
R
Windows Server 2025 Secured-core Server
Replies
0
Views
54
RoySasabe
R
Y
Easily enable Azure Arc on Windows Server 2022
Replies
0
Views
92
Yash_Shekar
Y
J
The Future of Windows Server Hyper-V is Bright!
Replies
0
Views
105
Jeff Woolsey
J
Back
Top Bottom