Page 7 of 13 FirstFirst ... 56789 ... LastLast
Results 61 to 70 of 130

Thread: HOWTO: Reverse VNC

  1. #61
    Join Date
    Jun 2007
    Beans
    36
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: HOWTO: Reverse VNC

    hi, i had same problem of papulo and corbin, did someone know how to solve it ?
    thank you

  2. #62
    Join Date
    Apr 2006
    Location
    Los Angeles, CA
    Beans
    3
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOWTO: Reverse VNC

    I've just opened a bug in launchpad as I have the same problem (https://bugs.launchpad.net/ubuntu/+s...nc/+bug/172633)

  3. #63
    Join Date
    Oct 2007
    Location
    California, USA
    Beans
    3
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOWTO: Reverse VNC

    Quote Originally Posted by dazwin View Post
    I've just opened a bug in launchpad as I have the same problem (https://bugs.launchpad.net/ubuntu/+s...nc/+bug/172633)
    Thank you for opening that report. I guess we'll see what happens.

  4. #64
    Join Date
    Mar 2005
    Location
    Canada
    Beans
    1,595

    Re: HOWTO: Reverse VNC

    Thanks dazwin.

    I was on Launchpad last night looking to see if there was a bug reported about it. I wasn't sure if it was a VNC problem or not, as I am able to establish a reverse-VNC connection using the method outlined in post #6 using either the internal IP or my DynDNS address, but not using UVNC's "Single-click".

    For example, on my Windows XP laptop (ip: 192.168.1.107), I can use UltraVNC to "add a client" and connect to Gutsy running vncviewer -listen (ip: 192.168.1.106) and I get connected. I can also connect using my DynDNS address using the same method of "add new client".

    I'll confirm this again tonight and then add the information to Launchpad.

    -Dave
    Last edited by dbott67; November 30th, 2007 at 03:11 PM. Reason: Updated for clarity

  5. #65
    Join Date
    Mar 2005
    Location
    Canada
    Beans
    1,595

    Re: HOWTO: Reverse VNC

    Okay, here's an update.

    It may be the version of RFB (remote frame buffer?) that UltraVNC single-click uses (3.16) vs. the supported versions of up to 3.6.

    According the the output below, VNC-SC uses v.3.16, while UltraVNC server uses v.3.3.

    Here's what I did:

    I was able to connect using the "Add New Client" option in UltraVNC Server both internally and externally (see attached screen shots and text output below):

    Successful connection from Laptop (192.168.1.107) to Gutsy (192.168.1.106) using UltraVNC Server's "Add New Client" option:

    Code:
    dbott@gutsy:~$ vncviewer -listen
    
    VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
    Copyright (C) 2002-2005 RealVNC Ltd.
    See http://www.realvnc.com for information on VNC.
    
    Wed Nov 28 18:49:56 2007
     main:        Listening on port 5500
    
    
    Wed Nov 28 18:50:25 2007
     CConn:       Accepted connection from 192.168.1.107::4049 <-- connection from my laptop using the internal IP address in UltraVNC
     CConnection: Server supports RFB protocol version 3.6
     CConnection: Using RFB protocol version 3.3
     TXImage:     Using default colormap and visual, TrueColor, depth 24.
     CConn:       Using pixel format depth 6 (8bpp) rgb222
     CConn:       Using ZRLE encoding
    
    Wed Nov 28 18:50:26 2007
     CConn:       Throughput 20135 kbit/s - changing to hextile encoding
     CConn:       Throughput 20135 kbit/s - changing to full colour
     CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
     CConn:       Using hextile encoding
    Successful connection from Laptop (192.168.1.107) to Gutsy (using public DynDNS address) using UltraVNC Server's "Add New Client" option:

    Code:
    dbott@gutsy:~$ vncviewer -listen
    
    VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
    Copyright (C) 2002-2005 RealVNC Ltd.
    See http://www.realvnc.com for information on VNC.
    
    Wed Nov 28 19:01:26 2007
     main:        Listening on port 5500
    
    
    Wed Nov 28 19:06:37 2007
     CConn:       Accepted connection from 69.49.xxx.yyy::62000 <-- connection from UltraVNC using my DynDNS address
     CConnection: Server supports RFB protocol version 3.6
     CConnection: Using RFB protocol version 3.3
    
    Wed Nov 28 19:06:38 2007
     TXImage:     Using default colormap and visual, TrueColor, depth 24.
     CConn:       Using pixel format depth 6 (8bpp) rgb222
     CConn:       Using ZRLE encoding
     CConn:       Throughput 11900 kbit/s - changing to hextile encoding
     CConn:       Throughput 11900 kbit/s - changing to full colour
     CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
     CConn:       Using hextile encoding
    Unsuccessful connection from Laptop (192.168.1.107) to Gutsy (using public DynDNS address) using UltraVNC's Single-click:

    Code:
    dbott@gutsy:~$ vncviewer -listen
    
    VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
    Copyright (C) 2002-2005 RealVNC Ltd.
    See http://www.realvnc.com for information on VNC.
    
    Wed Nov 28 19:01:26 2007
     main:        Listening on port 5500
    
    Wed Nov 28 19:10:57 2007
     CConn:       Accepted connection from 69.49.xxx.yyy::62008 <--- using UVNC Single-click
     CConnection: Server supports RFB protocol version 3.16
     CConnection: Using RFB protocol version 3.8
    
    Wed Nov 28 19:12:00 2007
     main:        End of stream
    Both attached screenshots show successful connections back to the vncviewer in listen mode. It appears as though the problem lies with Ultra VNC's "Single Click" add-on application.

    -Dave
    Attached Images Attached Images
    Last edited by dbott67; November 29th, 2007 at 01:42 AM.

  6. #66
    Join Date
    Apr 2006
    Location
    Los Angeles, CA
    Beans
    3
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOWTO: Reverse VNC

    This workaround no longer works for Ubuntu 8.04 - try post #105 instead, which works for me.

    (You could also download and install xvncviewer 3.3.7 from Gutsy manually - it still works in Hardy, but the above solution is probably better.)


    A workaround is to revert back to the old v3.3.7 viewer (from universe):

    $ sudo apt-get install xvncviewer
    $ sudo update-alternatives --set vncviewer /usr/bin/xrealvncviewer
    Last edited by dazwin; June 10th, 2008 at 12:58 AM.

  7. #67
    Join Date
    Apr 2006
    Location
    Los Angeles, CA
    Beans
    3
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOWTO: Reverse VNC

    Ok, I opened a bug report against the wrong package. There is already a bug open for this filed against vnc4 (https://bugs.launchpad.net/ubuntu/+s...c4/+bug/123631).

    It's also not really a bug with vncviewer, but a bug in UltraVNC SingleClick, which reports an incorrect protocol version. There is a thread about this on the UltraVNC forums:

    http://forum.ultravnc.info/viewtopic.php?t=10451

  8. #68
    Join Date
    Mar 2005
    Location
    Canada
    Beans
    1,595

    Re: HOWTO: Reverse VNC

    Quote Originally Posted by dazwin View Post
    A workaround is to revert back to the old v3.3.7 viewer (from universe):

    $ sudo apt-get install xvncviewer
    $ sudo update-alternatives --set vncviewer /usr/bin/xrealvncviewer
    Great work, dazwin!

    Thanks for the workaround. I will post this info into the original post.

    Just to add a bit of info to the workaround: I needed to specify the display number in the vnciewer -listen command (my original HOWTO omitted the display # and it just automatically defaulted to display 0; xvncviewer seems to default to display 1):
    Code:
    vncviewer -listen 0
    For some reason, running vncviewer -listen without specifying the display # defaulted to 1 (which means that vncviewer listens on port 5501 instead of 5500).

    Code:
    dbott@gutsy:~$ vncviewer -listen 0
    VNC viewer version 3.3.7 - built May 24 2007 12:45:44
    Copyright (C) 2002-2003 RealVNC Ltd.
    Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
    See http://www.realvnc.com for information on VNC.
    vncviewer -listen: Listening on port 5500 (flash port 5400)
    vncviewer -listen: Command line errors are not reported until a connection comes in.
    VNC server supports protocol version 3.16 (viewer 3.3)
    No authentication needed
    Desktop name "WinVNC"
    Connected to VNC server, using protocol version 3.3
    VNC server default format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    Using default colormap and visual, TrueColor, depth 24.
    Got 256 exact BGR233 colours out of 256
    Using BGR233 pixel format:
      8 bits per pixel.
      True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
    Using shared memory PutImage
    Throughput 3690 kbit/s - changing from 8bit
    Using viewer's native pixel format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    ShmCleanup called
    Code:
    dbott@gutsy:~$ vncviewer -listen
    VNC viewer version 3.3.7 - built May 24 2007 12:45:44
    Copyright (C) 2002-2003 RealVNC Ltd.
    Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
    See http://www.realvnc.com for information on VNC.
    vncviewer -listen: Listening on port 5501 (flash port 5401)
    vncviewer -listen: Command line errors are not reported until a connection comes in.
    -Dave
    Last edited by dbott67; November 29th, 2007 at 04:02 PM.

  9. #69
    Join Date
    Oct 2007
    Location
    wrong planet
    Beans
    746
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: HOWTO: Reverse VNC

    Quote Originally Posted by dbott67 View Post
    [COLOR=Red]can "send their desktop", you need to set vncviewer to listen-mode on your computer:
    Code:
    vncviewer -listen 0
    4. Lastly, the remote user needs to issue the following command:
    Shouldn't that 0 be a port number such as 5500?
    Linux Advanced Guides and News!
    http://linuxinnovations.blogspot.com/

    Green means go, Yellow means faster, Red means don't stop.

  10. #70
    Join Date
    Mar 2005
    Location
    Canada
    Beans
    1,595

    Re: HOWTO: Reverse VNC

    Quote Originally Posted by go_beep_yourself View Post
    Shouldn't that 0 be a port number such as 5500?
    No. By default, the program takes the number specified (in this case 0) and adds it to 5500. If you were to specify 5500, the app would listen on port 11,000 (5500 + 5500):
    Code:
    dbott@gutsy:~$ vncviewer -listen 5500
    VNC viewer version 3.3.7 - built May 24 2007 12:45:44
    Copyright (C) 2002-2003 RealVNC Ltd.
    Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
    See http://www.realvnc.com for information on VNC.
    vncviewer -listen: Listening on port 11000 (flash port 10900)
    vncviewer -listen: Command line errors are not reported until a connection comes in.
    -Dave

Page 7 of 13 FirstFirst ... 56789 ... LastLast

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
  •