![]() Most times, when the UAC prompt came up, TightVNC not only lost the connection, but crashed. ![]() I normally need to do admin-level work on the remote computers, so I hit his issue very frequently. The biggest issue with TightVNC are the hard disconnections associated with the UAC prompt. It would be nice if TightVNC's setup program could create an alternative icon called "TightVNC Server (Application Mode) as Administrator". Many people find it hard to configure the "TightVNC Server (Application Mode)" to start with administrator privileges, and Microsoft has moved things around again in Windows 10 and made it even harder. The first problem with TightVNC is installation. I can then "prove" that such remote control sessions can only be started manually. Avoiding such suspicions is also the reason why I tell users to disable option "Accept incoming connections". There is a second reason: some people use their laptops at work too, and I want to avoid questions from their IT administrators about a newly-installed service designed for remote control. ![]() Most people do not how to configure a port forward on the router (let alone install a VPN), but I can do that on my side, so a reverse connection is the way to go. I always use a reverse connection for security reasons. I am finding that people have often seen TeamViewer and are less inclined to tolerate the difficulties associated with TightVNC, so I have to endure more and more snarky comments about the low-quality open-source software I tend to use. Yesterday I had a particularly bad time with TightVNC and I wanted to share it with you. I have even written setup instructions in Spanish, in case I cannot preinstall it on the target computer: I have used it for years to help friends and relatives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |