TightVNC service problem under x64 7 Ultimate

Page 2 of 2 FirstFirst 12

  1. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #11

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

    Try to break it if you can!
      My Computer


  2. Posts : 53
    windows 7 Ultimate 64 Bit
       #12

    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.
      My Computer


  3. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #13

    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?
      My Computer


  4. Posts : 53
    windows 7 Ultimate 64 Bit
       #14

    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.
      My Computer


  5. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #15

    Hannibal001 said:
    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. :P
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:28.
Find Us