UltraVNC

Thank you very much - that was exactly what I was looking for! I was confused with the pchelpware issue because the info for the repeater is titled "About UltraVnc Repeater" but the actual content says "PcHelpware Repeater Rel 1.00".

Rudi,

Thanks for this latest update - after some testing, I'd realized that the repeater was what changed the behavior with regards to who had to connect first. I'm using the pchelpware repeater rel 1.00, since the repeater on the UltraVNC download page is a command line version only that I can't ...

Ok, after more testing, this only works when the viewer initiates the connection first. If the server goes first, I get the DSMPlugin error. Is this expected behavior? I don't think it used to work like this, but I could be wrong.

- Daniel

Rudi,

The change in id position seems to do the trick - I no longer get the proxy error at the repeater when the server connects in. However, I am getting a DSM plugin error. With regards to my second question in that other post, if my viewer is using the NoReg version of 1.2.2, what version is the ...

Rudi,

Thanks for the response - I changed the Hosts line to this:

-plugin -connect xxxx.xxxx.xxxx:8089 -noregistry -id 4321

I still see the same issue - as soon as I run the server side sc exe, I see this in the log:

Repeater for Rel1.0.0 of PcHelpware
socket() initialized
bind() succeded to ...

No matter what I do, using this creator I cannot get an exe that works with any repeater - at this point, I'm sure it's user error but I can't figure it out. Any help out there? This is the repeater log:

Repeater for Rel1.0.0 of PcHelpware
socket() initialized
bind() succeded to port 8088
listen ...