Originally Posted by burdi01
What about using an other VNC such as TigerVNC?
And what about accessing the VM via VB's RDP?
Just my 2 cents.
Trying another VNC is next on the trouble shooting list, as this only happens when I VNC in. If it's the tightvnc client and not the KDE desktop sharing server (which I'm currently using), this might work. I'm also wondering if tightvnc's own server might help instead.
Hmm...never thought of using RDP to get into the VM instead of going through the linux box. I have the network on the VM set to NAT, I may have to set it to bridged so it is accessible from outside of the host. I wonder if I can forward the rdp port from the VM to the host instead? I currently have ports 1433 (mssql) forwarded to the host so I can access mssql from other machines on the network, and that works fine. Definitely going to give this some thought and play with it, that is a most excellent idea!