When you connect to the desktop using PocketCloud, it throws anyone else off the console (assuming it's not a Terminal Services Server) that is logged in with the same credentials.

I was able to log into my laptop running Windows 7 using PocketCloud on my iPhone. It took over the logged-in session on the laptop.

I then used my Mac to connect, using Remote Desktop Connection, and it kicked me out of PocketCloud. So it's all RDP port 3389.

As to what's happening on your router, it looks as though the PocketCloud Companion for Windows client is tunnelling a session through TCP on a different port. This makes sense, seeing that you sign in with a Gmail account.

I did a netstat -a while connected using the PocketCloud client, as well as verification through Process Monitor from SysInternals), and I found this:

192.168.0.195:1171 pb-in-f125:5222

This coincided with Process Monitor, which found that the PocketCloudService process was talking on various ports locally to a remote port of 5222. For instance (edited for brevity):

That is correct, and it is by design. What do you want to do exactly? If you port forward from the router, it will kill any existing PocketCloud connections, but that's an RDP limitation inside Windows and has nothing to do with PocketCloud.
–
user3463Jun 20 '12 at 22:44

I want to have the ability to put in my ip address into the windows remote desktop interface from my laptop away from home and connect that way
–
KiloJKiloJun 20 '12 at 22:51