Why does autoreconnect doesn't work?

[Ween]

Hi,

I am trying to use autoreconnect but it doesn't work for me.
Both server and viewer runnning Win2000 SP4 and running the
RC18 version.

In the server I run:
winvnc -autoreconnect -connect <viewer ip>

In the viewer I run:
vncviewer <server ip> /listen /password <password>

However, when there is a line drop I need to connect to the server again manually.

I get no errors and I can see that the viewer is listening to port 5500 (I tried other ports but it doesn't work either).

What can I do to solve the problem?

Thanks

[coolbreeze22]

I see that when the -autoreconnect is used then when the server kills the individual client the connection is not killed.
Is this all reconnect does?

[byteboon]

Autoreconnect means that when the viewer is closed (or loses connection), it will automatically try a reconnect. Works when the viewer is in listen mode only.

Internally, autoreconnect just stores the information from -connect and uses that to try a *single* reconnect immediately after the viewer disconnects.

[Ween]

Internally, autoreconnect just stores the information from -connect and uses that to try a *single* reconnect immediately after the viewer disconnects.

Is this measns that if the server had a problem
and killed the client, there will not be a resume in the connection and the client will need to connect manually? (because what I have now is autoreconnect from the viewer side when the viewer has a problem he reconnects automatically).

[byteboon]

It means that if the "problem" is that there is a loss of connectivity, then the autoreconnect may fail because it is triggered *immediately* and *singly* after the client is disconnected from the server.

It *does not* mean that the server will reconnect when the connection becomes available again.

Basically, you can close the viewer and the server will start the session again. This lets you "reset" the session if it starts getting slow / messed up / etc.

[Ween]

Ok, Thanks.

Now I understand how autoreconnect works.

I am thinking about writing a small batch file
which will check if the vncviewer process is active and will restart it every x minutes (by using task scheduler).
I think this will solve the problem.

[coolbreeze22]

well the functionality for autoreconnect is now cleared up. Unfortunatly it is not the functionality I'm looking for.

I'm going to try and create a vb 6.0 program that monitors many vncviewer connections and reconnects one or many of them when they become disconnected.
This could get hairy. Any ideas or warnings?

[Ween]

I wrote a simple batch script that does the job:

@echo off
tasklist /fi "IMAGENAME EQ vncviewer.exe" > tmptask
find "vncviewer.exe" tmptask > nul
if errorlevel 1 goto vnc
goto done

:vnc
del tmptask
c:
cd\
cd program files
cd ultravnc
start vncviewer xx.xx.xx.xx /password yy
cls

:done
del tmptask
cls

You should run this script using task scheduler every x minutes.
If the process doesn't exist the script will run it...

This will work for WinXP. For Win2K you will need to do minor adjustments.