ports/174976: virtualbox 4.2.6: VNC not working

[Martin Birgmeier]

>Number:         174976
>Category:       ports
>Synopsis:       virtualbox 4.2.6: VNC not working
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 04 19:10:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Martin Birgmeier
>Release:        FreeBSD 8.2.0 release
>Organization:
MBi at home
>Environment:
FreeBSD hal.xyzzy 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Sat Nov  3 09:16:25 CET 2012     root at hal.xyzzy:/z/OBJ/FreeBSD/amd64/release/8.2.0-nfse/sys/XYZZY_SMP  amd64
>Description:
Up till virtualbox 4.1.22, I have been starting headless virtual machines using something like

    VBoxHeadless -n -m 9001 --startvm 'FreeBSD 7 i386 (v901)'

Now, neither the -n nor the -m command line options are supported. However, in the VirtualBox manager command, I set the "server port" on the "remote display" tab to 9001.

Now, when starting, VBoxHeadless displays:

    04/01/2013 19:49:09 Listening for VNC connections on TCP port 9001
    04/01/2013 19:49:09 Listening for VNC connections on TCP6 port 5900
    VRDE server is listening on port 9001.

So first, the old bug where the TCP6 port was not set has resurfaced.

Aside from that, the second problem is that using vncviewer (from net/tightvnc) does not work at all: issuing

    vncviewer hal:9004

regardless of the setting of "authentication method" in "remote display" results in being asked for a password, and no possible supplied password works, always returning

    password check failed!

This happens even if the "authentication method" is set to "Null".

>How-To-Repeat:
See the description.
>Fix:
At least the TCP6 port problem has been solved before in the port.


>Release-Note:
>Audit-Trail:
>Unformatted: