yes, it is definitely possible - like I say, I'm doing it and it works fine ... I've tested for you again today, connecting to the following:
windows 7 home premium (frigged to allow rdesktop host)
windosw 2003 server
windows 2000 server
and all open fine in fullscreen when called from within a script on my n900 (didn't test via an ssh but IMO that's irellevant to your issue).
note - running rdesktop -f connects fullscreen (with the fullscreen toggle icon in the bottom right of the screen) - if I toggle, the window is entitled rdesktop - xxx.xxx.xxx.xxx), but running rdesktop-cli -f does NOT result in fullscreen, I get the session displayed in a window titled "xterminal" and without the fullscreen toggle icon bottom right.
As I said previously my installed version of rdesktop is 1.7-maemo3 while rdesktop-cli is at 1.6.3-maemo3 (both according to FapMan).
However when I type rdesktop (no parameters) it reports client version 1.6.0, and running rdesktop-cli (no parameters) reports the same client version. rdesktop-cli is in /usr/bin, size 224472 bytes, while rdesktop is a symlink from /usr/bin -> /opt/maemo/usr/bin/rdesktop, size 250792 bytes.
It sounds to me like you may be running an old version of rdesktop (or maybe you've previously manually created a symlink to an old version or something)? I suggest you double check that you are up to date - uninstall & reinstall the app's if neccessary to be sure - and double check what is actually running when you call rdesktop.
Pigro,
already a great thanx for you exquisite support !
I checked all versions, (sym)links and sizes and my configuration is EXACTLY the same as yours.
Uninstalled an reinstalled, I always get the same result. The connection succeeds in Fullscreen,
but it seems it lacks a refresh or something. For example the screenshot below; it doesn't show the mousepointer but
it's already there, I can even move that mouse.
I am pretty sure by now it has to do something with launching in the background or so;
if I connect, Push Ctrl + Backspace, and then select the window, it works fine too !
script looks the one you made, and I launc it from a terminal like this:
./conn
sh conn
./conn &
It's not that ia can't use it like this, the main reason is I want to understand what is happening ...
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 :-)
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 .
so any updates to the screen refresh problem? also, how do i get rid of the fullscreen icon at the bottom right? there are times when i need to click at the lower right of the screen.....
plus, for folder mapping - do i need any additional ports opened on the firewall?
also, how do i get rid of the fullscreen icon at the bottom right? there are times when i need to click at the lower right of the screen.....
The only time you would normally need access to the lower right hand corner of the remote real estate is to access the windows task tray (as for any app you are running within windows, you can move the app window itself to avoid overlapping with the N900 fullscreen icon). If that is your need, you can get to any hidden tray icons by clicking on the top of the task bar and dragging it up from 1 line high to 4 or 5 lines high - this will expose most/all of the hidden task tray icons. Not a solution, but a viable workaround (at least for me) for the few times I need to do this.
plus, for folder mapping - do i need any additional ports opened on the firewall?
you mean such that your local n900 share(s) are exposed on the remote PC in explorer? You should be good to go without any f/w changes (on either side) in that case.
ok. thanks for the replies. i can't get folder mapping to work at all.
also, for some keys which are not on the keyboard (like > and <), how do i enter them?
as for the lower right, when i use office, there is a zoom control slider there which i can't access because that icon is blocking it. guess i'll have to do it the hard way.
rdesktop + ssh combo has really freed me from carrying my laptop. now all i need is a decent mouse + keyboard with bluetooth connectivity and i literally have a mobile computer with me (oh and bring along the RCA input cable as well so i can plug it into a TV for a super big screen to do my work). aaaaaah! such freedom!
Hi guys. I've been studying this thread for few days now - and have become totally confused.
My problem is like a few others that i can connect flowlessly to my home p.c thru rdesktop on N900 via my own router. If i try connecting thru 3G or from any router other than my home router, it jus does'nt connect.
All firewalls are disabled on my computer and router configured to forward port 3389 to my static ip (home pc).
I have tried logging in with my host p.c ip and with my real router ip with no luck. (i am assuming my real router ip is the same that i use to log in to my router settings i.e. the one i type into the browser for router config).
Can any1 guide me plz. Am i supposd to install anything on the pc or on the phone becoz at the moment I have not installed any software on my p.c to assist remote sessions. Only thing i've done is install rdesktop on my N900. P.s. I have read other members talking about something like vnc and ssh softwares, i dnt knw if this is my problem. So wot's the nxt step i take plz b4 jumping into the river, becoz i dnt knw if the problem lies with my phone, pc or the router.
