Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/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://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/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://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Search found 2 matches
- 2011-06-09 21:30
- Forum: Olders
- Topic: WinVNC binds to the wrong interface
- Replies: 3
- Views: 5377
Re: WinVNC binds to the wrong interface
Thanks Rudi, I was ignorant to that fact and searching for anything that stood out :) At this point all I have to go on is the following log entry, which is produced when I run "vncviewer.exe -loglevel 10 -console". It's printed to the log after I hit cancel (the process never connects): vsocket.cpp ...
- 2011-06-09 16:57
- Forum: Olders
- Topic: WinVNC binds to the wrong interface
- Replies: 3
- Views: 5377
WinVNC binds to the wrong interface
Regarding the problem mentioned in the following thread: http://forum.ultravnc.info/viewtopic.php?p=84978#84978 My host OS is Windows 7 Professional x64 The server is UltraVNC Server 1.0.9.6.1 I get pretty much the same output in the logs that l2onin pasted in the last post in the above thread, and ...