Notices

2: Go to the start menu (on your windows box) and select "Disconnect"

3: Enter this as the command to start rdesktop, substituting your own information where applicable:

Is it just me or is it even harder to tap things on the top and bottom edge of the screen now (ie windows taskbar or the window controls on top right)

On the N810 the only issue i had was with the right scrollbars, and i assumed that with the N900's screen being flush it would be able to detect everything just fine, but it seems like in practice the bottom and top are much less accurate than before (left and right edges seems perfect now, though, for what its worth). I wonder if making the resistive contact surface larger than theviewable area would make touches to the edge of the screen reasonably accurate.

Yeah, so are you guys having issues hitting the taskbar? I've tried calibrating the screen multiple times, but it seems like its once again a hardware limitation

rdesktop-cli -f -u username -p password 123.123.123.123:1234 works perfect for me. But the rdesktop app not - and it would have been so nice to have some UI...

Any hints?

Don't forget you can use the accessability on screen keyboard if you need specific keys that the N900 can't handle.

I am having the exact same problem but at least rdesktop-cl is working.

...and fast. Just great - any ideas how to make a batch/script and a shortcut on the desktop. That would help so much already... tired of typing into the terminal prompt each time.

Download the Rdesktop-cl it already comes with a GUI that saves most of the setting for you.

rdesktop-cli you mean? No UI at all - rdesktop (1.7 something) has a UI yes - but does not work for me (and a couple of others as you can read here...)

Very strange I have no probs at all with 1.7. Using it through ssh on Lan and over internet gateway. All I can suggest are the problems I faced when setting up initially.
1)Make sure you have a server running on the windows machine. I use Cygwin which is free and easy to set up.
2) If you are running Vista home or Xp home it will need to be patched to get the term server running.
3)Make sure to open port 22 on your router and forward to appropriate ip.
4)Make sure to allow remote access to computer and open port 22 on firewall if needed.
5)Try sending it through ssh tunnel specific to local host
ssh -L3389:localhost:3389 user@remotemachine
Then when connection is established log into rdesktop and instead of putting ip address type
localhost:3389
6)Make sure your workgroup matches that of the workgroup computer you are logging into.
7)Double check that you are using the correct ip address if you are trying to connect outside of your LAN you will need your public ip address.
8) Finally make sure that port 3389 or whatever port you choose to use is listening on remote computer. For windows type:-
Netstat -a -n
into cmd prompt.

Sorry if these are basics to alot of you these are just issues that I have come accross and overcome to make it work. Hope it comes together.

Judging by this post earlier in the thread it appears that the new rdesktop doesn't understand the syntax for non-standard ports and tries to resolve the whole thing as a hostname. With a server on the usual port 3389 it works very nicely though.