Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Possible Bug: UVNC autoreconnect

Post Reply
M.e.M.O.
8
8
Posts: 10
Joined: 2008-10-27 13:46
Location: Istanbul

Possible Bug: UVNC autoreconnect

Post by M.e.M.O. »

Hello ,

Firstly I want to thank you for this awesome work. I have been using it for quite some time now, without much problems. Many of them I was able to solve. But one thing , I have no luck so far :

I have been running UVNC servers in service mode with

Code: Select all

service_commandline=-autoreconnect ID:1234 -connect xxx.net:1234 
This had been working almost a year by now. But after upgrading to 1.0.8.2 , server seems to be trying to connect to repeater , but when I try to connect to the repeater, it becomes active, then locks viewer. After that, server stop autoreconnecting back to the repeater with these in the log :

Code: Select all

.\vncmenu.cpp : ############### Usernames change: old="username", new="username"
Sat Feb 20 09:05:12 2010
.\vncclient.cpp : PostAddNewClient I
.\vncservice.cpp : PostAddNewClient failed
.\vncclient.cpp : ~vncClient() executing...
.\vncclient.cpp : deleting socket
.\vsocket.cpp : closing socket
Sat Feb 20 09:05:14 2010
.\vncservice.cpp : @@@@@@@@@@@@@ 
I connect to another PC on the same network, and try to connect server with direct connection through IP , it askes for password, then server starts sending connection requests to the repeater and I can connect for a couple of times. I sort of pinch it with direct connection and it wakes back up :-D

I just downloaded and put just vncserver.exe (1.0.6.5) and renamed 1.0.8.2 for seeing if it is about server exe or not. It's just new I will inform you if it works or not.
I need some help on pointing where I should start digging this problem.
Any ideas would be apreciated.
Last edited by M.e.M.O. on 2010-02-22 10:22, edited 1 time in total.
M.e.M.O.
8
8
Posts: 10
Joined: 2008-10-27 13:46
Location: Istanbul

Re: Possible Bug: UVNC autoreconnect

Post by M.e.M.O. »

More news :

1.0.6.5 keeps crashing.

Any ideas to start where to look?
Last edited by M.e.M.O. on 2010-03-01 15:48, edited 1 time in total.
M.e.M.O.
8
8
Posts: 10
Joined: 2008-10-27 13:46
Location: Istanbul

Re: Possible Bug: UVNC autoreconnect

Post by M.e.M.O. »

installing version 1.8.0 helped.
Why does 1.8.0.2 fail on autoreconnect feature?
redge
1000
1000
Posts: 6797
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Re: Possible Bug: UVNC autoreconnect

Post by redge »

what is your repeater version and host is linux or windows ?

i won't have problem of autoreconnect with ID and repeater is on linux.
http://storage.ultravnc.info/repeater014_1.tgz

the only anoying problem is the winvnc disconnect with server running as application, but i can connect viewer again.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
M.e.M.O.
8
8
Posts: 10
Joined: 2008-10-27 13:46
Location: Istanbul

Re: Possible Bug: UVNC autoreconnect

Post by M.e.M.O. »

Repeater is on linux (Fedora) . Version 0.14.

I have been using it untill version 1.0.8.2 without any problems.

I am familiar with this connect/disconnect problems the repeater has.

Something like :
Server sends connection request to repeater , waits like 30 seconds for a client to connect.
Disconnects, and sends connection request again.

When you try to connect the server through repeater, its shows a confirmation dialog , when you click ok you connect.
But , when you connect, if the server drops the timeout and disconnect before you click "ok", viewer crashes and freezes the screen, even sometimes crashes repeater. Only way to "revive" the repeater is to end its process with "kill -9" as root. No other way :/

edit : I have edited the shell script I used to run repeater. Now it doesn't delete daily logs and compresses them (you know how huge they become after a couple of days run ) . This simply means I can provide more logs if you want.
Last edited by M.e.M.O. on 2010-03-17 13:46, edited 3 times in total.
Post Reply