mooler, your download, with using cli options, the problem still happens every time.

Which ip address are you trying to connect to? The one your router assigns to your computer - 192.168.1.149 or something to that affect? Or the IP that your ISP gives you

Make sure you are not logged on to your Windows XP Box

If you have a router try forwarding the IP address of your N800

I have successfully RDP'd into my Windows XP Home box from my own home network as well as from Panera Bread

Im off to work. I'll check back later

Sorry, I should have been more clear. I'm a sysadmin, so I'm talking abouut getting into my Windows servers, which I can easily do using mstsc or MacOS clients. (Also, before you get the wrong idea, please know that I'm a Linux admin; Windows is unfortunately a necessary evil for me (VMware VirtualCenter))

digisage, if your server is running windows server 2003 then it probably has rdp 6 (which vista also has).

On Vista, i need to go into remote desktop and 'Allow connections from computers running any version of Remote Desktop (less secure)' instead of default higher security option using network level authentication. This added security was put in for RDP 6.0 (winserver2003/vista) and the open source rdesktop client does not support that (yet?) Since microsoft built the mac version i guess that version is kept up to date with security of rdp 6.

Also the command line build i did supports -0 option to connect to server console (if thats what your trying to do)

I had to do a couple of things to get rdesktop to successfully and reliably connect with my windows 2003 servers-

On the server go to- Administrative Tools->Terminal Services Configuration. In the 'General' tab I set it at-
Security Layer-> RDP Security Layer
Encryption Level-> Client Compatible

Under the 'Logon Settings' I've set it to 'use client provided logon information' to prevent having to type the user/password twice.

On the tablet, set it to use 8bpp color depth or it'll crash on logon...

At this point it would work 'sometimes'

To get it working consistently I had to create an ssl certificate and install it, then on the same tab of the Terminal services configuration window, set terminal services to use that certificate.

That in mind, it works every time now. (I regularly connect to 5 Windows/SBS 2003 servers and 2 Windows 2000 servers this way for work...)

hope this helps,
kernelpanic

p.s.- there is something with the rdesktop maemo package where once you've crashed by not setting 8bpp, you may need to reboot the tablet to get it to successfully start.

<EDIT> I've compiled the debian etch rdesktop1.5 package for armel and installed it on my tablet. and 16bpp works. (but it's not hildonized. i.e.- once minimized you can't restore the window, hardware keys don't work so '-f' must be specified on the command line, etc...) But it looks as if most of the issues (aside from ecnryption settings) are specific to the maemo port... </EDIT>

anyone know how to simulate right-click with the command line remote desktop client? the key I used with 1.4 doesn't work for me.

I don't know how and why, but it works

The connection is made reliably all the times if and only if data are being exchanged between my n810 and the AP the very moment I press the ok button at the logon screen of rdesktop (Connection Details window).

To ensure this, I press the play button at the "internet radio" applet just before I press the ok button at rdesktop, in order to be sure the ok button will be pressed while internet radio is buffering.

I also tried pressing ok btn while pinging or loading a "heavy" web page. In these cases, it succeeds ocasionally. On the other hand, if you have continous data flow (radio buffering or ftp) it never crashes !

I had a really old linksys (B) wap11 version 2.2 and it did not work with the n810, I now have a netgear that A/B/G and I dont have the problems anymore.

If you have a really old AP, maybe consider upgrading?

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.

Awesome app, I downloaded rdesktop from the maemo repository site. I believe it was ver 0.4. After running once, I ran into the same problems other users reported - it wouldnt open anymore. So, I downloaded ver 1.5 which is xterm or cmd based (is this the right term). I am able to successfully log in to my desktop or laptop computer when using the router assigned IP i.e. 192.168.1.4
I'm using the command ; rdesk -f -u USERNAME -p PASSWORD 192.168.1.4

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

you have set your router to forward the rdp port to your PC have you?