TightVNC service problem under x64 7 Ultimate

[mANgLEr]

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?

 

[bartels]

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

Cheers,
B.

 

[TimStitt]

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. Win7 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.

 

[TimStitt]

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 Win7 is the same). TightVNC: Version 1.3.10 Released

How did you get the service installed on Win7?

 

[bartels]

Hello TimStitt!

There is a separate folder with the installer:

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

Thanks for helping out.

B.

 

[TimStitt]

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/Win7/S2008 this will be fixed in the next release, without the service running it works fine in Vista/Win7/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 Win7/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

 

[bartels]

Thanks! This is very helpful.

B.

 

[TimStitt]

Thanks! This is very helpful.

B.

You're welcome!

 

[rvlewis]

Tight/Ultra

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.

 

[Hannibal001]

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.

 

[TimStitt]

Great.... let us know how you go with the tests.

Try to break it if you can!

 

[Hannibal001]

I found out that it was not my system but Comodo Internet Security giving me the problems. I got rid of Comodo and got ESET Smart Security and seem to have no problems now( I am running Real VNC now also but do not see why Tight VNC would not work). However when uninstalling the Comodo I found a process remained on my system named cmdagent.exe which did NOT want to be removed. Had to restart in safe mode and use LockHunter for windows 7 64 bit to get rid of it by unlocking it and delete it on next reboot. I used ESET for many years and only stopped to wait for them to catch up w/ Windows 7 64 bit.

 

[TimStitt]

Hi Hannibal001,

I'm sort of lost here... let me try to piece it together (but get out your red pen for corrections )

So you installed the new tight VNC but there was problems that you couldn't solve. These problems were related to comodo as you described. So you used RealVNC instead and that works. But we still don't have tTghtVNC working on Win7 64bit. Is this correct mate?

 

[Hannibal001]

I did not try Tight VNC again. Just went w/ Real VNC. And yes, it was Comodo refusing to accecpt my instructions to let any vnc through(from my laptop;both PC & laptop running Win7 ultimate 64 bit). Installed ESET and it connects just fine(after it asked for permission to let it). And Comodo left behind a .exe that was locked and tried to download something on reboot from uninstall. ESET stopped it and I found the process but could not do any thing w/ it because it stated I did not have permission to access file. When I went to services it was there but machine said could not find file or process. Live help from comodo was no help. Just told me reinstall and then uninstall again,which would have required me(they said) uninstall ESET first then reinstall it again(BLAH-BLAH-BLAH). I had a couple of probs w/ comodo not listening to instructions when setting permissions. And in training mode would let EVERYTHING through without a popup telling me what was going on. Will NOT be using comodo again. Also when testing vnc connection, vnc would say my router was the culprit, but it was forwarded right and was comodo blocking connection. I hope this helps clear up things a little. If not post again and I will try to clarify.

 

[TimStitt]

I did not try Tight VNC again. Just went w/ Real VNC. And yes, it was Comodo refusing to accecpt my instructions to let any vnc through(from my laptop;both PC & laptop running Win7 ultimate 64 bit). Installed ESET and it connects just fine(after it asked for permission to let it). And Comodo left behind a .exe that was locked and tried to download something on reboot from uninstall. ESET stopped it and I found the process but could not do any thing w/ it because it stated I did not have permission to access file. When I went to services it was there but machine said could not find file or process. Live help from comodo was no help. Just told me reinstall and then uninstall again,which would have required me(they said) uninstall ESET first then reinstall it again(BLAH-BLAH-BLAH). I had a couple of probs w/ comodo not listening to instructions when setting permissions. And in training mode would let EVERYTHING through without a popup telling me what was going on. Will NOT be using comodo again. Also when testing vnc connection, vnc would say my router was the culprit, but it was forwarded right and was comodo blocking connection. I hope this helps clear up things a little. If not post again and I will try to clarify.

AH, I understand now.

I really dislike it when you end up with numpty support staff at businesses that should know better. I had a similar problem with VMware until I was escalated past the newbie techs, and Pacnet (my ISP in Australia) since they outsourced has some of the worst tech staff I've ever encountered). It looks like you're experience with Comodo has added them to the family.