ultravnc
Document IPv6 syntax for the client/viewer
Hello, Maybe i've missed something obvious, but i can''t find any documentation on the syntax to use in the client for connecting to an IPv6. Also Google ultravnc ipv6 didn't show syntax, only changelogs.
Using V1.6.4.0 on W11 for client, same on W10 for server.
First, went to the security tab to check "Use IPv6" and save.
Then i've tried simply inputting the IP as-is like: fd00:abcd::1234:1 and got an error. Thought maybe the double :: was interpreted as port separator so tried: fd00:abcd:0:0:0:0:1234:1 Then tried using quotes: "fd00:abcd::1234:1" By Google found some other client (TrollVNC for IOS) using braces so tried this too but same: [fd00:abcd::1234:1]
Although the IPv6 connection itself seems ok, as putting the address in hosts file and using the hostname it works flawlessly. (i used a different hostname with IPv6 only to ensure it wouldn't fallback to IPv4, and confirmed with netstat it's really an IPv6 connection).
Would gladly do some tests if needed, found some things to enable logs for server side but not for client side.
I'm current not working on ipv6. As soon as some testing need to be done i will conact you Thanks
Using V1.6.4.0 on Win11 for client, UltraVNC Viewer cannot connect via IPv6， Status: Failed to connect to server! “Remote Ripple” on Android client connects to Ultra VNC server normally.
After writing the IPv6 address to the Windows host file, the VNC viewer can connect normally！
version online that should support the ipv6 as viewer input. Can someone test this. https://uvnc.eu/download/1642
Supported formats:
[2001:0db8::1] - IPv6 with default port 5900 [2001:0db8::1]:0 - IPv6 with display 0 (port 5900) [2001:0db8::1]:5901 - IPv6 with port 5901 [2001:0db8::1]::5901 - IPv6 with explicit port notation Backward compatibility maintained:
hostname:display hostname::port 192.168.1.1:0
Works perfectly!
Tested on my network (W10 server, 1.6.4.0 and W11 client with new 1.6.4.2), all those syntaxes now works fine. Same as IPv4 still works also, backward compatibility confirmed.
IPv6 connection to VNC service is now fully resolved after testing the new v1.6.4.2 . Using IPv6 domain names is also fine! Note that the domain name must include [ ].