Page 1 of 2 12 LastLast
Results 1 to 50 of 62

Thread: External VNC viewer?

  1. #1
    Join Date
    Aug 2008
    Posts
    2

    Default External VNC viewer?

    I have Java issues and would like to use an external vncviewer (Win32) to connect to a VM. I tried to connect to VMID 101 with the command line:

    vncviewer 192.168.0.60:101

    got an connection refused error and turns out that there's not even a VNC server listening (at port 5900). Is is possible to use an extern vnc viewer to connect to the VM's?

  2. #2
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    no, there is no vnc server listening, but you can start a server with:

    Code:
    nc -l -p 5900 -c "qm vncproxy VMID PASSWORD"
    After that you can connect one time (because PASSWORD is a one time ticket).

    - Dietmar

  3. #3
    Join Date
    Aug 2008
    Posts
    13

    Default

    I'm also interested in solving that issue.
    I've tried the solution above but all I got is: "Not a valid VNC server".

    I've tried also to forward a vnc connection from a kvm machine.
    I've used socat (piping from /tmp/qemu-server-vnc-ID.socket to tcp socket) and been close to success: vnc viewer saw a server.
    But I can not figure out what password should use to authenticate.
    BTW "change vnc password" does not work in QM.

    Best regards
    Pawel

  4. #4
    Join Date
    Aug 2008
    Posts
    13

    Default

    OK, that works for kvm, so socat is not needed.
    But what to do to get external vnc viewer to work with ovz? The solution above does not work ("Not a valid VNC server").

    And just out of curiosity: how to pass authentication when trying to connect to the unix socket: /tmp/qemu-server-vnc-ID.socket?


    Best regards
    Pawel

  5. #5
    Join Date
    Aug 2006
    Posts
    9,888

    Default

    Quote Originally Posted by pjo View Post
    OK, that works for kvm, so socat is not needed.
    But what to do to get external vnc viewer to work with ovz? The solution above does not work ("Not a valid VNC server").

    And just out of curiosity: how to pass authentication when trying to connect to the unix socket: /tmp/qemu-server-vnc-ID.socket?


    Best regards
    Pawel
    for openvz container just connect remotely via ssh, why do you want to use vnc here?
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  6. #6
    Join Date
    Aug 2008
    Posts
    13

    Default

    Quote Originally Posted by tom View Post
    for openvz container just connect remotely via ssh, why do you want to use vnc here?
    I can image such a situation: one can create and start a container from web interface so the container network is not configured yet.
    And provided vnc viewer can't be started (e.g. problems w/ java plugin version).

    regards
    Pawel

  7. #7
    Join Date
    Aug 2006
    Posts
    9,888

    Default

    Quote Originally Posted by pjo View Post
    I can image such a situation: one can create and start a container from web interface so the container network is not configured yet.
    And provided vnc viewer can't be started (e.g. problems w/ java plugin version).

    regards
    Pawel
    in such a case connect via ssh to the Proxmox VE and then:

    Code:
    vzctl enter VMID
    the host can access all containers without the need of a running network.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  8. #8
    Join Date
    Aug 2008
    Posts
    2

    Default

    Quote Originally Posted by dietmar View Post
    no, there is no vnc server listening, but you can start a server with:

    Code:
    nc -l -p 5900 -c "qm vncproxy VMID PASSWORD"
    After that you can connect one time (because PASSWORD is a one time ticket).

    - Dietmar
    Thanks, works great.

    wacked.

  9. #9
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    Quote Originally Posted by pjo View Post
    OK, that works for kvm, so socat is not needed.
    But what to do to get external vnc viewer to work with ovz? The solution above does not work ("Not a valid VNC server").
    We use vncterm for that:

    Code:
    vncterm [VNCOPTS] [-c command [ARGS]]
     
    #example:
    vncterm -c vzctl enter VMID
     
    vncterm -rfbport 5900 -passwdfile FILE -timeout 20 -c vzctl enter 104
    that way you can proxy any application.

    - Dietmar

  10. #10
    Join Date
    Aug 2008
    Posts
    13

    Default

    Quote Originally Posted by dietmar View Post
    We use vncterm for that:
    [...]
    - Dietmar
    Great! It works much faster. Thanks a lot.
    BTW Where I can learn more about vncterm? Its man page is not informative very much

  11. #11
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    The source code is available at ftp://pve.proxmox.com/sources/

    - Dietmar

  12. #12
    Join Date
    Jul 2008
    Posts
    17

    Default

    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword

  13. #13
    Join Date
    Sep 2008
    Posts
    12

    Default

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    What about that is configurable for my local settings, assuming I use the user 'root' for Proxmox, 'administrator' for all the VMs, and a single password for them all? Also, what would I type into my terminal server client (the app of the same name in Ubuntu) to access the VMs?

  14. #14
    Join Date
    Jul 2008
    Posts
    17

    Default

    Quote Originally Posted by djbon2112 View Post
    What about that is configurable for my local settings, assuming I use the user 'root' for Proxmox, 'administrator' for all the VMs, and a single password for them all? Also, what would I type into my terminal server client (the app of the same name in Ubuntu) to access the VMs?
    Each line added to the file represents a Proxmox VE virtual machine that you want to be able to connect to externally. In my example 101 through 108.

    The first column is the port you want to listen on for a particular VM (penultimate column). That is of course configurable.

    The last column is the password you want to use to connect to the VNC server. This has nothing to do with users or passwords on the virtual machine. It's best to think of the VNC server as simply a virtual monitor, keyboard and mouse. Like any monitor keyboard and mouse, the VNC server knows nothing about what OS your running or its users so this password has nothing to do with the users or passwords on your virtual machine. This password is simply used to access the VNC server (as if your keyboard and mouse required a password to use).

    Don't use Terminal Server Client for VNC servers. It just runs vncviewer which is really, really slow. Use Vinagre instead which I think is a standard Gnome app. In the "Connect" dialog use the hostname or IP of the Proxmox VE server (not of your VM) and the port for the VM you set up in the inetd.conf file. When it connects Vinagre will ask you for the password for the VNC server which is the one in the inetd.conf file. Once you're connected you will see what you normally would see on a monitor-- a login prompt or login dialog depending on the OS on the VM.

    It's worth noting that the OS sees this as its regular monitor and keyboard so if it's configured to blank the screen after a period of inactivity you may need to hit a key to see anything at all.

    It's also worth noting that just like a regular monitor, keyboard and mouse the VNC server has no concept of cut and paste. You can't cut something on your local machine running Vinagre and paste it into your VM. You can of course cut and paste entirely within the VM as usual. So if cut and paste is something you need you should use Remote Desktop for Windows virtual machines or some other method for other virtal machines.

  15. #15
    Join Date
    Jul 2008
    Posts
    17

    Default

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    I should have mentioned that I don't think inetd is installed on Proxmox VE by default. So to use this you need to run
    apt-get install openbsd-inetd
    on the Proxmox VE server as root.

  16. #16
    Join Date
    Nov 2008
    Posts
    46

    Default

    Anyone ever try xinetd, since it is already installed in the PVE?

    I tried to create a file in /etc/xinetd.d:

    service vnc-200
    {
    socket_type = stream
    protocol = tcp
    port = 9000
    wait = no
    user = root
    server = /usr/sbin/qm
    server_args = vncproxy 200 windowsvnc
    }

    Then, from a Win box, I try to access the VM via 192.168.x.y:9000, but I get a connection refused.

    Any suggestions?

  17. #17
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    There seems to be a confusion about the installed inetd.

    By default, we install 'openbsd-inetd'

    - Dietmar

  18. #18
    Join Date
    Mar 2009
    Posts
    13

    Default

    BTW, I have some java issues as well, but only with one of my recently installed proxmox boxes. I've installed 2 machines, both with the same iso, and one of them works great, but the other one has no java vnc viewer (laptop with ff3, sun's java, ubuntu). Reinstall did nothing. Anyone else has these problems? I can work around them but the java vnc viewer is useful at times.

    Thanks

  19. #19
    Join Date
    Apr 2009
    Posts
    35

    Default

    Quote Originally Posted by pjo View Post
    I'm also interested in solving that issue.
    I've tried the solution above but all I got is: "Not a valid VNC server".

    I've tried also to forward a vnc connection from a kvm machine.
    I've used socat (piping from /tmp/qemu-server-vnc-ID.socket to tcp socket) and been close to success: vnc viewer saw a server.
    But I can not figure out what password should use to authenticate.
    BTW "change vnc password" does not work in QM.

    Best regards
    Pawel
    What password are you using to authenticate? I tried the command Tom mentioned, VNCviewer (windows) asks only for a password, I tried with the rootpw, blank, space they all fail and "nc" drops the connection.

  20. #20
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Default

    Quote Originally Posted by dietmar View Post
    no, there is no vnc server listening, but you can start a server with:

    Code:
    nc -l -p 5900 -c "qm vncproxy VMID PASSWORD"
    After that you can connect one time (because PASSWORD is a one time ticket).

    - Dietmar

    This sounds promising, but I get here:

    "Not a valid VNC server"

    Tried vncviewer and krdc

    Any suggestions most appreciated.

  21. #21
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Default

    Quote Originally Posted by tom View Post
    in such a case connect via ssh to the Proxmox VE and then:

    Code:
    vzctl enter VMID
    the host can access all containers without the need of a running network.
    Thank you, thank you, thank you!!!

    I have been looking for the OpenVZ equivalent of xm vm_name console
    I was beginning to think it was not possible.

  22. #22
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    Try to debug with telnet:

    # telnet IPADDRESS 5900

    to see if the vnc server is answering. Or try to use another port.

    - Dietmar

  23. #23
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Default

    Quote Originally Posted by dietmar View Post
    Try to debug with telnet:

    # telnet IPADDRESS 5900

    to see if the vnc server is answering. Or try to use another port.

    - Dietmar

    Cool thanks. I get

    Code:
    root@devel:~# telnet 10.33.33.131 5900
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    RFB 003.008
    And hangs there, waiting for some stream.

    Now to search this string...
    http://www.google.com.au/search?q=RFB+003.008

  24. #24
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default

    Quote Originally Posted by DaveQB View Post
    Cool thanks. I get

    Code:
    root@devel:~# telnet 10.33.33.131 5900
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    RFB 003.008
    So the VNC server works perfectly.

  25. #25
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Default

    I tried and tried and tried yesterday and suddenly it started working. Bugger me if I know why it wasn't, I didn't change anything in the process.

    Thanks guys!!

    PS I would recommend a tick box option in the web GUI to allow external VNC viewing to a VM in Proxmox. That would be the icing on the cake with this beautiful server software!
    PSS Hmmm maybe I can look at implementing this myself

  26. #26
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Thumbs up

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    Nice work clipcarl!!!

  27. #27
    Join Date
    Apr 2009
    Location
    Sydney, NSW
    Posts
    40

    Default

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword


    Is it right that this only works for KVM and not OpenVZ VM's?

    I have OpenVZ VM's on 5901 and 5902 and KVM VM's on 5903 and 5904.

    [code]
    david@david ~ $
    telnet 10.33.33.131 5901
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    unable to find configuration file for VM 101 - no such machine
    Connection closed by foreign host.
    david@david ~ $
    telnet 10.33.33.131 5902
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    unable to find configuration file for VM 102 - no such machine
    Connection closed by foreign host.
    david@david ~ $
    telnet 10.33.33.131 5903
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    RFB 003.008
    Connection closed by foreign host.
    david@david ~ $
    telnet 10.33.33.131 5904
    Trying 10.33.33.131...
    Connected to 10.33.33.131.
    Escape character is '^]'.
    RFB 003.008
    Connection closed by foreign host.

  28. #28
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default Re: External VNC viewer?

    you can use vncterm for that

    Code:
    vncterm --rfbport 5900 -c vzctl enter 777

  29. #29
    Join Date
    Apr 2009
    Location
    Salerno - Italy
    Posts
    255

    Default Re: External VNC viewer?

    Then.. with
    /usr/sbin/qm qm vncproxy 101 SecretPassword
    Is it possible to transfer file directly to/from Guest VM 101 with VNC client ( like UltraVNC ) if I disable temporanealy VM 101 Network?

  30. #30
    Join Date
    Aug 2006
    Posts
    9,888

    Default Re: External VNC viewer?

    Quote Originally Posted by BiagioParuolo View Post
    Then.. with
    /usr/sbin/qm qm vncproxy 101 SecretPassword
    Is it possible to transfer file directly to/from Guest VM 101 with VNC client ( like UltraVNC ) if I disable temporanealy VM 101 Network?
    I donīt think that this is possible here but never tried.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  31. #31
    Join Date
    Jun 2009
    Posts
    21

    Default Re: External VNC viewer?

    This works great for KVM guests, but I have not been able to figure out a command line to have vncterm started from inetd. I always get a "connection refused" error. I looked through the x11vnc man page, but from what I can see, vncterm does not support most of the x11vnc options.

    vncterm does work from the command line (for a single session).

    The simplest thing I tried was:
    Code:
    5902 stream tcp nowait root /usr/bin/vncterm -inetd -c vzctl enter 102

  32. #32
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default Re: External VNC viewer?

    Quote Originally Posted by zordio View Post
    vncterm does work from the command line (for a single session).
    Yes, seems that vncterm does not work with -inetd

  33. #33
    Join Date
    Feb 2009
    Posts
    56

    Default Re: External VNC viewer?

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    This works awesome!!! Of course I changed SecretPassword to something else

  34. #34
    Join Date
    Sep 2008
    Location
    Washington Court House, United States
    Posts
    213

    Default Re: External VNC viewer?

    having issues getting this to work for 1.4 and a kvm instance.

    In short - I setup a kvm - but cannot attach via external vnc
    what is the easiest how-to for us to follow here -

    server id is 101

    Strange - seems I can do this on the 1.3 and earlier - but 1.4 just cannot get it to work (go figure)

  35. #35
    Join Date
    Sep 2008
    Location
    Washington Court House, United States
    Posts
    213

    Default Re: External VNC viewer?

    even trying this

    # nc -l -p 5900 -c "qm vncproxy 5900 101 password" fails

    :-<

    i get connection refused and then that process stops on the server

  36. #36
    Join Date
    Mar 2009
    Location
    Muenster
    Posts
    140

    Default Re: External VNC viewer?

    Quote Originally Posted by typo3usa View Post
    having issues getting this to work for 1.4 and a kvm instance.

    In short - I setup a kvm - but cannot attach via external vnc
    what is the easiest how-to for us to follow here -

    server id is 101

    Strange - seems I can do this on the 1.3 and earlier - but 1.4 just cannot get it to work (go figure)
    Hi typo3usa,

    I tried it today and it worked very well. I did what clipcarl recommended.
    I use UltraVNC as a client to connect to all my KVM instances. Are you sure you opend the ports on the router (if you are behind one)? And forward them to the pve ip - not to the kvm internal nic?

    kind regards
    BitRausch

  37. #37
    Join Date
    Apr 2009
    Location
    Salerno - Italy
    Posts
    255

    Default Re: External VNC viewer?

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    It goes on 1.4 version...
    and you remember to made: sh openbsd-inetd restart

    Bye

  38. #38
    Join Date
    Apr 2009
    Location
    Salerno - Italy
    Posts
    255

    Default Re: External VNC viewer?

    And How to automate: vncterm --rfbport 5900 -c vzctl enter 777
    ?

  39. #39
    Join Date
    Jun 2009
    Posts
    21

    Default Re: External VNC viewer?

    I've come up with the attached script to spawn (and respawn) VNC listeners for OpenVZ containers. The script assumes each one listens on 59XX (for 100-199 of course). Usage notes are included at the top of the script.

    Usage:
    Start with: nohup vz_vnclisten <VMID> &
    Stop with: kill `cat /var/run/vz_vnclisten_<VMID>` (may take a while to stop)
    Start on boot by adding to /etc/rc.local:
    /usr/local/sbin/vz_vnclisten <VMID> &
    Attached Files Attached Files

  40. #40
    Join Date
    Feb 2010
    Posts
    1

    Default Re: External VNC viewer?

    Hi there,

    I read this thread on and on to connect my external vnc to the proxmox kvm sessions with "chicken vnc" on Mac. It didn't go well since now and i tought i share my solution with you guys, who has MacOSX 10.6.2.

    On my Site this steps works:

    1. Download wine from the internet and install it -> http://winebottler.kronenberg.org/
    2. Download also Thight VNC only the excecutable Edition -> http://www.tightvnc.com/download/1.3...x86_viewer.zip
    3. Start on your Proxmox VNC Server via SSH following command: nc -l -p 5900 -c "qm vncproxy VMID PASSWORD" -> exp.: nc -l -p 5900 -c "qm vncproxy 101 mypassword"
    -> tnx for this solution @dietmar
    4. Just execute the vncviewer from your Mac -> type in the box your IP ADRESS:PORT -> exp: 192.168.1.1:5900
    5. Enter your password

    -> Now id should work on your Mac to ;-)

    Just to explain why i used TightVnc with Wine?

    - I wasn't able to connect over firefox to the openvnc session -> it always gave me a blank page
    - I tryed safari too, it works for the moment but it didn't fit the screen size so its not really nice to work with it
    - So if i tested the firefox and Internetexplorer from my Bootcamp Partition Windows 7 it always worked perfectly, also tightVnc worked without any problem

  41. #41
    Join Date
    Feb 2010
    Posts
    6

    Default Re: External VNC viewer?

    Does anyone know of a way to obtain some form of logging information using the vncproxy method? I would really like to be able to log connection attempts and subsequently authentication failures. Anyone have any pointers?

    Is it possible to specify an interface for the vncproxy? On servers with multiple interfaces, it would be nice to only open the connection on a single interface/address.

  42. #42
    Join Date
    Mar 2010
    Posts
    3

    Default Re: External VNC viewer?

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    at my job we are using this setup right now, we have a promox high-availibity cluster (http://en.wikipedia.org/wiki/High-availability_cluster), meaning different ip address, my question is there a way to connect directly to the vm's,

    for instance we have several win vm's if in any case one system goes down that means that whoever is connect to that vm will get timed out, because the system that takes over has a different ip address all together, so i guess

    my real question is can i use a remote desktop program like krdc to connect to a windows vm using the vm's ip address and port instead of the actual proxmox machine.

  43. #43
    Join Date
    Aug 2006
    Posts
    9,888

    Default Re: External VNC viewer?

    windows rdp? why not. just enable on the windows side. no proxmox ve specific settings.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  44. #44
    Join Date
    Mar 2010
    Posts
    3

    Default Re: External VNC viewer?

    Quote Originally Posted by clipcarl View Post
    I added this to my /etc/inetd.conf so that I can always connect to my VMs with an external viewer:
    9001 stream tcp nowait root /usr/sbin/qm qm vncproxy 101 SecretPassword
    9002 stream tcp nowait root /usr/sbin/qm qm vncproxy 102 SecretPassword
    9003 stream tcp nowait root /usr/sbin/qm qm vncproxy 103 SecretPassword
    9004 stream tcp nowait root /usr/sbin/qm qm vncproxy 104 SecretPassword
    9005 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 SecretPassword
    9006 stream tcp nowait root /usr/sbin/qm qm vncproxy 106 SecretPassword
    9007 stream tcp nowait root /usr/sbin/qm qm vncproxy 107 SecretPassword
    9008 stream tcp nowait root /usr/sbin/qm qm vncproxy 108 SecretPassword
    at my job we are using this setup right now, we have a promox high-availibity cluster (http://en.wikipedia.org/wiki/High-availability_cluster), meaning different ip address, my question is there a way to connect directly to the vm's,

    for instance we have several win vm's if in any case one system goes down that means that whoever is connect to that vm will get timed out, because the system that takes over has a different ip address all together, so i guess

    my real question is can i use a remote desktop program like krdc to connect to a windows vm using the vm's ip address and port instead of the actual proxmox machine.

  45. #45
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    12,206

    Default Re: External VNC viewer?

    Quote Originally Posted by itazuramono View Post
    my real question is can i use a remote desktop program like krdc to connect to a windows vm using the vm's ip address and port instead of the actual proxmox machine.
    Why not?

  46. #46
    Join Date
    Mar 2010
    Posts
    3

    Default Re: External VNC viewer?

    Quote Originally Posted by dietmar View Post
    Why not?
    why not with proxmox? well for us it works but trying to find a better way for it to

    work because we do not have a heartbeat address, each system in the cluster has a

    fixed ip, so when node goes down and there are employees connected to the vm's then

    there work would be interrupted. and would have to connect to the vm on the other

    system where as if it were connected to the vm directly since our system takeover are

    instantaneous, then they would not have any interruption.our vm's have fixed ip leases

    from our dhcp servers.

  47. #47
    Join Date
    Mar 2010
    Posts
    4

    Default Re: External VNC viewer?

    Quote Originally Posted by Marcel Gautschi View Post
    Hi there,


    - I wasn't able to connect over firefox to the openvnc session -> it always gave me a blank page
    - I tryed safari too, it works for the moment but it didn't fit the screen size so its not really nice to work with it
    - So if i tested the firefox and Internetexplorer from my Bootcamp Partition Windows 7 it always worked perfectly, also tightVnc worked without any problem

    you ever found a fix for this? on how to use firefox? besides using the chicken of vnc

  48. #48
    Join Date
    May 2008
    Posts
    24

    Default Re: External VNC viewer?

    Thanks Clipcarl.
    It works fine.
    Just two remarks.
    I had to restart openbsd-inetd by proxmox2:~# /etc/init.d/openbsd-inetd restart.
    In a cluster you need to change /etc/inetd.conf for the vm in the node where the vm is placed and use the IP of that node!!
    As a client I use Remmina on Linux Mint 8. Works like a charm!!

    Peter

  49. #49
    Join Date
    Dec 2009
    Posts
    62

    Default Re: External VNC viewer?

    Quote Originally Posted by SuperMiguel View Post
    you ever found a fix for this? on how to use firefox? besides using the chicken of vnc
    For Safari all you need to do is edit /usr/share/pve-manager/root/qemu/vnc-direct.htm and change:

    $out .= "<APPLET id=vncapp CODE='VncViewer.class' ARCHIVE='/vncterm/VncViewer.jar' width=640 height=480 vspace=0 hspace=0>\n";

    to $out .= "<APPLET id=vncapp CODE='VncViewer.class' ARCHIVE='/vncterm/VncViewer.jar' width=800 height=600 vspace=0 hspace=0>\n";


    Then the missing line problem goes away. No idea how to fix the blank white page in Firefox.

  50. #50
    Join Date
    Dec 2010
    Posts
    1

    Default Re: External VNC viewer?

    hi, i am new in this job, i need to know how to do this permanent.

    tks

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •