Example:
Server listening on port 1000
Server LAN IP: 192.168.0.23
Connect to the server on 192.168.0.23
Server establishes a PPPoE connection to the internet, gaining an internet IP eg: 196.41.22.44
UltraVNC Connection is Lost upon PPPoE connection establishment or loss.
Its not a big deal, but rather annoying.
Is there some way to keep UVNC Connections Alive? They die quite often on my LAN, which should not be.
After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
[BUG] Connection lost (via LAN) when PPPoE connection change
Re: [BUG] Connection lost (via LAN) when PPPoE connection ch
This will happen on UVNC 1.0.9.x ... I suppose you are using one of these version.
It is because these version implement a feature ... auto re-bind the IP if there is a change, so establishing a PPPoE will triggger this operation. Unfortunately this requires a restart of the uvnc service, thus all active connection will be dropped.
Of cource, the auto-rebinding of new IP is an usable & necessary feature, but the present operation hadn't taken the consideration of the impact of established connection.
For you situation, before any new version is released that have this problem solved, one possible way is to switch back to the 1.0.8.2, which doesn't have the above-mentioned feature.
Of course, there are a lot of changes/improvements from 1.0.8.2 to 1.0.9.x, you should take a look on them to see if there any impact to your configuration if going back to an old version.
It is because these version implement a feature ... auto re-bind the IP if there is a change, so establishing a PPPoE will triggger this operation. Unfortunately this requires a restart of the uvnc service, thus all active connection will be dropped.
Of cource, the auto-rebinding of new IP is an usable & necessary feature, but the present operation hadn't taken the consideration of the impact of established connection.
For you situation, before any new version is released that have this problem solved, one possible way is to switch back to the 1.0.8.2, which doesn't have the above-mentioned feature.
Of course, there are a lot of changes/improvements from 1.0.8.2 to 1.0.9.x, you should take a look on them to see if there any impact to your configuration if going back to an old version.