Remote Desktop Connection - Fatal Error (Error Code: 5)

[NT]

Tried to work this one out but it beats me. Nothing on microsoft kb that i
can find nor in the posts here back to June. One guy on google has
experienced same problem but with different set up...
http://jo-san.it/blogs/coltk/archive/2006/05/17/Remote_Desktop_Connection_Trick.aspx
his workaround doesn't work for me.

So what have I got set up? 1 PC and 2 laptops, all running XP Pro, all Wi-Fi
connected via a linksys Access Point/ADSL modem/Router. They are all part of
the same workgroup and this is a LAN (all 3 are at home) not a WAN issue I
believe. I can run RDC client on any of the 3 and the server side works on
both the laptops (i.e. I can connect to either of them from the PC or other
laptop).

However, I can no longer connect to the PC from either of the laptops using
RDC (it worked fine about 6 months ago) without getting this error:
Fatal Error (Error Code: 5)
The session will be disconnected. Your computer may be low on memory. After
closing some applications, try to reconnect the session.

The error is produced after the password is entered. However anything such
as typing or mouse movements inside the RDC window is slow prior to entering
the password. It seems like the connection is slow but using non-RDC
connections I can access documents, etc on the PC from the laptops via the
LAN without a problem.

The PC is the most powerful of the 3 with 1GB of memory and an ATI RADEON
PRO 9800 graphics card with the latest drivers. I am running Norton Internet
Security on all 3 but have tried without it running, including with
firewalls disabled.

Possibilities I have considered but not with any success are: I have a
corrupted RDC server install on my PC; my graphics card which has been
replaced recently is no longer working with RDC; my network or firewall or
user settings on the PC are causing the problem. Have looked at all of them
but no luck! Have also looked in the Event Viewer on the laptop (local
client) - nothing stands out. In the Event Viewer on the PC there are a few
more interesting warnings/errors but they are not easy to tie in with
attempts to access via RDC..

 

[NT]

Is this one for the too difficult pile?!

 

[acoroian]

I have the same problem and have found no fix for it. But there is a
workaround. Some guy in some forum (dont remeber where it was) said
that if you open a secondary RDP window while you still have the first
one trying to connect it will connect even though the first one you
open will give u the error code 5.

Post back if it works for you.

 

[NT]

Thanks for your reply.

No luck I am afraid. Still not getting a connection, even with a second RDC
window. I get a different error messages on the second connection either it
says it has 'timed out' or 'the client could not establish a connection to
the remote computer'.

Both are strange given that not using RDC I can see the computer fine and
access it without hassle.

Just to eliminate the client as an issue I have tried this from more than 1
laptop. I have also tried it laptop to laptop - both work fine.

Any other suggestions?? I ideally would like to 're-install the server side
app that picks up the RDC request but do not have a clear idea of all the
steps. With a clean install I reckon it might be problem solved - it did
work in the past so something has stopped it working.

Let me know your thoughts!

NT.