View Single Post
Posts: 50 | Thanked: 15 times | Joined on Jan 2011
#373
Originally Posted by Pigro View Post
Ah - I thought you meant that you got a graphical window for your host PC in the "foreground" of the n9000, but with that window not displayed fullscreen but with a title bar showing ... what you actually meant is that when you run your script, you are left with the stdout from the rdesktop startup script rather than getting the remote desktop graphics screen displayed - until you go to the n900 task switcher screen and choose the actual rdesktop window (which is there in the background) explicitly.

I now understand, but I can't really help. Maybe try PM'ing the maintainer? Otherwise, if you set up a temp guest login to your rDesktop host and PM me the account details, I could connect to it from my n900 to see if I get the same issue (assuming the host is accessible over the internet) ... that would at least help you narrow it down to either your n900 rDesktop install playing up OR your host PC being somehow responsible. I realise that you probably don't want some random bloke off a forum logging into your server (even on a locked down guest account) so no problems if you don't fancy it :-)
An image tells you more than 1000 words ...

I tried this connecting to about 5 systems - to whom I connect on a daily basis, all with the same result.
Win7Ultimate, W2K3 server, W2K8(R2) servers, Windows Home Server, ...
You can see why I would like this to work as smooth as possible ;-)

When I try the same rdesktop connection from my ubuntu systems, they work flawless !

I'll try to PM the maintainer. When I get feedback or a solution, I'll post back here .