UltraVNC

OK. I just decided to try a totally different computer for the Repeater. It works!! The only problem is that even when a viewer hasn't initiated the connection, it goes to active. It didn't use to do this before. If anyone has a solution for this, that would be great. If not, I'm happy that it is ...

The only difference than what was recommended above is on the viewer I am using:
vncviewer -proxy LocalIPofServerRunningRepeater:5901 ID:100

Here is the log file from the repeater:

Repeater for Rel1.0.0 of PcHelpware
socket() initialized
bind() succeded to port 5901
listen() succeded
socket() initialized
bind() succeded to port 5500
listen() succeded
accept() connection
Viewer added to list 102
ID added 102


This is just after a ...

Yes, we have upgraded to a new repeater due to a server crash. I tried what you recommended and it still doesn't work. I opened the client on my end then had the client run the .exe and it still immediately disappeared.

Like i said, it is getting at least to my router as I see the traffic ...

Thanks for the reply. Unfortunately, I get the exact same response. I have made the change in the helpdesk and the viewer. On the remote client, I double click the .exe and it still just flashes and disappears in the system tray.

Hello, I have a few questions. We were able to get this working fine with the help of Redge in the past. Now all of a sudden it isn't working. When the client double clicks the .exe, it goes into the system tray and immediately disappears. It no longer says, trying for 5 minutes.

Here is how we ...

It works, but not correctly. I will try to use the public repeater after the holiday. Have a Merry Christmas!

I changed it to 5500 and 5901. I now get it automatically connecting when the user initiates the connection.

Redge, you there? Anyone have any thoughts on this?

I have SC working with multiple ID's and using a repeater. But when the client makes a connection, it no longer waits for the viewer to connect. It immediately says connected. I can then open the viewer and connect, but I need it to wait until I have initiated the connection on the viewer side ...

It seems to work, but the connection on the client side automatically connects, even if the viewer hasn't been initiated. All of my settings are identical to your post in the .exe and in the viewer. I have the viewer as 5901, and the server as 5500. I have Mode I and II checked. I've tried ...

Sorry for the delay Redge. Thanks for the new version, but it still does the same thing. I ran the distributor.exe and went to settings. I put 5500 in both listen areas for viewer and server. I have tried it with 443 checked and unchecked, and I unchecked dynamic IP service. Restrict Access to ...

Thanks Redge. I was able to get it working several weeks ago. But now, it is not working. I know it worked, so the .exe should be fine as it hasn't changed. I think the problem is with the repeater. When the repeater is running, the client automatically says it is being viewed even if I haven't ...

We are trying to set it up so that you can open any ID from any computer. We figured we would have to use a Repeater on computer to act as the server between the workstations on the network and outside requests. Here is what happens when we have the repeater running. The client on the outside double ...