A few additional points:-
1/ If the user specifies a non-FQDN computer name the UltraVNC client could use either the connection-specific DNS suffix (such as might be issued by a DHCP server) or the domain suffix of a domain-connected workstation. (I am thinking might be better if used in conjunction with an administratively pre-authorised list of connection-specific DNS suffix)
2/ This may require the use of a split DNS. This might be a bit of an administrative nightmare if there are a lot of entries needed. It is not an insurmountable obstacle though.
3/ Assuming one or more discovery method is used it would be preferable to display a warning/informational dialog to the user to confirm that a UltraVNC Repeater was discovered and will be used for the connection. The user should then be offered the chance to terminate the connection (default), allow this connection but keep warning, or never show the warning again for connections to this server. Again administrative override and/or disabling of the warning would be highly desired.
Note: To my mind these are fairly trivial features that can be added to the client without modification to the VNC protocol, server or repeater. That said I am aware that the changes are beyond my ability (trivial is a relative term!) and defer to the very kind developers as to whether this is something that they should spend their time on.
