The problem manifests itself in Debian GNU/Linux with the following error when the username field is set to 'username@domain-name.localdomain':
Code: Select all
CConnection: server supports RFB protocol version 3.4
CConnection: Using RFB protocol version 3.3
main: your connection has been rejected
Code: Select all
CConnection: server supports RFB protocol version 3.4
CConnection: Using RFB protocol version 3.3
unknown 3.3 security type -6
main: unknown 3.3 security type
The problem isn't the upgrade from UltraVNC Server 1.0.1 to 1.0.2 that was supposed to fix a security flaw with MS domain logon II.
Client VNC programs don't even describe which version of the RFB protocol they support.
The RFB protocol is defined in a document at
http://www.realvnc.com/docs/rfbproto.pdf.
Wikipedia claims there are RFB protocol versions 3.3, 3.7 and 3.8.
Someone with a related, unanswered, question: [topic=8425][/topic]
A patch: http://www.realvnc.com/pipermail/vnc-li ... 45424.html
Possibly related: http://www.realvnc.com/pipermail/vnc-li ... 45425.html
Someone else with the problem: http://linux.derkeiler.com/Newsgroups/c ... 00846.html
Developer discussion: http://www.realvnc.com/pipermail/vnc-li ... 14774.html, http://www.realvnc.com/pipermail/vnc-li ... 15937.html