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

Connecting from diff PC with same ID breaks initial session?

Post Reply
nom4tter

Connecting from diff PC with same ID breaks initial session?

Post by nom4tter »

Hi there,

while testing PcHelpWare 1.0 I ran into the following issue:

After successfully establishing a connection from 1 server (user PC) to 1 listener (supporter PC) in repeater mode, I wanted to test what happens if another (unexpected) user tries to establish a connection at the same time with the exact same ID (e.g. through a preconfigured pchelpware_server.exe published on a website without contacting the supporter first). It seems that this breaks the initial session without warning and resets all connections (ECONNRESET in repeater log).

Can someone confirm this? If so, is there a workaround?

I would have expected that the second connection is refused by the repeater to ensure a stable initial session. This could save the supporter some hassle with (dumb :wink:) users.
Post Reply