Problem using portmapper with Remote Desktop

[David_NL]

Hi,

Here's my problem: I'm trying to take over PC1 from PC2 by using a
portmapper on PC1.

I'm using a portmapper that listens on localhost port 5100 (on PC1).
If a connection has been established it sends all incoming data to
127.0.0.2 port 3389 (RDP port) and all data comming back from 3389 is
send back to the other side (PC2).

If i use 'Remote Desktop' (mstsc.exe) on PC2 and connect to port 5100 on
PC1 i get the Windows logon screen from PC2.
This means the portmapper actually works untill now.

BUT when i login on the RDP session (enter username + password -> OK),
PC1 freezes (black sreen) and after 30 seconds i get a timeout on the
'Remote Desktop' client on PC2.
After 5 minutes PC1 wakes up again and i get the logon screen.

I've tested a similar situation where i use a SSH server on PC2 and a
SSH client on PC1 to encrypt the data send over the network (using the
portmapping function in the ssh client).

If i login to the SSH session on PC1 and then open the 'Remote Desktop'
connection on PC2 i get the 'Windows logon screen'.
After i login to windows -> RDP session on PC2 gets a timeout and PC1
freezes for about 5 minutes.... thats the same problem i have when using
the portmapper.

Is this some limitation in the Windows RDP service ?? You can't use a
portmapper on the PC you want to take over ??

Thanks for any help/tips,

Regards, David.