Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Tech-Archive recommends: Fix windows errors by optimizing your registry

It has always been a problem with this server ( Dell PowerEdge 1600SC )
when it ran Windows 2003 Ent. no SP, SP1, and now SP2. It has been a
problem with the previous version of mstsc.exe client (5.x) as well as the
current version (6.x) This problem is the main reason I installed a Dell
DRAC controller card in the server so I have the ability to reboot it when
the RDP console connection fails.

EventLog is mostly loaded with TermServDevices errors relating to missing
printer drivers when the client connects. I can't really see anything in
the log at the specific moment the client attempt to connect and fails.

The onboard video is ATI RAGE XL PCI with a driver version 5.10.2600.6014,
and according to Device Manager > Update Driver is the latest version
available.

-- Paul



"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns99B6D4B2DC217veranoesthemutforsse@xxxxxxxxxxxxxxxx
That's correct, you can't restart the terminal Services service.
I don't think that that's the problem either, since you can connect
and login.

Has this always been a problem with this server? If not, was
something changed directly before the start of the problem?
Which SP is the server running?
Any warnings or errors in the EventLog on the server when this
happens?
Similar problems are sometimes reported with certain video drivers
on the server. Updated yours lately?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Paul" <paule@xxxxxxxxxxxxxxxxxxxxx> wrote on 25 sep 2007 in
microsoft.public.windows.terminal_services:

When I remote desktop into my Windows 2003 Server from Windows
XP Pro, I enter my username and password into the local remote
desktop dialog. The connection is established to the server.
Screen goes black for a second like it's about to succeed, then
bounces back out to the local username/password dialog. The
only cure for this is to reboot the server. This doesn't happen
often but it does seem to happen after a remote desktop
connection over a poor/flaky/slow internet connection, like the
server side remote desktop process gets confused by junk packets
and never recovers.

Is it possible to just restart "remote desktop service" without
rebooting the whole server? I thought I read somewhere this
isn't possible because "remote desktop" is integrated too deeply
into the OS ?

-- Paul



.

Relevant Pages

  • [2.6.30.1] Significant latency playing video file from NFS4 share
    ... No significant other processes running on either the client or the ... latencytop on the server does not show any significant latencies. ... # CPUFreq processor drivers ... # Core Netfilter Configuration ...
    (Linux-Kernel)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • Re: Client behind a firewall!
    ... Microsoft MVP - Terminal Server ... Internet with Remote Desktop enabled when I'm at work, ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)