Issue connecting viewer to repeater

[Sdrabor]

I am doing this using:
Repeater 1.1.0.7
UltraVNC 1.0.2

Everything is working fine when I use the standard UltraVNC connection using my repeater IP:port. Here's where I'm running into problems:

When I try to use a VNC link with the switches -proxy IP:port -ID: myid on the end, it connects, sits for about 5 seconds, and then in the repeater logs I see this:
connecting to 0.0.21.124:5900, and then eventually -
connect() failed.

??? what in the wold? When things work I'd see
"Viewer added to list" on the repeater with no problems. Why would it do this instead of opening up as usual? Also, when this happens I have to manually close down the vncviewer.exe from my running processes manually, as it'll just sit in there forever trying to run.

Thanks for any help

[YY]

I try to use a VNC link with the switches -proxy IP:port -ID: myid on the end

I saw two problems at your scribe:
1. "-ID:" is incorrect, the right syntax is just "ID:"
2. You have a space between the directive "ID" & myid, i.e. not acceptable.
ID:myid ---OK
ID: myid --- Error

So your script s/b like this:
vncviewer.exe -proxy IP:port ID:myid

Try if this works.

Be aware: for all parameters/switches that need to be separated with space, just have ONE SPACE between them only, more than one may cause incorrect operation. Also, put NO Trailing SPACE after the scribe, this will provide error too.

[Sdrabor]

Thanks so much! That worked great. Looks like my other piece of the puzzle was that I had both mode I and II checked in the repeater, and once I got mode I removed I connected without any problems.

One other issue still remains. If I close down the viewer before connecting to a server, but after connecting to the repeater, the vncviewer.exe still stays in my processes until I kill it. Is this a bug :x or should it shut down on it's own?


Just for verification for anyone else that runs into this, the correct script for the link is:
"<vncviewer location>\vncviewer.exe" -proxy <ip>:<port> ID:<id#>

so for example, mine looked like:
"C:\program files\VNC\vncviewer.exe" 192.168.1.120:5900 ID:5500

[YY]

If I close down the viewer before connecting to a server, but after connecting to the repeater, the vncviewer.exe still stays in my processes until I kill it. Is this a bug :x or should it shut down on it's own?

Yes, it is NO GOOD with this response. I do know why this happened -- the viewer was waiting for the reponse from repeater. When the viewer registers to a repeater, if the matched ID server doesn't appear in 5 minutes then repeater will remove that viewer from list, and returns a signal to that viewer too. When the viewer receives this signal, it will pop up a windows of "Connection failed - Error reading Protocol Version".
This is OK, but the problem (or the bug) is: if you close down the viewer before connecting to a server, the vncviewer is stilling running in background and waiting. If you can wait for 5 minutes, you can see the above-mentioned pop up.

Looks like my other piece of the puzzle was that I had both mode I and II checked in the repeater, and once I got mode I removed I connected without any problems.
mine looked like:
"C:\program files\VNC\vncviewer.exe" 192.168.1.120:5900 ID:5500

The repeater should be running properly with both mode I and II enabled, I think the problem is your setting. From your script, it shows your repeater using port 5900 as accept.
Why use 5900, but not the default 5901, or other else?
OK, you can choose any port you like, but 5900 is not a good choice, because any VNC connection using mode 1 are using 5900 (default) too.
This may be the cause of your other piece of the puzzle, and why it can be fixed with mode 1 disabled.

[Sdrabor]

That makes sense. I don't have a specific reason for using 5900 instead of 5901, I guess it just ended up being that way, lol.

Thanks for all the input!