Industry


Ads by TechWords

See your link here


UltraVNC remote desktop service

Because of an issue an attorney was having connecting to a work PC over VPN using VNC (Virtual Network Computing remote desktop software), I set out to look for a different flavor of VNC that would fix the problem.

Let's begin with the issue he was having: RealVNC and most other flavors of VNC (they are all based on the original VNC software created by AT&T labs) have a problem when used in conjunction with Windows built in Remote Desktop (RDP) sharing software. Basically, if you connect to the console of an XP or 2003 system (you can only connect to console in XP as only one RDP connection is allowed) with RDP and disconnect without logging out of the connection, the connection stays open. When you try to connect with VNC, it will connect, but all you see is a black screen.

For most people, this isn't an issue, as they either use RDP or VNC and not both, but for this user and for me as well, it is a problem as both apps need to be used at different times.

So why use VNC as opposed to PC Anywhere or RDP?

RDP has a major disadvantage for support people in that only one person can see the desktop at a time. If I connect to a user's PC with RDP, their screen goes black and then they get the "locked PC" screen. If I connect with VNC or PC Anywhere, both of us can see what is going on. Much more useful when helping someone with a problem or teaching them how to do something in an app.

PC Anywhere costs money and is really only useful when you need to be able to connect to a PC over dialup or serial connection. If you only do remote sharing over IP at your local network or over the internet, then PC Anywhere isn't worth the cost.

If you don't need to share the desktop among multiple people and you don't need to connect through means other than IP, then I suggest you use Windows RDP as it's typically the best performing solution of the lot.

Anyhow, as luck would have it, there is a flavor of VNC out there that has a built in fix to the issue, UltraVNC. This flavor also has many other features that are not available in any of the other opensource and free versions. Features such as the ability to use NT/200x AD domain authentication for security and working screen scaling. Both of these are muy bueno (that means very good for those of you who don't speak Spanish).

By the way, all VNC flavors are opensource based, but RealVNC does have pay for play versions. Their enterprise version that costs around $50 per license (less if you buy in bulk) does include the ability to use NT/200x AD domain security, but it doesn't yet have the RDP "blackscreen" fix.

UltraVNC also has what they call the Singleclick version, which allows a central support person to deploy UltraVNC on a temporary and as-needed basis to another person. Plus it has other features, like a proxy that can be used to connect two systems hidden between NATed "routers".

So if you do need a remote desktop and RDP won't fit the bill, definitely take a look at UltraVNC. For what it's worth, it gets my stamp of approval.

In another post, I'll also talk about how to deploy it to multiple machines in your network automatically.

What People Are Saying

If you want a front end

If you want a front end designed especially for UltraVNC, you want to take a serious look at http://www.vncscan.com

It's the only VNC manager out there that embraces UltraVNC and it's features so fully.

It's $40 per administrator and that's a steal compare to similar apps of this kind.

Great. Thanks for the

Great. Thanks for the updated info.

This functionality was meant

This functionality was meant for people running in a Terminal Services environment (thus why it refers to DataCenter or Enterprise edition), but it works fine with the standard remote desktop server components too...

The only caveat is that you must (1) be in a domain environment, and (2) that the Remote Control properties be set in the AD User account (otherwise, the user will need to "allow" the connection...

No it doesn't... It either

No it doesn't... It either needs one extra Windows XP Workstation or a Windows 2003 Server - you must connect to a remote desktop session on the server (or other XP machine first), then do the shadow 0 /V:computername command...

Cool...thanks for the

Cool...thanks for the tip.

According to the KB article, though, it only works if you have Win Server 2003 Enterprise or Data Center.

Which I, of course, don't have.

Will definitely file that one away though as it is a good workaround if you have the right tools.

Oh, and I forgot - the key

Oh, and I forgot - the key is to connect to session "0". That is the console session (and the only one available in XP).

Sorry about that.... Take a

Sorry about that....

Take a look at http://support.microsoft.com/default.aspx?scid=kb;en-us;279656 for more information....

You drop a bomb like that

You drop a bomb like that Jeffrey and don't give more info?

Please let us know how to do that...or are you holding out for lunch?

Actually, you can "shadow" a

Actually, you can "shadow" a remote desktop connection and get the functionality you desired....