SC (III) Command Line

[athletic_supporter]

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 information, and I haven't gotten it to work for me yet.

I've read that in some versions "id" needs to be capitalized, that sometimes you use ":" but other times you use "-", use "::" for ports < 1024, etc. Now I'm confused. And stuck. I'm basically just guessing and it's not getting me anywhere, so I'm looking for help.

Here's a list what I've tried from the command line:
winvnc.exe -id 1234 -sslproxy -connect my.repeater.com:443 -noregistry

winvnc.exe -id 1234 -sslproxy -connect my.repeater.com:443 -noregistry -run

winvnc.exe -sslproxy -connect my.repeater.com:443 -noregistry -run -id 1234

winvnc.exe -sslproxy -connect my.repeater.com::443 -noregistry -run id:1234

winvnc.exe -sslproxy -connect my.repeater.com::443 -noregistry -run ID:1234

Can anyone shed some light on this for me?

Thanks,

--A.S.

[athletic_supporter]

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 connection is never completed, both sides just sit waiting for each other.

Seems like I'm close, anyone have a suggestion?

[athletic_supporter]

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 to reach out to the repeater. The connection, unfortunately, is not being completed.

I'm running out of ideas. Has anyone ever gotten this to work?

[B]

Does the following thread help at all?

[topic=27589][/topic]

[athletic_supporter]

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 fine when I connect 'regular' (not with command line), so the problem is with the command line.

here is the command line:
winvnc -sslproxy -connect my.repeater.com::443 -noregistry -id 666

and I see this in the logs (with my comments):

--- snip ---
5901

0
socket() initialized
bind() succeded to port 5901
listen() succeded
SSL initialized
socket() initialized
bind() succeded to port 5500
listen() succeded
SSL loading CERTIFICATE.PEM
SSL listener started on port = 443
Incoming Viewer (SSL client) <- HERE'S the "support" component
accept() connection
Viewer added to list 666
Incoming Server (SSL client) <- HERE the "Customer" component fails
numberRecv error. <- ERROR!!!
This TCPTunnel is be destructed <- Tear down of tunnel
Incoming Server (SSL client) <- Repeat "Customer" component... fails
numberRecv error.
This TCPTunnel is be destructed
Incoming Server (SSL client) <- Another connection attempt... fails
numberRecv error.
This TCPTunnel is be destructed
Incoming Server (SSL client) <- now I run "Customer" non-commandline
Server added to list 666 <- and it WORKS... what's different with
Server Removed from list 666 <- the command line???
Viewer removed from list 666

I can't get my head around why it works perfectly with the "double-click" method, but doesn't work from the command line. If we can figure out what's causing the "numberRecv error." then we'll know what the next step is.

anyone have a suggestion?

[B]

From http://www.uvnc.com/pchelpware/sc/helpdesk.html it appears you might need to use the -id parameter <b>first</b>?