Terminal Services Access Painfully Slow

Any help would be appreciated, as I'm starting to drive the users
nuts... :)
I've got a small SBS 2003 R2 Premium network, 20 PCs plus the SBS
Server. It's an in-place upgrade of a SBS 2000 Server.
I would say 90% of the time when I access the server via Terminal
Services from outside the office (I'm the IT Admin, like to check
backup results, add users remotely, etc.), the session will connect,
and begin to display the desktop, but won't ever finish displaying the
desktop. Sometimes I will see the start bar, other times I will just
see some blocks of color on the screen, which I know to be open
windows, dialog boxes, etc. I usually have to Disconnect the session
(hitting the "X" on the tab at the top), waiting a couple of minutes
(it won't let me back in any sooner), and then reconnecting. On the
subsequent reconnect, things work fine.
What becomes a bigger issue is that the server has a tendency to choke
when I first access it, which of course interrupts client activity.
Exchange will often report that it's disconnected from the Outlook 2003
client in Cached Mode, print jobs may fail, document save attempts may
fail, etc. This is where the users are getting impatient, which I can
appreciate.
I have the issue with the Microsoft Monitoring Components not working
right, and have not yet uninstalled and reinstalled them, but I don't
imagine that this is the source of this issue.
Oh, I use Console Mode (mstsc /console) when accessing the box
remotely. On this topic, was it just my strange luck, or did Microsoft
finally provide a true "Console Mode" with R2? That is, in using
console mode in prior versions of Windows and SBS, I would never get a
true look at the console, and the apps that were running. Since R2,
whatever I left open on the desktop of the server is displayed to me
when I connect with Console Mode.
Sorry for the tangent there, but I have a few networks that I manage,
and this is the only one that chokes with this activity. Other networks
that I access using TS Console Mode work wonderfully.
TIA for the help.

-Tim

.

Relevant Pages

  • Re: May need to move from SBS because of connection issues
    ... After you removed ISA from the server did you remove the client from the workstation and the notebook? ... You did say you could connect to other SBS networks, as well as your own, with the notebook if you took it to your home or to say *$'s. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 Consulting
    ... I also found the suggestion to use hardware solutions for those server ... 20 networks per admin -- thanks for the estimate. ... > There are a couple of approaches to managing multiple SBS networks. ... >>> yet the people who are your Techs Couldn't answer these questions? ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services Access Painfully Slow
    ... Try lower resolution ... I've got a small SBS 2003 R2 Premium network, ... It's an in-place upgrade of a SBS 2000 Server. ... I use Console Mode when accessing the box ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 - No Internet Access/Outlook 2000 slow from Some Win98 Clients
    ... ISA or Basic Firewall logically sits - between these subnets. ... Server NIC ... Les Connor [SBS MVP] ... When you say that the internal and external networks should ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services Access Painfully Slow
    ... You mean lower resolution on my laptop, or on the TS Session? ... I've got a small SBS 2003 R2 Premium network, ... It's an in-place upgrade of a SBS 2000 Server. ... I use Console Mode when accessing the box ...
    (microsoft.public.windows.server.sbs)