[solved] Random Failure

[Galaxiom]

We originally had problems with the olded version and it was suggested that we upgrade.

[post=63156][/post]

I've now updated to 1.06.5 but the problem persists. This time there is no error message in the Windows logs. It has occurred on at least two different servers this time.

We have been using UltraVNC for several months and the problem appears to have developed recently.

We are using Novell Netware Client for Windows (Version 6) to log on so perhaps it is something to do with this. There have been no recent changes to Novell. I also noticed with the new version of UVNC that the Novell login screen does not automatically initiate a refresh of the view either when it loads after pressing CtrlAltDel or as the password is typed. This was not previously the behaviour. We also use McAfee AV.

The symptom are the viewer suddenly closes and it is impossible to reconnect to the server. It appears the connection might be failing when the server automatically locks the logged on session after the timeout. However I don't think this is always the case.

On the client a thin bar stays present at the top of the monitor and the viewer exe continues running. Subsequent attempts to connect open another viewer session with the Statistics window but not the failure to connect message.

Starting the viewer again after stopping the viewer process in the Task Manager results in the usual message. Error reading protocol version.

Restarting the server uvnc service does not fix it. The two winvnc executables running on the server must be terminated and the service started again. I don't understand why there are two but one uses much more memory than the other.

In normal running they are 15712 KB and 3072 KB
In error after restarting the service without killing the processes they use 2920 KB and 912 KB.

[Rudi De Vos]

Please check if it still happen with 108 ( pre-release)

[Galaxiom]

Will try the 108 prerelease later today.

Today the symptoms have been different.

Viewer does not shut down but just sits there with the last working screen displayed. Seems to do it when viewer is left open and unattended for a few minutes while user is focused on another window. Did this twice in about twenty minutes.

This time was it definitely not associated with the remote computer locking the session as it happend while the session was still active.

[Galaxiom]

Haven't had a chance to try 1.08 yet.

However I can report that the behaviour is the same on a Windows 2003 server that does not have the Novell login installed.

[Galaxiom]

Installed Version 1.08
All good now.

Thanks

[smallfish]

so good, This version is looking for a long time.Thanks