UltraVNC

Thanks, that thread shows me that others have similar problems, and that (presumably) this will eventually work. I'm sticking to it and will (do my best to) solve it. After further investigation, I find that the commandline (above) connects to the repeater, but encounters an error. It works just ...

Getting closer... by sniffing the traffic on the repeater, I see that no combination of parameters causes winvnc to try to connect to the repeater, until... winvnc -sslproxy -connect my.repeater.com::443 -noregistry -id 1234 -service So, even though it's running as a service (?!?), it at least tries ...

So, here's what I've got so far: winvnc -sslproxy -connect my.repeater.com::443 -noregistry -id 1234 -run and winvnc -sslproxy -connect my.repeater.com::443 -noregistry -id 1234 -run -listen both cause the 'customer' application to launch in the background without asking for the ID. However, the ...

I'm trying to get the SCIII "customer-side" (winvnc) to launch with just a command-line, rather than the usual double-click & enter your ID. SCIII works fine for me the usual way, and I've read the posts and the doc on the command line parameters which are accepted, but I'm getting conflicting ...

I'm using SCIII to access headless appliances (i.e. no monitor can be attached as the video port is removed). My problem is that most (nearly all) of the appliances are behind HTTP(s) proxies, and I can''t figure out how to configure the appliance (running winvnc.exe) to use the HTTPS proxy. One ...