Archive for category Technology

Tunneling Remote Desktop over SSH in Windows 7

Every so often I find myself away from home and needing to use Remote Desktop over an unsecured wireless network.   The Remote Desktop Protocol implemented in Windows 7 has made significant improvements in security over previous versions, but I still like to tunnel the Remote Desktop session through an SSH connection for the extra security.  Tunnneling means that data sent to a local port are forwarded through an SSH connection to a remote port.  In the case of Remote Desktop, once the SSH connection and tunnel are established, the Remote Desktop connection is made to <localhost>:<port> instead of the <remote host>:<port>.  SSH listens for data on that local port and forwards it through the tunnel to the specified port on the remote host.

Before continuing, you’ll need

  1. SSH server on your remote Windows machine
  2. SSH client on the local machine

The rest of this article assumes you’ve got these components installed and working.  I use copssh for an SSH server on Windows 7, and I use PuTTY for an SSH client on my local Windows 7 machine.  With the server and client working, there are two simple steps to tunneling Remote Desktop over SSH: establish the tunnel, then establish the Remote Desktop connection.

Establishing the SSH Tunnel

In PuTTY, set up your session like normal then go to the Connection > SSH > Tunnels screen:

PuTTY tunnel options

Setting up a tunnel in PuTTY

Set the source port to 3391, and set the destination to <hostname>:3389 (e.g. google.com:3389, or equivalently 66.102.7.99:3389).  Leave “Local” and “auto” selected.  Click Add.  (I’m using google.com here instead of any useful domain just as an example)

Important: note the source port is 3391, not 3390 as is typically used in many tutorials around the web.  Windows 7 blocks Remote Desktop connections to localhost:3390.  The source port could be any number of ports, so feel free to try something else if 3391 is already used on your system. (But note that 3389 is the default Remote Desktop port, so do not change that number unless you know what you’re doing).

The added tunnel should look something like this:

PuTTY Tunnel added

PuTTY tunnel added

This means that the SSH connection will listen for data on local port 3391 and forward it to google.com, port 3389.

Now, open the SSH connection (click Open).  A PuTTY terminal will open; you can minimize it or use it as needed, but we won’t need it any more for this tutorial.  The simple fact that it’s present means that an SSH connection has been established between your local system and the remote host, and the tunnel is open.

Establishing the Remote Desktop Connection

Now that the tunnel has been opened between the local host port 3391 and remote host port 3389, we can start the Remote Desktop connection. Instead of typing the remote host name in the Remote Desktop connection window, type localhost:3391.

Remote Desktop Connection

Remote Desktop Connection to localhost:3391

Hit Connect, and that’s it!  Barring any unforeseen problems (see below for some tips on troubleshooting), you’ll be enjoying a Remote Desktop Connection to a remote computer tunneled securely through an SSH connection.  This means all data transmitted and received over the course of interacting with the Remote Desktop session is protected by all the security measures inherent in the SSH protocol.  It’s not impenetrable, but it’s better than RDP alone.

Suggestions for Troubleshooting

If you run into problems, these are some likely culprits:

Firewall – if there is a problem, this is often the source.  Make sure you can successfully connect to the remote SSH server using the SSH client on the local machine (this requires port 22 open).  Also make sure you can establish a Remote Desktop connection to the remote machine (port 3389).  If you can do both of these, then the firewall is not the problem.

Try a different local port – there is always the possibility that port 3391 on the local machine is used for something else.  Try changing this to something random.

Make sure remote desktop is available and  enabled – only Professional and Ultimate versions of Windows 7 will serve Remote Desktop connections (other versions may have just the client for connecting to other machines).  Additionally,  Windows 7 disables Remote Desktop by default.  From the start menu, right-click on Computer then click Properties, then click Remote Settings.  You may also have to explicitly modify the Windows 7 Firewall to allow Remote Desktop (i.e. open port 3389).

, , , , ,

13 Comments

Why I Love the Lenovo X200s

Feast your eyes on the amount of battery life I was projected to get from my Lenovo X200s today:

Close up of the battery meter

Close up of the battery meter

Granted, I probably won’t end up getting the full 15 hours. That came up while viewing a PDF in class with wireless off and the screen at fairly low brightness. In normal use I probably get only 8-10 hours.

You know, only 8-10 hours for a dual-core laptop with 1440×900 screen and 4gb ram. In a well-built 3-lb package. Gotta say, I do love this little laptop.

, , , ,

5 Comments

My Experience with HTC TouchFLO and Windows Mobile 6.5

HTC Imagio

HTC Imagio

I purchased the HTC Imagio (on Verizon) the day it came out.  I had been steadily following the reviews and it looked like the perfect phone.  Wi-Fi, GPS, Bluetooth, Verizon’s 3G network, FM receiver, huge touch screen, and TouchFLO, HTC’s interface to Windows Mobile.

I wanted to love this phone.  I just couldn’t.  Returning to my iPod Touch was like being reunited with an old friend.

I thought it might be useful to give a detailed review of what worked for me and what didn’t; why, in the end, I returned the phone.

The Good

HTC’s TouchFLO interface is generally very well done.  The front screen, shown above, is really nice.  You get a nice big clock, the weather, call information, and upcoming appointments all in one place.  Along the bottom you can quickly see if there are emails or texts waiting to be read.

The screen is beautiful.  It’s large so you can fit quite a lot on it.  It’s vibrant and colorful.  It’s easy to look at.

The phone itself just feels good.  It’s the right size and weight, and the case is solid.  There’s a 3.5mm jack for using normal headphones (more and more common these days, but still nice).

The on-screen keyboard was fine.  Friends who tried it out didn’t like it, but I had no problems.  The XT9 technology makes typing on virtual keyboards basically painless.

The TouchFLO contacts integration is very well done.  Information such as profile pictures can be pulled from Facebook.  You can see in one place all text messages you’ve shared, all emails, appointments, events for each contact.

I loved the camera and I especially loved the video recording.  I’ve never had a mobile camera (that was any good anyway), so this was a new experience for me.  I could get used to it.

The Bad

Here’s a list of my grievances:

  1. The processor in the phone is ancient and it shows.  Opening applications takes forever (notably, mobile outlook), switching applications takes forever, and sometimes the phone just isn’t responsive.  You can never tell whether you’ve pressed something incorrectly without just waiting.  Scrolling in any context – text, websites, pictures, etc. – is slow and jerky.
  2. I really dislike the overall email solution which is sad given the importance of email to the whole smartphone experience.  As you can see in this picture (from pocketnow), the TouchFLO email interface is an envelop with letters sticking out.  This seems fancy and slick, but there are some problems. HTC TouchFLO E-mail Interface
    • The slanted edges of the envelope hide text from the middle of sentences and makes previewing the email annoying.  To read the full email, you have to open mobile outlook.  SLOW.
    • The character set is messed up so that HTML email messages and anything else other than standard text will show the uncomfortable-looking empty box-characters for unknown ASCII codes.
    • The direction for flicking your finger across the screen to move between messages is opposite in the email interface what it is in the text messaging interface.  This may seem trivial, but if you flick the wrong direction on the first email, it automatically loads mobile outlook – and outlook takes forever to load.
    • There is no way to mark a message read from the preview screen (you have to open the email in mobile outlook – recall yet again the bit about it being slow.  Seeing a pattern here?).
    • Mobile outlook is just painful.  It’s slow both to open and operate.  It’s not finger friendly.  It is painful on the eyes.  I couldn’t customize which folders held deleted messages or sent messages, and the default setting was different from all three of my email accounts – so, for instance, when I deleted emails on the phone, I had to delete them again in gmail from this new folder that just showed up.
  3. I dislike the music and picture and video interfaces.  The visual media interface (like the email) tries too hard to be “slick” and ends up just taking up too much space and displaying pictures/videos that much smaller.  The music interface was just terrible.  I could never tell what group of songs I was playing from.  Because the processor was so slow, I hated trying to flip between songs.  The phone couldn’t even play music smoothly in the background while performing other operations – even the non-multi-tasking ipod touch can do that.
  4. There are two competing interfaces for reading and sending text messages.  This wasn’t necessarily bad in and of itself; the problem is that it seemed completely random which one would come up.  The TouchFLO text messaging interface is really well done.  I loved it.  It was fast, it looked good, and it was easy to use.  The Windows Mobile text messaging interface is terrible.  It’s basically mobile outlook with all the inherent problems, including being slow to open and navigate.  Hard to believe HTC allowed that Windows Mobile interface to survive at all.
  5. I actually had to get involved in memory management.  If I didn’t reboot the phone for a week or so, the memory baseline (e.g., all applications closed) would hit up around 85-90% utilization and everything would slow down (even more) considerably.  I cannot imagine a “normal” person (I mean non-nerd), for instance my mother, owning this phone and having to deal with memory management on a regular basis.
  6. I really missed having a dedicated power button to put the phone to sleep.  I had to lock it (only available from the home screen, or depress the “end call” button for three seconds then select that option from the menu) and then just wait for the screen to turn off.
  7. It is impossible to have the phone set to vibrate and the music playback volume set to anything other than silent at the same time.  This is very frustrating when you want to listen to music but forget that turning up the volume for the music turns up the volume on the ringer as well.  I got some nasty surprises from this issue.  Note that when you change the volume, you can change the system volume and ringer volume separately – so they can be at two different audible levels.  You just can’t have one vibrate and the other audible.

The End

In the end, the contrast between the TouchFLO interface and Windows Mobile was just too much.  It’s like living with Dr. Jekyll and Mr. Hyde in your pocket, and never knowing which will appear when you wake up the phone.  This problem is only compounded by the slow processor, since mistakes generally mean you wait.

So, after nearly a month of use, I begrudgingly called Verizon and returned the phone.  To Verizon’s credit, it couldn’t have been easier.  The CSR gave me zero problems and was actually very understanding.  The return shipping label was included in the original shipping.  I put everything back in the box, affixed the label, and dropped it in a Fedex dropoff.  Several days later I called back up, verified the credits to my account, and everything was done.  The reps in every instance were respectful and courteous.  (This is the main reason we switched from Cingular back in the day, and it’s one of the main reasons we stay with Verizon – they seem to be willing to bend over backwards to help me no matter the problem).

HTC has another Windows Mobile 6.5 phone, the HD2, with supposedly much better specs – in particular, a Snapdragon 1GHz processor and a larger capacitive touch screen.  Considering my experience with the Imagio however, the slow processor is only part of the problem.  The real problem is an inconsistent user interface that plagues bottom-line usability of the device.  As nice as that HD2 looks, I’d be wary of the actual user experience.

The Future

So… Droid anyone? :)

, , ,

8 Comments

The Vastly Improved Windows 7 Update Process

Just a quick note today to document one of my favorite improvements in Windows 7. It’s not one that gets a lot of press or is listed on any set of features I’ve seen, but it makes a practical, day-to-day difference in the overall usability of the computer. It’s the Windows Update tool, which today installed the most recent Nvidia drivers, Office 2007 Service Pack 2, a Malicious Software Removal Tool, and several other odds and ends… and then it was done. No rebooting the computer. Just done!

, ,

1 Comment

DRM Pokes Me in the Eye and the Funnybone

I’ve installed Windows 7 Professional (RTM) on all of my computers now–two laptops and two desktops. Overall, it’s an excellent operating system. Memory management appears to have improved significantly, UAC prompts are sparse, and of course the UI has some nice tweaks. Oh, and most system updates don’t require a reboot.

I need to vent about one thing, though, and it may seem small but my goodness it is frustrating. Kind of like getting poked in the eye, or slammed in the funny bone, or like both happening at once. That one thing is the so-called broadcast flag, where broadcasters can flip a digital switch and prevent end users from recording content.

I have a Hauppauge WinTV-HVR 1600 TV tuner with one analog tuner and one ATSC tuner. It worked flawlessly under Windows Vista. We never once had a problem with the broadcast flag.

Now, though, when Emily tries to record an episode of “What Not To Wear” or “More to Love” (I mean, these are seriously popular shows and you can see how broadcasters would want to be REALLY careful about not letting people–oh, the horror–record their precious TV shows and possibly watch them at a later time)–it’s these shows that will record for 5 minutes then we get a little notice in the taskbar: “A recording has been cancelled” and then in Media Center, this now-dreaded popup: “Restrictions set by the broadcaster, yadda-yadda-yadda”:

recordedtv

In some cases a re-run will record just fine later that night.

I think–I hope–this is a bug somewhere, since as I understand it Vista Media Center obeyed the broadcast flag and we never saw this issue.  But, since Windows 7 is so new, and technically isn’t even publically available (my copies are perfectly legitimate), there isn’t much discussion going on and certainly not about this problem.  So, I’m not sure if it’s a driver problem, a Media Center problem, or what.

So poke my eye out, media  conglomerates, operating system, world at large.  Cheap-shot my funny bone.  I don’t care.  Mostly.

P.S. “Food Lovers Fat Loss…” just happened to be on this morning when I needed a screenshot for the blog.  I mean it.  Seriously.

, , , , ,

2 Comments