Re: Terminal Services Access Painfully Slow
- From: "Barule Technologies" <toakes@xxxxxxxxx>
- Date: 24 Jan 2007 18:34:05 -0800
Resolution appeared to help; I ran it from a desktop at home with
800x600 16-bit color, and the access was pretty smooth, first try.
Still have to deal with the daily failure of MSSBSSSR - I know how to
fix it, just haven't had time. Could this be playing a role at all?
Thanks.
-Tim
On Jan 23, 3:18 pm, "SuperGumby [SBS MVP]" <n...@xxxxxxxxxxx> wrote:
drop the lappy to 800*600 (or maybe 1024*768)
"Barule Technologies" <toa...@xxxxxxxxx> wrote in messagenews:1169579232.293126.311210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You mean lower resolution on my laptop, or on the TS Session?
-Tim
Cris Hanna [SBS-MVP] wrote:
Your video setting on the local maybe overdriving the server settings
Try lower resolution
--
Cris Hanna [SBS-MVP]
------------------------------
Please do not contact me directly, only respond in the Newsgroups
MVPs do not work for Microsoft
------------------------------
Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2
<toa...@xxxxxxxxx> wrote in message
news:1169222047.545386.254110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- Terminal Services Access Painfully Slow
- From: toakes
- Re: Terminal Services Access Painfully Slow
- From: Cris Hanna [SBS-MVP]
- Re: Terminal Services Access Painfully Slow
- From: Barule Technologies
- Re: Terminal Services Access Painfully Slow
- From: SuperGumby [SBS MVP]
- Terminal Services Access Painfully Slow
- Prev by Date: Re: RWW and RDP issue
- Next by Date: Re: Considering SBS Over Full Product Versions
- Previous by thread: Re: Terminal Services Access Painfully Slow
- Next by thread: SBS 2003 low disk space
- Index(es):
Relevant Pages
|
