maemo.org - Talk - rDesktop for OS2008?

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - rDesktop for OS2008? (https://talk.maemo.org/showthread.php?t=13037)

Re: rDesktop for OS2008?

i believe this is what i opened up in the port forwarding area.... i opened up port 3389 to alow traffic in n out from my pc

Re: rDesktop for OS2008?

I have downloaded and installed rDesktop for 2008, and it installed fine,except that its in the EXTRA'S folder and I'm told it should be in the UTILITIES FOLDER, Plus, which I fill in the info and click to OK button, NOTHING HAPPENS, and I mean NOTHING, no white screen, no flicker, NOTHING. HELP!!!! SOMEONE, ANYONE. I would love to get this thing working. I re-FLASHED 2 times already

Re: rDesktop for OS2008?

Quote:

Originally Posted by jaysen (Post 137876)

Originally, I posted this in the NEWBIE section - But figured having it posted here would gain more traffic;

Be gentle...

So I finally took the plunge and bought a new n810 Let me lay a quick foundation for you on my background with Linux based system; None. With that said, thank god for the internet and these forums... heh. ive been able to quickly learn the general functions and messed around with xterm. After days of reading, I finally got the courage to install rdesktop.

So now that I have successfully logged in via my wireless network. I decided to try and connect to it via using an EVDO Bluetooth connection via my paired treo 700p (w/ PAM hack) and n810. I have opened the default port of 3389 (assigned by windows) via my router and assigned "Public IP" to the IP my isp issues. I Believe I have everything setup correct but when I try to connect using either of two cmds below, I receive the same error;
rdesk -f -u USERNAME -p PASSWORD MY.IP.ADDY
rdesk -f -u USERNAME -p PASSWORD MY.IP.ADDY:3389

1. It will give me an error that says ERROR: connect: No route to host

or

2. Autoselected keyboard map en-us and then just lock up there...

When i re-run the command to try and connect I can see data being sent on my treo but after a couple of minutes it stops and goes inactive...

So my question is... Is my phone not allowing me to connect because it cannot do UDP TCP via 3389 ? or is the EVDO connection just too slow to allow a usuable rdesktop enviornment ?

Any help would be greatly appreciated... Just so you know I have not been able to try connecting via another Wireless connection not of my own... maybe I can walk the neighborhood for an unsecure connection to see if I can connect ?

If this helps any I am currently setup on Verizon FiOS here in California, my router is in Actiontec

I have used rdesktop over dialup, 1xCDMA, and EVDO no problem. (EVDO is screaming fast) It should work fine. There's a couple of things you can try.

1. from a windows machine connected to the internet (but not on your home router) try to connect using the Remote Desktop Connection. This will tell you whether your port forwarding is working correctly for tcp port 3389. Make sure you are using the correct IP address. Verify the external IP address of your DSL/cable modem. (How you do this depends on your hardware.) With DSL, IP address sometimes changes, With Cable, sometimes you don't get a real (i.e.- Internet Routable) IP at all, making RDP problematic. If you have a modem AND a router, then you need to make sure that either
A- your modem is bridging and your router/firewall has an external IP address.
or B- your modem is forwarding to your router AND your router is forwarding to your computer correctly.

2. Connect your treo to your n810 and open the web browser to verify whether you are actually tethered. If you can't open a webpage, you are not online. Thus, no path to host.

hope this helps,
kernelpanic

Re: rDesktop for OS2008?

kemelpanic-
thanks checking the first now

Re: rDesktop for OS2008?

Quote:

Originally Posted by tj110158 (Post 139106)

this is the same problem many people are having (including me). the command line version (1.5 I believe) works, but I can't get a working right-click...

Re: rDesktop for OS2008?

Quote:

Originally Posted by doubledrat (Post 139323)

this is the same problem many people are having (including me). the command line version (1.5 I believe) works, but I can't get a working right-click...

I have repackaged the installer for command line rdesktop (for other reasons) so i went ahead and bound this key in newest installer.

The original post i made of this had instructions for editing ALL of the hardware buttons by editing the /usr/lib/rdesktop15/keymaps/common file

But if your only interested in menu key, install current package here :
http://wardenclyffetower.com/MaemoFi...-cli-1.5.0.deb

Re: rDesktop for OS2008?

brilliant. thanks! I missed the original post, so didn't know I could do it myself. Now I've no reason not to go for os2008 (apart from lack of capslock :( but I'll live without that)

Re: rDesktop for OS2008?

To everyone that has assisted me....

THANKS !

All of you were on the right track with all your suggestions... I ended up having a port conflict with my Slingbox and RDP... Long story short one of my call lines said to allow RDP to connect to Slingbox - How that got screwed up... I DUNNO.

But it is not fixed, and I am proud to say I have been able to sucessfully RDP using my n810 and any (useable) internet connection.

Re: rDesktop for OS2008?

ADVICE?

I have sucessfully run rDesktop on my N810 to my Win XP pro PC from within my house using the IP address of the PC through my wireless USB router. (It's spotty but mostly connects). However I have never been able to connect at another access point (it locks yp on the OK button and finally times out). I'm guessing the IP address is incorrect in the rDesktop start screen although I got it using http://whatismyipaddress.com/. I have RR cable for ISP. Any ideas anyone? Thanks!

Re: rDesktop for OS2008?

You need to make sure your router is forwarding in port 3389 to the computer you're trying to connect to. It's unlikely that your ISP is blocking this port, but your router most likely is, if only as a side effect of using NAT between your internal network and your ISP.

Keep in mind there are security implications of opening up this port to the outside world.