Reconnect option on failed try...

louk · Post by **louk** » 2004-06-08 13:50

When a connection is to be established from the viewer to the server by the normal way and connection can't be produced, a popup says "Failed to connect to server!". To try again, it is required to move to an other window and double click on a server icon or even to procede through the start buttom and Ultravnc programm group to restart the viewer again. This is quiet nerving.

It would be more convinient, when an option for displaying the connection panel again to may be modify the settings or just retry because the server was not up yet, would be available. The failure message box should contain the hint as yet seen and two buttoms, one "Reconnect" and one "Cancel".
Reconnect opens the connection dialog again.

redge · Post by **redge** » 2005-07-10 23:30

I agree this feature too

very usefull for bad network connection.

pgmoney · Post by **pgmoney** » 2005-07-11 02:42

louk wrote:When a connection is to be established from the viewer to the server by the normal way and connection can't be produced, a popup says "Failed to connect to server!". To try again, it is required to move to an other window and double click on a server icon or even to procede through the start buttom and Ultravnc programm group to restart the viewer again. This is quiet nerving.

It would be more convinient, when an option for displaying the connection panel again to may be modify the settings or just retry because the server was not up yet, would be available. The failure message box should contain the hint as yet seen and two buttoms, one "Reconnect" and one "Cancel".
Reconnect opens the connection dialog again.

I thought that had been fixed already... this mod took all of about 20 minutes to do so there may be bugs, but if you want to try it the link is below.

http://www.advantig.com/files/vncviewer101a3.zip

I think thats enough mods from me for one day. Have to get back to work on a LinkSys project.

louk · Post by **louk** » 2005-07-11 08:01

Many thanks pgmoney. V 1.0.0 RC20.2 didn't have it, but in your version of the viewer (V 1.0.1 Advantig mod 3) this feature is implemented (a bit different from the proposal - but also ok. It is not a two button solution. The connection panel is popped up in addition to the failure info message).

So you can place a checkmark on this point and proceed to the next

.

redge · Post by **redge** » 2005-07-17 03:35

pgmoney or any devs,

pedja wrote:I noticed that UltraVNC viewer has problems if remote computer is brutally disconected from internet.
It cannot realize that connection is broken and it stalls.
On XP I do not get blue screen, but application does crash in such situations.

source: (unmodified)
http://www.teamviewer.com/forum/topic.asp?TOPIC_ID=113

I try it and have same issue.
There any fix that checking every x seconds for know if session winvnc is live (I know default Ping with ICMP can't be used, blocked at firewall)
but for communicate, there a way for check this anyway like *nix style request traceroute over Unpredictable UDP port.

workaround:

wait dead socket timeout close itself (180 sec =3min)
TCP/IP have a default timeout before reject a packet (time too long) ?

request: (Now fail)
any update possible to check this behavior if happen to close viewer and ask re-connect or cancel that can save time ?

pgmoney · Post by **pgmoney** » 2005-07-17 05:01

redge wrote:pgmoney or any devs,

pedja wrote:I noticed that UltraVNC viewer has problems if remote computer is brutally disconected from internet.
It cannot realize that connection is broken and it stalls.
On XP I do not get blue screen, but application does crash in such situations.
source: (unmodified)
http://www.teamviewer.com/forum/topic.asp?TOPIC_ID=113

I try it and have same issue.
There any fix that checking every x seconds for know if session winvnc is live (I know default Ping with ICMP can't be used, blocked at firewall)
but for communicate, there a way for check this anyway like *nix style request traceroute over Unpredictable UDP port.

workaround:

wait dead socket timeout close itself (180 sec =3min)
TCP/IP have a default timeout before reject a packet (time too long) ?

request: (Now fail)
any update possible to check this behavior if happen to close viewer and ask re-connect or cancel that can save time ?

I thought there was a time-out in there somewhere... how long did you wait for it to fail? I'm currently doing some extended testing on Remote Engineer and don't have UVNC installed but I'll install it later this week or next weekend and see what I can find.

redge · Post by **redge** » 2005-07-17 13:46

I thought there was a time-out in there somewhere... how long did you wait for it to fail?

3 min, the default timeout socket closing itself and viewer

until this delay, unpossible to re-connect to same host even the host is already onnected before this timeout expired.
valid for any vncviewer flavor

the advantage of RealVNC viewer 4.1.6 over UltraVNC viewer 1.0.1 show a clear message:
read: Connection reset by peer (10054)
Do you wish to attempt to reconnect to hostname?
Yes No

you click Yes, and you are quickly connected without put again the password

the need from most users that seriously miss on UltraVNC viewer

pgmoney · Post by **pgmoney** » 2005-07-17 14:57

Ok, I understand now... you don't want to wait for the timeout. That makes sense.

redge · Post by **redge** » 2005-08-07 06:03

realvnc 4.x.

vncviewer -autoreconnect by default active ! can be disabled as an option.

UltraVNC

Reconnect option on failed try...

Reconnect option on failed try...

when lost connection, need question reconnect or cancel ?

Re: Reconnect option on failed try...