Remote Desktop Service not behaving properly but no error

  • Thread starter Thread starter KitKatNeko
  • Start date Start date
K

KitKatNeko

Hi.
I have 2 XP SP2 clients trying to connect using RDP.
Connecting Client uses RDC v6 and/or 5.1
Serving client uses the default TermServices (5.1)

RDC is enabled on serving client
Ports are open and listening, communication is ok

When trying to remotely log in into serving client, nothing happens. Hitting
connect does nothing and return to RDC connexion dialog without error
messages (nor visual or in the event log)

I have checked settings for RDC and nothing seems wrong...

fdenytsconnections is 0
TSEnabled is 0
TCP port 3389 (unknown service): LISTENING
portqry.exe -n servingclient -e 3389 -p TCP exits with return code 0x00000000

I have read that it maybe due to .NET 3 or SP3 but none of those are
installed...

This said, rebooting seems to correct the error but then it will occur again
later on.

Any comment or help will be appreciated.
 
Yes I can telnet and so does portquery and telnet show connectivity is ok.
As a matter of fact as stated previously, after a reboot I am able to use
RDC, but it seems after a while the services is not behaving properly.
 
As stated previously, "dialog without error messages (nor visual or in the
event log) "..no error message in the event log of both machines.
 
I am having this same problem. i can telnet to 3389, but when trying to RDP
in it will not work. NO message, no events, no nothing. Appears to try for
a second or 2 then stops
 
I was experiancing a similar problem, although it was working once if I
rebooted the system. Having used the RDC for a few years without issue, the
suspect for the cause of the problem was the graphics driver as I had updated
it recently. After downgrading from Nvidia Forceware 178.24 to 93.71 the
issue appears to have resolved itself.

Nick
 
I have came across a couple of things that point to KB957097 causing problems
with TS. Might be something for you guys to check into.
 
this sounded like a good lead.
After removing the KB and restarting this desktop I am still experiencing
the same issue.
 
Back
Top