Windows 7: TightVNC service problem under x64 7 Ultimate

After installing TightVNC 1.3.10 I can start the server manually using the 'Launch TightVNC Server' start menu shortcut but running it as a service gives me problems. The WinVNC.log file states:Unable to connect session to Console (error 5)vncDesktop.cpp: Console is not session zero - reconnect to restoreI've used TightVNC on many systems but I've only ever seen this on my new Windows 7 Ultimate x64 install and a Windows 2008 Enterprise x64 server.Can anyone explain what 'session zero' is and how I can get the TightVNC service working as it does under XP Pro?

I have the same problem. Did you ever find a solution?

Cheers,
B.

Hi mANgLEr & bartels,

Prior to vista, console session used to always be zero (i.e. the physial I am sitting in front of it' logged in session). Remote sessions pick up a number thereafter. Windows 7 console session ID is 1.

I'm not sure how to fix your TightVNC though as I have used Ultra VNC for the last few years. In Remote desktop you can edit the saved RDC file and add the 'connect to console' command, perhaps something is similar for TightVNC. I'll have a look and get back to you.

Hmm.. It didn't seem to create a service when I installed it. Nor can I find an option to do this.
A quick check on their website shows that it won't create a service in Vista (I guess Windows 7 is the same). TightVNC: Version 1.3.10 Released

How did you get the service installed on Windows 7?

Hello TimStitt!

There is a separate folder with the installer:

All Programs
-> TightVNC
-> Administration
-> Install VNC Service

Thanks for helping out.

B.

ah-ha, I missed that!

I just finished testing for you. Here's what I found.
From their website - TightVNC service is incompatible with Vista/Windows 7/S2008 this will be fixed in the next release, without the service running it works fine in Vista/Windows 7/S2008
I tried to circumvent this, but no luck.

So I looked further and found that the service for UltraVNC works perfectly on my 64bit. Perhaps the easiest and less messiest solution is to use UltraVNC on your Windows 7/2008 boxes. It's totally cross compatible with TightVNC (well they are all VNC protocol ), so there is no need to update your current clients.
Download UltraVNC

Thanks! This is very helpful.

B.

You're welcome!

I also prefer UltraVNC, but it does not work well with multiple displays, so I have had to use Tight VNC and an having the same problem.

The new VNC is out for Win 7.I just installed and am running it now.Seems to work fine and will test it from an away connection tomorrow. Will let you know what happens.