[Problem] SC <-> Repeater Mode II <-> UltraVNC Viewer

[oxygene.core]

Hi all.
I have this configuration:

PC#1: 192.168.0.10 - Running Repeater (ports keeped the same, option "Restrict access to server port" is set to 0)

PC#2: 192.168.0.9 - Running viewer:
Command for using repeater:

Code: Select all

vncviewer.exe -autoscaling -proxy 192.168.0.10:5901 ID:1234

PC#3: 192.168.0.10 (it is PC#1) - Running SC client

Code: Select all

[HOST]
Use repeater at 192.168.0.10:5500
-id 1234 -connect 192.168.0.10::5500 -noregistry 

[HOST]
Use direct connection to 192.168.0.9
-connect 192.168.0.9::5500 -noregistry 

PC#4: 192.168.0.3 - Running SC client with the same exe as PC#3

When I'm using direct connection to PC#2 (Viewer) - second [HOST] option on SC- , there are no problems for multiple client connections at the same time (Viewer running through Start > All Programs > UltraVNC > Run UltraVNCViewer).

When I'm using first option - running repeater - I got problem. First client connects ok, but when second tries to connect too, Viewer closes connection to fits client, and no one gets connection at all. After Viewer automatically reconnects to Repeater, it again can accept connections, but again only one per time.

How can I use multiple SC connections when using repeater scheme?

[kaldag]

How many ID's do you have on your repaeater??

Ken

[oxygene.core]

Thank you for reply, Ken.

I have one Viewer connected to repeater with ID:1234 and two clients who want to connect to it through repeater concurrently.

[kaldag]

Try adding more ID's to the repeater and making the change to the host line in SC.

Ken

[oxygene.core]

I think I've got an idea. We should create connection for both server and viewer for every new session?
It would be nice if repeater could notify registered Viewer on inbound server connection so that the viewer could create new connection to repeater and register new ID. Or even more cool - repeater by itself would create new connections (on inbound server connections) to registered viewer?
But I think this functionality would already implemented into PCHelpware you told in other topic.

[oxygene.core]

I think that repeater autodialing to registered Viewer is very important thing in our case.
Also as programmer I think that it is interesting solution, though this functionality somekind may extent from simple repeater.
Should I post it as a feature request?

[oxygene.core]

When I'm using first option - running repeater - I got problem. First client connects ok, but when second tries to connect too, Viewer closes connection to fits client, and no one gets connection at all. After Viewer automatically reconnects to Repeater, it again can accept connections, but again only one per time.

Active connection breaks after another client tries to connect on the same (already used in that session) ID. This is bug?
What should I do in order to walk around this problem? I don't want existing session to disconnect if there is attempt to connect to already used ID.

[bevtech]

I have noticed that as a problem even in the pchelpware repeater. If you hit the same id you lose your connection.. I am not sure if that was intended or a bug