Archive for Vista

Yesterday I advised a customer who is a remote VPN/Terminal Services user to upgrade to Vista SP1 in order to make "Terminal Services Easy Print" available.

After the installation of SP1 the user was not able access the corporate VPN.

When trying to connect Vista hangs at "Verifying username and password" and eventually shows an 828 error.  On the server side event 20209 was logged.

There is a discussion on the ZA forums as to where the blame lies for the problem but there does not seem to be a clear answer.

For the sake of simplicity, I have found that:

On Vista SP1 machines with version 7.1.248 of ZoneAlarm free installed PPTP VPN connections to Windows 2003 Based RRAS servers do not work.  Also note that disabling ZoneAlarm does not help.  Uninstalling the product solved the issue immediately.

Always a pain when you try to solve one problem and create another in the process.  On a positive note Terminal Services easy print in Windows 2008 worked really well once we got the user reconnected.

Categories : Technical Posts
Comments (2)

I regularly use SSH to connect to customer systems and tunnel various different sorts of traffic through it (Telnet, ODBC, RDP etc). In certain cases, I have no other method of remote access to systems other than SSH.

This has not been a problem until I recently upgraded to Windows Vista which includes remote desktop connection v6, which will not allow connections to 127.0.0.1 on any port, it complains with the error message:

“The client could not connect. You are already connected to the console of this computer. A new console session cannot be established”

Which of course is true, if I were trying to connect to 3389.

So today after spending significant effort in the last couple of months I have found a simple solution to the problem:

  • Instruct your SSH client to listen on all interfaces for connections. For command line this means adding “-g” to your connection. I am using putty so ticking the box that says “local ports accept connections from other hosts” under Connection/SSH/Tunnels will do the job.
  • Putty

  • In the remote desktop client use 127.0.0.2 as the destination host and it will then happily pass through any tunnels you have created. For example 127.0.0.2:3390
  • I realize there probably are not that many people out there using SSH to tunnel RDP, but if you are then RDP 6 has been a real pain until now.

    Categories : How To, Technical Posts
    Comments (8)