I'm not sure if it's a right place to ask but let's see what happens ...
I have a local remote desktop pc [him] who is listening on its default local port of what ever ...
I don't want and can't make a nat in the organization public router. [this will get the job done, I know]
I need the local remote desktop connection to stay connected to my VPS [her] who is being served with a public address
this part is @client{[rdp listening port] <==connects on demand== [client's application] ==stay connected to server at certain port====> }
this part is @server { =public open port== [public socket who is always in a hand shake with the client] <=== "redirected terrific from other public listening port, this part is ok I can do it"}
I have used a program named Zebedee for port forwarding this is a very small cool app that forwards our terrific between ports, I can install a server on her and client on him then every time you connect to his local port it will redirect that terrific to the remote server, compressed and encripted
but how to do it wise verse? install a server of an always connected app on the client and make a connection to RDP local port on the other side it stays connected to the server at all time ????
so when some one connects to the server at port X the server connects the terrific to a dynamic IP computer client hosting Remote desktop connection
and when I connect to the server it's simple, it just route two local ports

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic