Hi There !!!
I've seen a similar post by John Hamilton about the same issue and i've currently been having the same issue with e the person on a windows vista terminal without any service packs & limited updates which i sthe reason im trying to use a remote connection to do this for them.
we set up a Tight VNC connection as a test coz previously we used REALVNC Free edition before they stopped updating it and i came across your version so decided to give it a gofor the simple reason you have windows vista and windows 7 support but i thought it wouldnt work being 2.0.2 doesnt work on win98se
so i became a smart ass and installed 1.3 on my win98se test terminal and got my friend to install 2.0.2 his end to test a theory.
and after an hour of setting it up & several screengrabs sent back and forth over msn messenger to guide him step by step we got it working fine.
At this point we were sooo happy more so on my part.
the program config has been running fine for a few days and no connection issues on port numbers or anything the only issue that happened was i couldnt connect to his computer 2 days ago on the correct ip addy...so we went through the option turning stuff off and nothing including his windows firewall...still nothing so he sent me a screenshot again
and the server by the clock has a red square around it so reading John hamiltons post i followed constatines advice about checking for multiple servers running and there was 2 "tvnserver.exe" processes runnign at 500k-700k so we exited the one and the other disapeered
this was odd so we started the server up again and the red square of death came back & so did the 2 processes as if they were linked together also the options to disable the server or kill clients are missing on the rightclick menu by the clock like tight vnc 1.3 has so we know this wasnt an issue even though i searched for a server disable type key in the registry but to no joy.
so to this point we have got completely baffled and i've tried everything to fix this apart from asking my friend to install 1.3 on his vista as im unsure if this will work at all fully like 2.0.2 does as the guy has both win7 and vista in his home.
i have asked him to uninstall 2.0.2 and then reinstall but surely this cant be a bug ??? if it is then and beta releases for us to try would be grateful as i see 2.0.3 was mentioned
and finally is the file transfers option within the vnc viewer always meant to be greyed out of does it only work when both partys are using the same version of tight vnc as in 2.0.2 or higher & not backwards compatible because trying to configure aol messenger to transfer files is a pain in the ass even though it does have a resume transfer function and this is good if the transfer crashes or takes to long.
id prefer if the tightvnc 1.3 & tight vnc 2.02 packages were merged into one program so it works on any o/s and has all the latest functions...next is chat functions lol.
please help out if you can.