Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RDP login problems with 2K3 server

0 views
Skip to first unread message

Jason Camp

unread,
Mar 23, 2007, 1:15:47 PM3/23/07
to
I've noticed an issue with two of my Windows 2003 Servers where I am unable
to login using RDP. I do not have the full blown Terminal Services installed
as we are not licensed. I have Remote Desktop enabled but occassionally am
unable to login.

Is there a way to uninstall reinstall the RDP componet?

Can I script something to band aid the problem?

I understand the TermService does not respond to net stop/start.

I've also played around with the qwinsta and rwinsta commands. The only
thing that seems to resolve the problem is a full restart.

Any suggestions are greatly appreciated.


Dragos CAMARA

unread,
Mar 23, 2007, 2:24:23 PM3/23/07
to
hi,
what mstsc version do you use and what error message do you have when you
try to connect?
--
Dragos CAMARA
MCSA Windows 2003 server

Jason Camp

unread,
Mar 23, 2007, 2:48:05 PM3/23/07
to
I am using windows XP. Is that the 5.2 client?

I do not get a specific error. It looks as if it is going to connect. I see
the server window come up but I never get a login prompt.


"Dragos CAMARA" <drag...@remove-this.hotmail.com> wrote in message
news:0C2EE824-7B91-4330...@microsoft.com...

Vera Noest [MVP]

unread,
Mar 23, 2007, 3:55:22 PM3/23/07
to
Windows XP's rdp client is version 5.2.x, yes, but it is possible
that you have installed rdp 6.0 from Windows Update. Could you
please verify which version you have? I've seen one identical
report with rdp client 6.0, and it's important to identify the
exact version.

Open your rdp client, click on the small icon at the left upper
side in the title bar, then click "About".
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Jason Camp" <jc...@absolute-performance.com> wrote on 23 mar 2007
in microsoft.public.windows.terminal_services:

Jason Camp

unread,
Mar 23, 2007, 4:14:28 PM3/23/07
to
I use version 5.1

"Vera Noest [MVP]" <vera....@remove-this.hem.utfors.se> wrote in message
news:Xns98FCD4D6EC8Cve...@207.46.248.16...

Vera Noest [MVP]

unread,
Mar 23, 2007, 4:32:01 PM3/23/07
to
OK, thanks for checking that. And yes, I made a mistake there, XP's
standard client is 5.1.
So now we know that it's not a problem with the 6.0 client, let's
try to find a solution:

I understand that this happens with 2 servers, but you can
sucesfully logon to other servers, is that correct?
Is there anything in the EventLog on the servers?
If you just leave the client after trying to connect, does it
eventually give you the logon screen, or does it time out, or does
it sit there indefinitively?
What is the main function of these servers? Is it possible that
they are overloaded?
When this happens, can you still logon to the physical console of
the server? If you can, can you connect with rdp to the server from
the server itself? Can you connect to a shared drive on the server
from the client?

Jason Camp

unread,
Mar 23, 2007, 5:32:53 PM3/23/07
to
Yes I can successfully log onto other 2k3 servers on the same network. There
is nothing in the event log worth noting. These are SQL servers under
minimal load. When I notice the problem I can let the RDP window sit for 10
plus minutes without seeing a login screen. I eventually just close the
connection. Yes I can still get to the console. Give me a day or two to find
the other information (RDP to itself, and accessing a shared drive).

Thank you very much for your help!

"Vera Noest [MVP]" <vera....@remove-this.hem.utfors.se> wrote in message

news:Xns98FCDB0BC3A29ve...@207.46.248.16...

Jason Camp

unread,
Apr 2, 2007, 4:29:21 PM4/2/07
to
My post is to large. If anyone is interested in screen grabs please let me
know.


I'm noticing problems again today. Below are more answers to previously
asked questions.

Attached is a screen grab from a remote server (term service probs.jpg). I
reset the connections on the problem server remotly using the
qwinsta/rwinsta commands.

After the connections were reset I try to RDP to the server and it just
hangs. There is an RDP window open but I never get a login prompt. It's been
in this state for 30 + mins.

I CAN access network shares on the problem server through the Run line.

I then console into the server and attempt to reset the connections from
there. Error is attached (term service console reset.jpg)

Using the console I am unable to RDP to the the server itself. Same
symptoms. The connection just hangs without a login window.


"Jason Camp" <jc...@absolute-performance.com> wrote in message
news:%23Rs1QLZ...@TK2MSFTNGP04.phx.gbl...

Vera Noest [MVP]

unread,
Apr 3, 2007, 8:34:01 AM4/3/07
to
[Best way to make screeen dumps available for readers is to put
them on a webserver and post the URL]

Since you can't even connect with rdp from the server's console to
the server itself, your problem is located in the server itself.
I would delete the rdp-tcp connection and recreate it (in TS
Configuration, right-click on Connections - Create new connection).
If that doesn't help, a call to Microsoft Support would be my next
step.

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

"Jason Camp" <jc...@absolute-performance.com> wrote on 02 apr 2007
in microsoft.public.windows.terminal_services:

0 new messages