Jeff Boerio | 1 Oct 2004 01:06
Picon

building VNC 4.0 w/ X.org on SUSE

I'm trying to build VNC 4.0 against X.org on SUSE and I'm having some
difficulties.

It appears that things aren't getting hooked in properly at "patch"
time, as if I look inside .../xc/programs/Xserver/vnc, no Makefile gets
created.  Same as in .../xc/programs/Xserver/vnc/Xvnc.

On a tangent, has anyone been successful in getting these things to
build on a 64-bit SUSE machine?

     - Jeff
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Steffen Römmler | 1 Oct 2004 09:38
Picon

vnc registry

Hello,

I would like to know, if there is a possibility to allow/disallow viewer to
create new connections. Also I would be glad to hear, that there is a registry
key to allow/disallow the server "Disconnect All Clients". I ask mainly for
v3.3.7 but also for v4 als well as TightVNC.

Thanks for interesting.
Stroem
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Matthew Klabnik | 1 Oct 2004 14:42

Re: Remote Sound

Vironique,

I needed to do something similar for a project. I explored this for months
and found a few S/W solutions but nothing easy. My solution was to buy a
Barix Instreamer. The Instreamer takes audio in and streams MP3 out over
Ethernet. I connected it to the audio out of the sound card. You then have a
two step process on the client side. You launch something like Winamp (or
whatever MP3 stream player works on your OS) and connect to the MP3 stream
from the Barix box. Then you launch your VNC viewer. You just have to expect
there to be some latency between your mouse events and the audio. That was
OK for my application.

The Instreamer can be found at:
http://www.barix.com/en/datasheets/Product%20Sheet%20Instreamer%20V13.pdf

It costs about $300. I was buying this for work so it was cheaper to buy a
few of these than pay a programmer to make the S/W solutions work for my
Solaris 2.6 servers. Someone smarter than I could probably incorporate a
streaming audio player into the VNC viewer. I'd pay $$ for that.

If that's too rich for you and you like to tinker look at
http://www.icecast.org/. This solution would use your server as the streamer
instead of external H/W but the concept is the same: Two separate
applications, VNC for Keyboard, Mouse & Video, streaming MP3 for the audio.

Matt

Matthew Klabnik

Sr Member of the Technical Staff
(Continue reading)

Corné Beerse | 1 Oct 2004 16:15
Picon
Favicon

Re: How do I tell the version of my Linux vncserver?

geofgibson wrote:

> I can't really find a way to see if I'm using ver. 3 or 4.  Where could I
> find that on my system?
> 

Xvnc --help

it lists roughly at the top.

>  
> 
> Thanks.
> 
>  
> 
> Geof Gibson - geofgibson <at> cox.net
> Apple Certified Portable TechnicianRegistered Linux User 319068
> You can always send mail to soundsurgeon.tv as well
>  <http://soundsurgeon.tv> http://soundsurgeon.tv
>  <http://variableproductions.com> http://variableproductions.com 
> 
> [demime 1.01d removed an attachment of type image/jpeg which had a name of image001.jpg]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image002.gif]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image003.gif]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image004.gif]
> _______________________________________________
(Continue reading)

Corné Beerse | 1 Oct 2004 16:15
Picon
Favicon

Re: How do I tell the version of my Linux vncserver?

geofgibson wrote:

> I can't really find a way to see if I'm using ver. 3 or 4.  Where could I
> find that on my system?
> 

Xvnc --help

it lists roughly at the top.

>  
> 
> Thanks.
> 
>  
> 
> Geof Gibson - geofgibson <at> cox.net
> Apple Certified Portable TechnicianRegistered Linux User 319068
> You can always send mail to soundsurgeon.tv as well
>  <http://soundsurgeon.tv> http://soundsurgeon.tv
>  <http://variableproductions.com> http://variableproductions.com 
> 
> [demime 1.01d removed an attachment of type image/jpeg which had a name of image001.jpg]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image002.gif]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image003.gif]
> 
> [demime 1.01d removed an attachment of type image/gif which had a name of image004.gif]
> _______________________________________________
(Continue reading)

Tom Wright | 1 Oct 2004 16:35
Picon
Favicon

RE: clipboard functionality

Tricia

Let me preface this with, this is for version 4.0.

When starting up the VNC viewer click on the options button.  Then click on
the inputs tab.  Make sure that the option "Accept clipboard changes from
server" is checked.  Then click OK and logon to the VNC server.  Now when
you highlight text on the server it is automatically sent to the client and
you should be able to do a paste.

Hope this helps.

Tom

-----Original Message-----
From: vnc-list-admin <at> realvnc.com [mailto:vnc-list-admin <at> realvnc.com] On
Behalf Of tsanders <at> centexhomes.com
Sent: Thursday, September 30, 2004 11:54 AM
To: vnc-list <at> realvnc.com
Subject: clipboard functionality

how can i get this to work?  i'm viewing (with vnc ) my pc #1 through a
browser on my pc #3.  if i click on clipboard (on pc #3) and type in text,
i only have an option to clear or dismiss.  shouldn't there be an option to
send the text to pc #1?  or am i doing something completely wrong?

tricia sanders
user support analyst
214.981.5779
tsanders <at> centexhomes.com
(Continue reading)

Ron Crummett | 1 Oct 2004 19:57

Remote VNC

I have a question that I have wanted to ask for a long time, but didn't even
know where to begin on it.  I now feel like I have enough of a grasp to ask,
so here goes...

I need to be able to VNC into some computers located about two hours from
here.  During a recent on-site visit I tried to gather the information
needed for VNC and this is what I have:

The IP addresses are assigned by DHCP and begin 192.168
I have the IP address of the router that the computers connect to
My IP address is also a 192.168 address
I have the IP address of my router

I feel that I have the information necessary to VNC into these "remote"
computers, but my question is how?  There are so many 192.168 addresses
behind routers and whatnot that I know a simple 'ping 192.168.xxx.xxx' will
not do the job; any suggestions?  I hope that this has made sense.

That's it from here.  More to come as the plot thickens...

Ron Crummett
CayNet Consulting, LLC
(208) 424-1590
roncrummett <at> caynetco.com
http://www.caynetco.com

[demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat]
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
(Continue reading)

John R Larsen | 1 Oct 2004 22:31
Picon

Re: Remote VNC

There are multiple issues involved.  I'm assuming that you have installed VNC on the remote 
computers and that the VNC server is running.  You need to know the LAN IP address of the remote 
machine you want to connect to.  You need to have access to the router at the remote site so that 
you can setup NAT port forwarding.  The router has a WAN IP address.  I assume that you know its 
IP address.  You need to configure the remote router to forward a given port number to a machine 
on the LAN.  As an example, say "machine1" with LAN IP address of 192.168.1.100 has its VNC 
server listening on the default port of 5900.  You need to configure the remote router to forward port 
5900 to 192.168.1.100.  If that is configure correctly, then on your local machine you should be able 
to simply put the WAN IP address in the VNC Viewer's "VNC server:" box and you will connect to the 
machine.

If you want to be able to connect to more than one computer at the remote site then you will need to 
configure each of the VNC Servers to listen on different ports.  The default display number is port 
5900.  Numbers you enter in the VNC Server setup dialog are offsets from 5900.  So if you put in the 
number "10" then the VNC Server would actually be listening on port 5910.  So, if you give each 
computer a different display number then you can configure the router to forward each different port 
number to the correct machine.

It gets tricky if the machines keep changing LAN IP addresses.  Somehow you need to keep track of 
their IP addresses.  I like to give my machines static IP addresses on the LAN so that I know which 
machine is which. 

Remember that VNC isn't secure.  When you connect to a remote computer as described above, 
the passwords and everything you type is plain text and susceptible to snooping.  To get around this 
I use ssh connections to a linux box on the LAN and use ssh port forwarding.  This provides a 
secure connection.

Good luck!  VNC is an awesome tool.  I've been using it for about six years and couldn't live without 
it.

(Continue reading)

Alan Watchorn | 1 Oct 2004 23:07

RE: Remote VNC

Ron,

You didn't explicitly say so but I assume there are 2 separate LANs, one at
the remote site and one where you are, and the LANs are connected by the
Internet.  Furthermore I assumed that there is a separate DHCP for each LAN.
I am also assuming you are using Windows (though this should apply in the
case of UNIX too but I am not familiar with that environment).

If this is the case there are a couple of ways you can use VNC.  The first
is a VPN (PPTP) connection between the two where you would set up a VPN on
the remote system and connect to it with your computer.  In effect your
computer appears as another system on that network.  It is a nice solution
because you are just dealing with one LAN and you can reference all the
systems by name rather than IP.  It does require a fair amount of work to
set up a VPN so that may not be a real possibility unless you need the VPN
for some other purpose (it may even already exist!).  A second way to do it
is to use different ports for VNC and forward them (in the router) to the
systems you want to get to on the remote LAN.  It's not as tough as it
sounds.  Forwarding is a pretty standard function in most routers - just
choose a port for each system and make sure you use the same port number on
VNC (you can probably get info from the archives on this web site on how to
do that).

The other thing you need to do is either choose static IP addresses for the
remote systems (you don't want the DHCP assigning them addresses or you will
have a moving target!) or sign up with a Dynamic DNS service so that the
name always gets you to the same system (even if the IP address changes).

Alan Watchorn
alan <at> eshelmanappraisals.com
(Continue reading)

Chad LaFarge | 1 Oct 2004 23:29

Still watching this space...

Mentioned this week was Enterprise version...  :) :) :)

Any news?
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Gmane