Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 11 hrs, 1 min ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 7 hrs ago - more...
clovis86 |
2011-02-24
, 22:29
|
|
Posts: 575 |
Thanked: 621 times |
Joined on May 2010
|
#361
|
nice one !
|
|
2011-02-27
, 19:21
|
|
Posts: 13 |
Thanked: 1 time |
Joined on Feb 2011
@ Stip , Macedonia
|
#362
|
Hi all ..i know this will sound lame for most of you guys but i really need to get to work this applikation ( rdesktop ) . I have win 7 with configured remote desktop settings and i've downloaded rdesktop client on my n900. now the question is : what to type in the fileds server and domain ...i also dont have usename and pass setup on that computer its just one admin user ..
i'd really appreciate your help.
Thanks in advance
i'd really appreciate your help.
Thanks in advance
|
|
2011-03-23
, 10:11
|
|
Posts: 50 |
Thanked: 15 times |
Joined on Jan 2011
|
#363
|
Hello,
yesterday I finally had the time the check out rdesktop on my N900.
Both at home and at work I have setup an ssh server om a windows server (Bitvise WinSSHD, great free software).
We use a ssh tunneling app so we have a kind of lightweight VPN: RDP over SSH. (BitVise Tunnelier, great free software)
I supposed it would be easy to do the same from my N900, and it does !
SSH to the box, portforward and rdesktop into it.
I have only one problem. When I do rdesktop via GUI, it works flawless, immediate fullscreen image.
When is use rdesktop from script, it connects, but i have to push the power button once and escape from it to diplay the RDC correctly. It does show a mouse and 'rdesktop connecting', but does not seem to continue displaying
script looks like this:
ANyone an idea ? I have searched google and TMO, but have not found a solution 
Tnx in advance,
kind regards,
wimmme
yesterday I finally had the time the check out rdesktop on my N900.
Both at home and at work I have setup an ssh server om a windows server (Bitvise WinSSHD, great free software).
We use a ssh tunneling app so we have a kind of lightweight VPN: RDP over SSH. (BitVise Tunnelier, great free software)
I supposed it would be easy to do the same from my N900, and it does !
SSH to the box, portforward and rdesktop into it.
I have only one problem. When I do rdesktop via GUI, it works flawless, immediate fullscreen image.
When is use rdesktop from script, it connects, but i have to push the power button once and escape from it to diplay the RDC correctly. It does show a mouse and 'rdesktop connecting', but does not seem to continue displaying
script looks like this:
Code:
#! /bin/sh ssh -L3390:127.0.0.1:3389 IP -lusername -p PORT -N -f sleep 10; rdesktop -u username localhost:3390 -p PASSWORD -D -f
Tnx in advance,
kind regards,
wimmme
|
|
2011-03-24
, 09:18
|
|
Posts: 50 |
Thanked: 15 times |
Joined on Jan 2011
|
#364
|
no one ? I have similar issues with rdesktop-cli.
rdekstop -f show connecting (wile already connected) and needs the power button + exit sequence
rdesktop-cli opens a connection in the correct resolution, but wirh the title-frame visible and the taksbar invisible -> incorrect window handling.
I really tried all possible combinations of options, but still nog go :-(
rdekstop -f show connecting (wile already connected) and needs the power button + exit sequence
rdesktop-cli opens a connection in the correct resolution, but wirh the title-frame visible and the taksbar invisible -> incorrect window handling.
I really tried all possible combinations of options, but still nog go :-(
|
|
2011-03-24
, 13:11
|
|
Posts: 433 |
Thanked: 274 times |
Joined on Jan 2010
|
#365
|
I don't use rdesktop from the command line anymore, but I used to use it over ssh that way and I still have following script (called from a desktop shortcut). Just tried and it launches rdesktop correctly in fullscreen no problem:
i have rdesktop version 1.7-maemo3 installed. Make sure you are on that version (I seem to remember full-screen issues & problems passing keyboard input to the app in previous rdesktop-cli versions).
If you're on the latest version already, maybe try reordering your parameters in case that makes a difference? or maybe try launching xterm from a script like above in case that's significant? I can't remember now why I started my ssh in background and then ran the rdesktop as a separate background process (rather than just putting them as sequential calls like in your method above) but I guess there must have been some timing issues in getting the tunnel up over gprs - I doubt that has any relevance for you. same goes for the fact that I am calling via tsocks (I needed that to have rdesktop use my socks proxy in order to remotely connect over 3G/public wifi to a 3rd party system via my own desktop in order to fool 3rd party firewall into thinking the traffic was coming form my home IP). I now have openvpn set up so I don't need any of the ssh/tsocks, I just connect from n900 to my home vpn and then run the rdesktop gui on n900 from within my own LAN in order to connect to the 3rd party from my WAN static IP (for which the 3rd party has a firewall exception).
Last edited by Pigro; 2011-03-24 at 13:28. Reason: added tsocks explanation & edited script for clarity on home/3rd party aspects
Code:
#!/bin/sh echo "start ssh" /usr/bin/osso-xterm 'ssh -p PPPP -D DDDD my_user@my_home_server.no-ip.org' & echo "sleep" sleep 15 echo "start rdesktop" /usr/bin/osso-xterm 'tsocks rdesktop -a 8 -f -u 3rd_party_username -p 3rd_party_password -r disk:N900=/home/user/MyDocs -d 3rd_party_domain xx.yy.zz.aa' & echo "after rdesktop exit"
If you're on the latest version already, maybe try reordering your parameters in case that makes a difference? or maybe try launching xterm from a script like above in case that's significant? I can't remember now why I started my ssh in background and then ran the rdesktop as a separate background process (rather than just putting them as sequential calls like in your method above) but I guess there must have been some timing issues in getting the tunnel up over gprs - I doubt that has any relevance for you. same goes for the fact that I am calling via tsocks (I needed that to have rdesktop use my socks proxy in order to remotely connect over 3G/public wifi to a 3rd party system via my own desktop in order to fool 3rd party firewall into thinking the traffic was coming form my home IP). I now have openvpn set up so I don't need any of the ssh/tsocks, I just connect from n900 to my home vpn and then run the rdesktop gui on n900 from within my own LAN in order to connect to the 3rd party from my WAN static IP (for which the 3rd party has a firewall exception).
__________________
n900: "with power comes responsibility".
If you buy a niche, highly modifiable smartphone and proceed to mess it up by blindly screwing around, don't just blame the phone, also blame yourelf.
n900: "with power comes responsibility".
If you buy a niche, highly modifiable smartphone and proceed to mess it up by blindly screwing around, don't just blame the phone, also blame yourelf.
Last edited by Pigro; 2011-03-24 at 13:28. Reason: added tsocks explanation & edited script for clarity on home/3rd party aspects
| The Following User Says Thank You to Pigro For This Useful Post: | ||
|
|
2011-03-24
, 13:42
|
|
Posts: 50 |
Thanked: 15 times |
Joined on Jan 2011
|
#366
|
Tnx Pigro, was thinking in the same direction.
To launch both processes in background so rdesktop could come in front, and let the SSH connection close when i tsdicon from the rdesktop.
Will try this this evening and feedback here ...
To launch both processes in background so rdesktop could come in front, and let the SSH connection close when i tsdicon from the rdesktop.
Will try this this evening and feedback here ...
|
|
2011-03-25
, 21:51
|
|
Posts: 50 |
Thanked: 15 times |
Joined on Jan 2011
|
#367
|
Originally Posted by Pigro
Sorry but no go. This has the same result as my own script. Strange ...
I don't use rdesktop from the command line anymore, but I used to use it over ssh that way and I still have following script (called from a desktop shortcut). Just tried and it launches rdesktop correctly in fullscreen no problem:
i have rdesktop version 1.7-maemo3 installed. Make sure you are on that version (I seem to remember full-screen issues & problems passing keyboard input to the app in previous rdesktop-cli versions).Code:#!/bin/sh echo "start ssh" /usr/bin/osso-xterm 'ssh -p PPPP -D DDDD my_user@my_home_server.no-ip.org' & echo "sleep" sleep 15 echo "start rdesktop" /usr/bin/osso-xterm 'tsocks rdesktop -a 8 -f -u 3rd_party_username -p 3rd_party_password -r disk:N900=/home/user/MyDocs -d 3rd_party_domain xx.yy.zz.aa' & echo "after rdesktop exit"
If you're on the latest version already, maybe try reordering your parameters in case that makes a difference? or maybe try launching xterm from a script like above in case that's significant? I can't remember now why I started my ssh in background and then ran the rdesktop as a separate background process (rather than just putting them as sequential calls like in your method above) but I guess there must have been some timing issues in getting the tunnel up over gprs - I doubt that has any relevance for you. same goes for the fact that I am calling via tsocks (I needed that to have rdesktop use my socks proxy in order to remotely connect over 3G/public wifi to a 3rd party system via my own desktop in order to fool 3rd party firewall into thinking the traffic was coming form my home IP). I now have openvpn set up so I don't need any of the ssh/tsocks, I just connect from n900 to my home vpn and then run the rdesktop gui on n900 from within my own LAN in order to connect to the 3rd party from my WAN static IP (for which the 3rd party has a firewall exception).
|
|
2011-03-27
, 20:50
|
|
Posts: 50 |
Thanked: 15 times |
Joined on Jan 2011
|
#368
|
I kept playing with parameters and other script, but I think I am just not skilled enough to make this work. I cannot imagine this doen't work; It should be possible to open a remote desktop connection fullscreen from a script, not ?
|
|
2011-03-27
, 23:08
|
|
Posts: 738 |
Thanked: 179 times |
Joined on Mar 2010
@ Gold Coast, Australia
|
#369
|
Originally Posted by basarovski
Ok make sure you have wifi connected to your n900 now on your PC open up the command cmd, type ipconfig press enter now look for your IPV4 address it will be somthing like 192.XX.XX.XX maybe completly diffrent on your router.
Hi all ..i know this will sound lame for most of you guys but i really need to get to work this applikation ( rdesktop ) . I have win 7 with configured remote desktop settings and i've downloaded rdesktop client on my n900. now the question is : what to type in the fileds server and domain ...i also dont have usename and pass setup on that computer its just one admin user ..
i'd really appreciate your help.
Thanks in advance
Just input that IP into Rdesktop on N900 like this mine is this
10.0.0.1:3389 where 3389 is the port number for remote desktop
|
|
2011-03-28
, 11:14
|
|
Posts: 433 |
Thanked: 274 times |
Joined on Jan 2010
|
#370
|
Originally Posted by wimmme
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:
I kept playing with parameters and other script, but I think I am just not skilled enough to make this work. I cannot imagine this doen't work; It should be possible to open a remote desktop connection fullscreen from a script, not ?
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.
__________________
n900: "with power comes responsibility".
If you buy a niche, highly modifiable smartphone and proceed to mess it up by blindly screwing around, don't just blame the phone, also blame yourelf.
n900: "with power comes responsibility".
If you buy a niche, highly modifiable smartphone and proceed to mess it up by blindly screwing around, don't just blame the phone, also blame yourelf.
Last edited by Pigro; 2011-03-28 at 11:17.
