Board index Linux

About using VNC...

About using VNC...

Post by Guy Parr » Tue, 30 Jan 2001 15:20:25



     It clearly says in the "Getting Started with VNC" section on
their site: The server and the viewer may be on different machines and
on different architectures.  We expect the most common use to be the
display of a Unix X desktop on a PC, for example..."
     I have just such a setup, but I don't understand how to start the
server in the Linux partition.  I can't seem to get it clear.  You can
only be booting into one OS at a time, right.  If I'm in Windows how
can I get across to the other partition to start Linux's server so I
can THEN start the viwer from Windows...
      I don't get it.  The docs says something about DNS numbers.
Something about 127.0.0.1..Would I type something o do with that in
Windows' telnet program?  Sorry to sound dense; I just can't seem to
ask the question the right way, thanks to shit documentation....sigh.
     tia...
Quote:

>Then using a viewer in Windows you can connect to remotemachine:1 and
>display it there. Or, you can browse to http://remotemachine:5801 with
>a Java capable web browser.

 
 
 
Top

About using VNC...

Post by max » Tue, 30 Jan 2001 21:54:21




>      It clearly says in the "Getting Started with VNC" section on
> their site: The server and the viewer may be on different machines and
> on different architectures.  We expect the most common use to be the
> display of a Unix X desktop on a PC, for example..."
>      I have just such a setup, but I don't understand how to start the
> server in the Linux partition.  I can't seem to get it clear.  You can
> only be booting into one OS at a time, right.  If I'm in Windows how can
> I get across to the other partition to start Linux's server so I can
> THEN start the viwer from Windows...
>       I don't get it.  The docs says something about DNS numbers.
> Something about 127.0.0.1..Would I type something o do with that in
> Windows' telnet program?  Sorry to sound dense; I just can't seem to ask
> the question the right way, thanks to shit documentation....sigh.
>      tia...

What you want is what VNC doesn't offer. VNC remotely displays the
display af a machine on the display of another machine. You can't have
Linux and Windows up and running at the same time on the same machine
using VNC.

For that you would need VMWare. Check out www.vmware.com. It allows you
to run a virtual machine on your current OS, so you can run Linux from
Windows (or the other way around).

max

 
 
 
Top

1. Trouble using VNC thru a ssh tunnel

I would like to connect from my home machine, "home" to my work
machine, "work" using VNC through a ssh tunnel with port forwarding.
I am running Redhat 7.1, openssh-3.1p1-1, and vnc-3.3.3r2-18.3 on both
machines.

I am able to run VNC without port forwarding by starting a vncserver
on work and issuing the command 'vncviewer work:1' from home.

But when I do this with port forwarding (work:5901 --> home:5902) by
first establishing a ssh connection with 'ssh -L 5902:work:5901 work'
and then issuing the command 'vncviewer localhost:2' from another
pseudotty, I get the following error.

vncviewer: VNC server closed connection

I get no errors in /var/log/messages or /var/log/secure.  If I turn on
the -v option to the ssh command, I do get the following error from
the debug output while connecting to work and prior to attempting the
vncviewer command.

------------------------------------------------------------------------------
debug1: Connections to local port 5902 forwarded to remote address
work:5901
socket: Address family not supported by protocol  I have tried forcing
ssh protocol 1 and ssh protocol 2, but this had no effect.
------------------------------------------------------------------------------

The vncviewer command causes the following output from the ssh -v
command.

----------------------------------------------------------------------------
debug1: Connection to port 5902 forwarding to work port 5901
requested.
debug1: fd 8 setting TCP_NODELAY
debug1: fd 8 setting O_NONBLOCK
debug1: channel 2: new [direct-tcpip]
debug1: channel 2: open confirm rwindow 131072 rmax 32768
debug1: channel 2: rcvd eof
debug1: channel 2: output open -> drain
debug1: channel 2: obuf empty
debug1: channel 2: close_write
debug1: channel 2: output drain -> closed
debug1: channel 2: read<=0 rfd 8 len 0
debug1: channel 2: read failed
debug1: channel 2: close_read
debug1: channel 2: input open -> drain
debug1: channel 2: ibuf empty
debug1: channel 2: send eof
debug1: channel 2: input drain -> closed
debug1: channel 2: send close
debug1: channel 2: rcvd close
debug1: channel 2: is dead
debug1: channel 2: garbage collecting
debug1: channel_free: channel 2: direct-tcpip: listening port 5902 for
work port 5901, connect from 127.0.0.1 port 2104, nchannels 3
-------------------------------------------------------------------------------

I use iptables on both home and work, so I disabled the iptables rules
on both machines for a short period of time, but this had no effect.

Any assistance in getting this working would be greatly appreciated.

Gary

2. binutils/ld question

3. display kde problems using vnc.

4. newbie stuck!! using rage fury maxx

5. Using VNC over ADSL line with PPPoe

6. 2 3c509 NICs; one not recognized

7. TT fonts missing using VNC

8. Link error while compiling a gtk program for Solaris 10 x86

9. Using VNC on Windows XP...not.

10. CDE login using VNC on Solaris 2.5.1

11. Using VNC and Netscape

12. Font display problems in matlab when using VNC (an X resources problem?)

13. Ctrl-C in Windows VNC viewer, Redhat VNC server


All times are UTC
Board index