New modified repeater

[_Ghost_]

Posted at
http://www.gullibet.com/tmp/vnc/repeater_src_2001.rar
http://www.gullibet.com/tmp/vnc/repeater_src_2001.zip
an updated version of the repeater.

This solves the following issue:
- launch viewer (or server) and connect to the repeater with ID:xxx, and keep him waiting (do not connect other side)
- kill viewer (or server) with task manager
- the repeater does not recognize that the connection has been closed
- ...and so the ID xxx remains occupied until the timer closes it

With this modification when the first side of the connection is made, with WSAAsyncSelect is told to report when the connection is closed (FD_CLOSE event), so the CONNRESET is immediately received; when the other side connects the socket is set back to blocking i/o with ioctlsocket.

Not a very elegant solution but it works...

Please everyone test this a lot!

Bye
Davide
[mod=494,1142860841]added http://www.gullibet.com/tmp/vnc/repeater_src_2001.zip for users asked compressed file as .zip because their don't have unrar[/mod]

[redge]

bug or limitation of repeater 1.2.2.1 ?

Not possible to lunch multi users viewers session to same repeater ID number when all partners (client/server) are NAT/firewalled

This limitation is good reason for one to one read/write (support helpdesk)
This solution limit usage of multi viewers NAT/firewalled to one server NAT /firewalled.
(viewer inputs is disabled at vnc server for only show mode for virtual class room, virtual show room)

log of repeater 1.2.2.1
21/01/2006 11:00:30 Viewer 12345678 already exists !
Viewer accept, 192.168.1.32:1268
DBG: remotehost ID remoteport 12345678
21/01/2006 11:00:44 Viewer 12345678 already exists ! <---
21/01/2006 11:13:40 Remove viewer 12345678 0
21/01/2006 11:13:40 Viewer removed from list 12345678

[_Ghost_]

This is a limitation of the repeater architecture, and it has always been in this way for what I know... The connection it's always one-to-one between one server and one repeater with a unique ID.
Bye
Davide

[redge]

Thank you for explanation/limitation of repeater.

I have posted my feature request for repeater V2
[topic=117][/topic]

[Rudi De Vos]

Davide,

Updates has been added to svn
http://sc.uvnc.com/svn2/utravncproxy/

[redge]

please read and click on topic below.
[topic=3782][/topic]

big difficult to do or easy to do request ?

[CBailey]

I'd also like to see the ability of the repeater to record sessions as well. Very frequently, I have reason to want to know what I did in a certain situation. Also, it would be a nice CYA feature, in case a customer tries to claim I did something I didn't, and it would be nice to have a record. I know that recording can be done on the receiving end, but it's much more convenient, and bandwidth-efficient, if it could be done at the server. Would this be hard to implement?

[innovate2000]

Posted at
http://www.gullibet.com/tmp/vnc/repeater_src_2001.rar
an updated version of the repeater.

This solves the following issue:
- launch viewer (or server) and connect to the repeater with ID:spam, and keep him waiting (do not connect other side)
- kill viewer (or server) with task manager
- the repeater does not recognize that the connection has been closed
- ...and so the ID spam remains occupied until the timer closes it

With this modification when the first side of the connection is made, with WSAAsyncSelect is told to report when the connection is closed (FD_CLOSE event), so the CONNRESET is immediately received; when the other side connects the socket is set back to blocking i/o with ioctlsocket.

Not a very elegant solution but it works...

Please everyone test this a lot!

Bye
Davide

Is it possible to access the log in any way? (or listen in on the WSAAsyncSelect conversation)?

[_Ghost_]

I'd also like to see the ability of the repeater to record sessions as well. Very frequently, I have reason to want to know what I did in a certain situation. Also, it would be a nice CYA feature, in case a customer tries to claim I did something I didn't, and it would be nice to have a record. I know that recording can be done on the receiving end, but it's much more convenient, and bandwidth-efficient, if it could be done at the server. Would this be hard to implement?

Well the most bandwidth-efficient way to record a session is to record it directly at the server, so no bandwidth is used... I used with success vnc2swf to record movies in swf format with perfectly quality and good framerate. The only "problem" is that you have to install python+pygame on the server machine.
Honestly at the moment I can't tell if it could be hard to implement it within the repeater.
Maybe simply dumping the server data to a file is enough (.vnc format) ?

[_Ghost_]

Is it possible to access the log in any way? (or listen in on the WSAAsyncSelect conversation)?

The log can be accessed after saving it (File / Save as)...
I don't understand what do you mean with "listen in on the WSAAsyncSelect conversation".

[redge]

bug report repeater 1.2.2.1 (tested on same subnet LAN)

winvnc loop to repeater caused by winvnc built 21 september 2005
with feature [-autoreconnect [ID:????]]
http://sc.uvnc.com/v2/winvnc.exe

pre-requisite
repeater running as service mode
winvnc running as service mode with or without service helper

step to reproduce:
Start... Run...
"C:\Program Files\UltraVNC\winvnc.exe" -autoreconnect ID:30011973 -connect 192.168.1.32

again go
Start... Run...
"C:\Program Files\UltraVNC\winvnc.exe" -autoreconnect ID:130011973 -connect 192.168.1.32

read log of repeater 1.2.2.1
socket() initialized
bind() succeded to port 5901
listen() succeded
THREAD VIEWER: 30356
socket() initialized
bind() succeded to port 5500
listen() succeded
THREAD SERVER: 30360
THREAD TIMER: 30364
Server accept, 192.168.1.32:2246
DBG: remotehost ID remoteport 30011973
04/03/2006 14:40:22 Server added to list 30011973
Server accept, 192.168.1.32:2247
DBG: remotehost ID remoteport 30011973
04/03/2006 14:40:39 Server 30011973 already exists !
Server accept, 192.168.1.32:2248
DBG: remotehost ID remoteport 30011973
04/03/2006 14:40:39 Server 30011973 already exists !
Server accept, 192.168.1.32:2249

... :port+1 ... until net stop winvnc

AsyncSelect: socket 220, event 32, error 0
04/03/2006 14:40:43 Server Removed from list 30011973

[_Ghost_]

Well this is actually not a bug, but a feature... since the repeater accepts only one server/viewer per ID and refuse acccess for duplicates ID, after the first successfull connection (Server added to list 30011973) in fact gives "Server 30011973 already exists ! ". But the winvnc server launched with -autoreconnect keeps repeating the connection forever until its closed, so the duplicate messages.
With older repeater versions you don't see this behaviour just because it did not allow duplicates IDs (duplicates are not added to the queue list) BUT it does not close the connection, so the server/viewer remains stuck in case of duplicates IDs.

[redge]

OK, thank you for the clarification.

[redge]

What are line with <<-----

ReadExact: recv returned -1?
Reading Proxy settings erro <<--- line word broken on the code of repeater
Server accept, 192.168.1.32:3308

error made by command line (winvnc running as service SYSTEM)
"C:\Program Files\UltraVNC\winvnc.exe" -autoreconnect -connect 192.168.1.32


-------------------------------------------------


Server accept, 192.168.1.32:1449
DBG: remotehost ID remoteport 30011973
18/03/2006 00:55:16 Server added to list 30011973
Viewer accept, 192.168.1.6:2007
DBG: remotehost testBID remoteport 30011973
resolving host by name: testBID <<---- value ?
failed to resolve locally.
Unable to connect to destination host, errno=6

finally i'm gonna resolve the problem by myself,
i succesfully connected the javaViewer to the repeater by editing the following line in RFBRepeaterSocketFactory

final String buf2 = "testB";
by
final String buf2 = "";


don't know what is testB used for.

error reported by Neo and Neo420 (same user)
source: [topic=5953][/topic]

[redge]

I have been running this new version and it still occasionally crashes my server. I am running Windows Server 2003 (SP1). When it crashes it goes to a blue screen and then keeps looping (boot > blue screen > restart > boot > ...) the cycle usually keeps up for a while. After manually restarting the server it seems to come up. Any help would be appreciated.

Here is what is in my Application Event Log:

Faulting application repeater.exe, version 1.2.2.1, faulting module unknown, version 0.0.0.0, fault address 0xc9c9c9c9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------

However this occurs more often in my System Event Log:

Error code 1000007e, parameter1 c0000005, parameter2 817a8b41, parameter3 fa047cb0, parameter4 fa0479ac.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

source:
[post=23834][/post]

[bttr]

Is anyone still working on that repeater version? I'd like to polish some things, but I'm only a C/Win32 beginner.

[bttr]

I see. Either this repeater is dead or this is a really "strange" community here.

[CBailey]

I think it's probably as good as dead. PCHelpware has done that. I'm sure we'd be interested in more development of the PCHelpware repeater. I'd love to have it in my Linksys router!

[UltraSam]

No module related to uvnc project is abandonned, even if no one is working on some of them for some time.

As soon as you have the source code you can improve it and make it living...

Feel free to modify/enhance it and share with the not-that-strange community here

[bttr]

I already successfully compiled the sources using Pelles C into a very small binary.

If anyone has proposals for cosmetical changes please post them here and now!

[jksmurf]

I still use repeater. I'd like to see it continued, and updated to help identify errors such as "failed to resolve locally".

This (my) [topic=6829][/topic] requests a similar thing, i.e. Hostnames for Repeater.

Any chance of an update?

k.

[johnney]

hello...I have a problem with an error message when I start Windows (seems to be showing up everytime other programs on my computer initialize at start up). It became very annoying. In uninstalled VNC but it still shows us. My guess is that it has something to do with a registry modification that I did once when I tried to make VNC to be used via http, and I remember I followed the instructions from a website that said to modify somethings with "loop" (sorry I can't remember exactly what it was). How can I get rid of that annoying message? I can't remember where I took those instructions from and I am not a registry expert. Follow this link to see the image (sorry, I could not figure it out how to create a hyperlink here):

http://h1.ripway.com/natyionut/VNC.JPG

[bevtech]

sounds like uvnc didnt uninstall fully from your system.

Use the command line c:\program files\Ultravnc winvnc.exe -uninstall



Source:

http://www.uvnc.com/install/cmdline.html

[johnney]

The fact was that the VNC folder still remained after the uninstal, in the D drive where I usually instal programs. Went there and the folder contained both the uvncserver.exe and winvnc.exe. I deactivated them first using the CTRL+ALT+DELETE command, then deleted the whole folder. Problem solved! thanks Jon...again