VNC .vs Msoft Terminal Server

[bruce]

hi...

are there comparisons between VNC and MSoft's Terminal Server.

i have a linux box that i'm using as a client into a windows 2000 box. the
issue i'm having is that the linux terminal service client apparently can't
be resized so i've got a client window on the linux laptop that fills
the screen. the linux client laptop is a 14" screen...

i know if i used vnc as both server/client i could resize the client
window... my question has to with functionality that i might get from the
terminal server client, that i wouldn't get from the vnc client app...

thanks...

bruce
[EMAIL PROTECTED]
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

linux - vncserver

[bruce]

hi.

i have vncserver running on a linux FC3 box. in adding another app, it
appears that vnc requires that my "/etc/hosts" file be set up with:
  127.0.0.1 foo localhost.localdomain   localhost

foo in this case is the name of the box.

i'm trying to setup my VNC and the Condor app to work on a number of
machines in my network. it appears that i can't have "foo" on the same line
as the 127.0.0.1 for Condor to work. however, it appears that I can't remove
the 'foo' or the VNC doesn't seem to work. i'm using VNC to generate the
gnome display.

it appears that my issues are tied to the /etc/hosts file...

any thoughts/assistance will be appreciated.

thanks

-bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC and mIRC

[bruce]

shobuz99...

as far as i know, mirc has nothing to do with ip addresses.i'm assuming this
is the mirc that's used to communicate with the irc channels...

as far as the vncsetup, before you even get there, you need to be able to
find/ping the ip address of the machine that has vnc, which means you need
to be able to ping the router and/or the machine in question.

-can you ping the router
-can you ping the pc/machine
-does the router have port forwarding setup so it allows the port in
question to be forwarded to the actual machine in question

once you've verified that you can communicate/ping with the targeted
machine, then you can setup vnc with no issue...

let us know your progress..


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Shobuz99
Sent: Sunday, August 06, 2006 9:34 AM
To: vnc-list@realvnc.com
Subject: VNC and mIRC


I have a general question for anyone of the VNC users
here. Does anyone have experience using VNC as a
server with mIRC installed on one of the computers
that connected to the same router? I'm asking this
badly, and I apologize for my poor explanation.
A friend of mine wishes to use VNC, in some form, i.e.
ultra, tight, realvnc,winvnc, etc. to monitor his
office machine while he's away. His office machine is
one of the boxes on a router (linksys wrt54gc) sharing
the router with a box that is setup with mIRC and what
seems to be a 'ghost' IP config.
I have tried to help him connect, remotely, to his
office box using VNC. I have forwarded ports 5500,
5800, and 5900 in his setup on the Linksys router. For
some reason, we cannot connect. We get a "timed-out"
error, no matter what port we choose.
When I ping his external IP, the return message is:
C:\>ping 12.42.238.220

Pinging 12.42.238.220 with 32 bytes of data:

Reply from 12.119.154.26: Destination net unreachable.
Reply from 12.125.130.154: Destination net
unreachable.
Reply from 12.119.155.42: Destination net unreachable.
Reply from 12.125.130.154: Destination net
unreachable.

Ping statistics for 12.42.238.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

As you can see, the external address is NOT the one
that appears in the replies. I suspect that mIRC is
creating the
external IP as a 'ghost' IP.
I'm not sure that is true, but am perplexed how to
connect to his server using VNC, if the IP is not the
real external IP.
Does anyone have any experience with this?
I have looked through the previous VNC digests that I
saved,
and I have google'd this several times with no luck.
I appreciate any suggestions anyone may have.
Shobuz99


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

VNCServer configuration

[bruce]

Hi..

I'm trying to figure out how to setup VNC Server on linux boxes, so that I
can have users login, who can then access their own instance of the server.
This would require that they be able to log in without knowing the port
before logging in... I don't want the user to mix their session with the
session of someone else... Also, how do i go about configuring the system,
so the user can use their own system login user/passwd...

thanks
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNCServer configuration

[bruce]

hi...

there's still a confusion.

i have a linux box:
i have vncserver running on the box
i want to have multiple users be able to remotely access the
 server using vnc


how can this be accomplished?

normally, you need to know the "port" in use for the vncserver session. if
you have mulitple users, each user won't know the port to use when logging
in.

also, how do you setup vncserver to use the underlying system user/passwd...


thanks



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alex Pelts
Sent: Sunday, June 17, 2007 8:26 PM
To: bruce
Cc: vnc-list@realvnc.com
Subject: Re: VNCServer configuration


Vnc does not work like this. You will need to run multiple instances of
vnc server, which is X server. This will quickly bring performance of
your host down.
Vnc designed to access one instance of X server remotely it is nothing
like a windows terminal server as far as user environment is concerned.
It is more like XP remote desktop.

With vnc EE you can use unix login facilities so your users will have
same password for vnc as they have for the rest of the system.
What ever you are trying to do is not efficient with vnc but it can be
done by starting multiple vnc servers and giving each user his own.

Alex

bruce wrote:
> Hi..
>
> I'm trying to figure out how to setup VNC Server on linux boxes, so that I
> can have users login, who can then access their own instance of the
server.
> This would require that they be able to log in without knowing the port
> before logging in... I don't want the user to mix their session with the
> session of someone else... Also, how do i go about configuring the system,
> so the user can use their own system login user/passwd...
>
> thanks
> ___
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNCServer configuration

[bruce]

also, if this can't be accomplished with the open source vnc, can it be
handled using the enterprise version... i'm assuming it can, otherwise,
vncserver/client is severley limited...

thanks


hi...

there's still a confusion.

i have a linux box:
i have vncserver running on the box
i want to have multiple users be able to remotely access the
 server using vnc


how can this be accomplished?

normally, you need to know the "port" in use for the vncserver session. if
you have mulitple users, each user won't know the port to use when logging
in.

also, how do you setup vncserver to use the underlying system user/passwd...


thanks



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alex Pelts
Sent: Sunday, June 17, 2007 8:26 PM
To: bruce
Cc: vnc-list@realvnc.com
Subject: Re: VNCServer configuration


Vnc does not work like this. You will need to run multiple instances of
vnc server, which is X server. This will quickly bring performance of
your host down.
Vnc designed to access one instance of X server remotely it is nothing
like a windows terminal server as far as user environment is concerned.
It is more like XP remote desktop.

With vnc EE you can use unix login facilities so your users will have
same password for vnc as they have for the rest of the system.
What ever you are trying to do is not efficient with vnc but it can be
done by starting multiple vnc servers and giving each user his own.

Alex

bruce wrote:
> Hi..
>
> I'm trying to figure out how to setup VNC Server on linux boxes, so that I
> can have users login, who can then access their own instance of the
server.
> This would require that they be able to log in without knowing the port
> before logging in... I don't want the user to mix their session with the
> session of someone else... Also, how do i go about configuring the system,
> so the user can use their own system login user/passwd...
>
> thanks
> ___
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNCServer configuration

[bruce]

Alex...

>From your scenario.

I start the server.
I have VNCServer as a service, which gets started when the server is
started.

A user goes to login, using VNC. How does the user know which port to use?
How does the user know which user/passwd to use?

You're stating that every user should have the same user/passwd, which
implies that every user is also going to have the same desktop/state.

This doesn't sound right.

It was my understanding that each user should be able to essentially have
their own 'desktop' when lokking in/using vnc...



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alex Pelts
Sent: Monday, June 18, 2007 1:05 PM
To: bruce
Cc: vnc-list@realvnc.com
Subject: Re: VNCServer configuration


If any of the users is logged in other users will see what she/he is
doing. I am not sure if that is what you want. If you do, then setup vnc
server and give everyone the same password. That is it. There is no need
for port.

If you do not want this behavior then vnc is not for you. I do not know
any way to protect one user from another using vnc. The only way to use
vnc is for all users to see the same screen. It is not different for EE
vs free edition. There are some added features in EE like encryption and
better authentication.

You can also start multiple vnc servers one per user but this is too
resource intensive, just like running multiple X servers on one machine.

Alex

bruce wrote:
> also, if this can't be accomplished with the open source vnc, can it be
> handled using the enterprise version... i'm assuming it can, otherwise,
> vncserver/client is severley limited...
>
> thanks
>
>
> hi...
>
> there's still a confusion.
>
> i have a linux box:
> i have vncserver running on the box
> i want to have multiple users be able to remotely access the
>  server using vnc
>
>
> how can this be accomplished?
>
> normally, you need to know the "port" in use for the vncserver session. if
> you have mulitple users, each user won't know the port to use when logging
> in.
>
> also, how do you setup vncserver to use the underlying system
user/passwd...
>
>
> thanks
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Alex Pelts
> Sent: Sunday, June 17, 2007 8:26 PM
> To: bruce
> Cc: vnc-list@realvnc.com
> Subject: Re: VNCServer configuration
>
>
> Vnc does not work like this. You will need to run multiple instances of
> vnc server, which is X server. This will quickly bring performance of
> your host down.
> Vnc designed to access one instance of X server remotely it is nothing
> like a windows terminal server as far as user environment is concerned.
> It is more like XP remote desktop.
>
> With vnc EE you can use unix login facilities so your users will have
> same password for vnc as they have for the rest of the system.
> What ever you are trying to do is not efficient with vnc but it can be
> done by starting multiple vnc servers and giving each user his own.
>
> Alex
>
> bruce wrote:
>> Hi..
>>
>> I'm trying to figure out how to setup VNC Server on linux boxes, so that
I
>> can have users login, who can then access their own instance of the
> server.
>> This would require that they be able to log in without knowing the port
>> before logging in... I don't want the user to mix their session with the
>> session of someone else... Also, how do i go about configuring the
system,
>> so the user can use their own system login user/passwd...
>>
>> thanks
>> ___
>> VNC-List mailing list
>> VNC-List@realvnc.com
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
> ___
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNCServer configuration

[bruce]

Hi Mike.

Thanks for your reply. What you've described is pretty much what my team has
been doing for quite awhile. However, in an enterprise situation, I'm
considering something that doesn't require users to have to login via ssh,
or to really play with vnc session ids.

It appears that vnc with xdmcp might actually provide a way to accomplish
this. I'm also going to do some research with nx to see if it meets my
goals.

thanks



-Original Message-
From: Boger, Mike [mailto:[EMAIL PROTECTED]
Sent: Monday, June 18, 2007 3:38 PM
To: bruce
Cc: vnc-list@realvnc.com
Subject: RE: VNCServer configuration


Bruce-

We have our users start up their own vncservers. The user initially logs
into the machine (telnet, ssh, etc.) and issues a vncserver command:

vncserver -geometry 1024x768

They will then be given the following info:

***
Reading user's xstartup file

VNC Server Enterprise Edition E4.2.6 - built Jul 27 2006 10:19:03
Copyright (C) 2002-2006 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Running applications in /home/mikeyb/.vnc/xstartup
Log file is /home/mikeyb/.vnc/happybox.domain.com:2.log
New desktop is happybox.domain.com:2  



The user then can point his/her vncviewer to happybox.domain.com:2...
Depending on how the ~/.vnc/xstartup file reads, is which window manager
gets displayed. The first one to get on the machine will get :1, the
next :2, so on so forth. As Alex mentions, the load will depend on what
each user is doing. Keep an eye out on load. An overloaded machine is a
sure fire way to make you very popular.


Here is our default xstartup (we have RHEL and Solaris in our
environment):

 
#!/bin/sh
[ -r ${HOME}/.Xdefaults  ] && xrdb -merge ${HOME}/.Xdefaults
[ -r ${HOME}/.Xresources ] && xrdb -merge ${HOME}/.Xresources

vncconfig -nowin &
if [ "`uname`" = "Linux" ]
then
/usr/bin/startkde &
else
/usr/dt/bin/Xsession &
sleep 30
xset s blank
fi


Hope that this helps-
Best Regards-
Mike

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of bruce
Sent: Monday, June 18, 2007 1:31 PM
To: 'Alex Pelts'
Cc: vnc-list@realvnc.com
Subject: RE: VNCServer configuration

Alex...

>From your scenario.

I start the server.
I have VNCServer as a service, which gets started when the server is
started.

A user goes to login, using VNC. How does the user know which port to
use?
How does the user know which user/passwd to use?

You're stating that every user should have the same user/passwd, which
implies that every user is also going to have the same desktop/state.

This doesn't sound right.

It was my understanding that each user should be able to essentially
have their own 'desktop' when lokking in/using vnc...



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alex Pelts
Sent: Monday, June 18, 2007 1:05 PM
To: bruce
Cc: vnc-list@realvnc.com
Subject: Re: VNCServer configuration


If any of the users is logged in other users will see what she/he is
doing. I am not sure if that is what you want. If you do, then setup vnc
server and give everyone the same password. That is it. There is no need
for port.

If you do not want this behavior then vnc is not for you. I do not know
any way to protect one user from another using vnc. The only way to use
vnc is for all users to see the same screen. It is not different for EE
vs free edition. There are some added features in EE like encryption and
better authentication.

You can also start multiple vnc servers one per user but this is too
resource intensive, just like running multiple X servers on one machine.

Alex

bruce wrote:
> also, if this can't be accomplished with the open source vnc, can it 
> be handled using the enterprise version... i'm assuming it can, 
> otherwise, vncserver/client is severley limited...
>
> thanks
>
>
> hi...
>
> there's still a confusion.
>
> i have a linux box:
> i have vncserver running on the box
> i want to have multiple users be able to remotely access the  server 
> using vnc
>
>
> how can this be accomplished?
>
> normally, you need to know the "port" in use for the vncserver 
> session. if you have mulitple users, each user won't know the port to 
> use when logging in.
>
> also, how do you setup vncserver to use the underlying system
user/passwd...
>
>
> thanks
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Alex Pelts
> Sent: Sunday, June 17, 2007 8:26 PM
> To: bruce
> Cc: vnc-list@realvnc.com
> Subject: Re: VNCServer configuration
>
>
> Vnc does not work like this. You will need to run multiple instances 
> of vnc server, which is X server. This will quickly bring performance 
> of your ho

RE: VNCServer configuration

[bruce]

Hi Alex...

Sorry to say, the solution you propose isn't really acceptable for an
enterprise environment. I don't want potential users to have to 1st ssh into
the system to then start a vnc session that they would then use...

Nor do I want to somehow allocate 10 sessions of vnc, and then allocate them
somehow by passing a script to the user

The real solution might be based on using XPDMC (?) in conjunction with VNC.
There might be a method of having a single session of VNC that can be used
by multiple users, while at the same time, providing a unique desktop, and
allowing the user to login using their user/passwd...

There might also be a solution using the NX app..

thanks



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alex Pelts
Sent: Monday, June 18, 2007 7:05 PM
To: bruce
Cc: 'Boger, Mike'; vnc-list@realvnc.com
Subject: Re: VNCServer configuration


One can write web management front end that would start a server and
publish its screen number. Or maybe you can run bunch of them and tell
users which are free. With EE user can use their unix password to login.

It is all highly dependent on what users actually do. If the
applications are computation/graphics intensive you will bring down the
machine in no time at all. If you already using vnc in such manner and
just want to separate user sessions you can use ssh to do the work for you.

Run say 10 servers on ports 5900 to 5909. Then for each user setup ssh
port forwarding where for each user ssh will forward on a different port
  - for first one localhost:5900 to host:5900, for second one
localhost:5900 to host:5901, etc. Then all user will have to do is to
connect to localhost screen 1 with vnc and ssh will port forward to the
correct port for that user. The only downside that it is not dynamic.

If you want something more dynamic, setup script that would start a
server, generate .vnc file and get it to user somehow. All user will
have to do is double-click on the file to connect to correct server.

Alex


bruce wrote:
> Hi Mike.
>
> Thanks for your reply. What you've described is pretty much what my team
has
> been doing for quite awhile. However, in an enterprise situation, I'm
> considering something that doesn't require users to have to login via ssh,
> or to really play with vnc session ids.
>
> It appears that vnc with xdmcp might actually provide a way to accomplish
> this. I'm also going to do some research with nx to see if it meets my
> goals.
>
> thanks
>
>
>
> -Original Message-
> From: Boger, Mike [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 18, 2007 3:38 PM
> To: bruce
> Cc: vnc-list@realvnc.com
> Subject: RE: VNCServer configuration
>
>
> Bruce-
>
> We have our users start up their own vncservers. The user initially logs
> into the machine (telnet, ssh, etc.) and issues a vncserver command:
>
> vncserver -geometry 1024x768
>
> They will then be given the following info:
>
> ***
> Reading user's xstartup file
>
> VNC Server Enterprise Edition E4.2.6 - built Jul 27 2006 10:19:03
> Copyright (C) 2002-2006 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> Running applications in /home/mikeyb/.vnc/xstartup
> Log file is /home/mikeyb/.vnc/happybox.domain.com:2.log
> New desktop is happybox.domain.com:2
>
> 
>
> The user then can point his/her vncviewer to happybox.domain.com:2...
> Depending on how the ~/.vnc/xstartup file reads, is which window manager
> gets displayed. The first one to get on the machine will get :1, the
> next :2, so on so forth. As Alex mentions, the load will depend on what
> each user is doing. Keep an eye out on load. An overloaded machine is a
> sure fire way to make you very popular.
>
> 
> Here is our default xstartup (we have RHEL and Solaris in our
> environment):
> 
>
> #!/bin/sh
> [ -r ${HOME}/.Xdefaults  ] && xrdb -merge ${HOME}/.Xdefaults
> [ -r ${HOME}/.Xresources ] && xrdb -merge ${HOME}/.Xresources
>
> vncconfig -nowin &
> if [ "`uname`" = "Linux" ]
> then
> /usr/bin/startkde &
> else
> /usr/dt/bin/Xsession &
> sleep 30
> xset s blank
> fi
>
> 
> Hope that this helps-
> Best Regards-
> Mike
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of bruce
> Sent: Monday, June 18, 2007 1:31 PM
> To: 'Alex Pelts'
> Cc: vnc-list@realvnc.com
> Subject: RE: VNCServer configuration
>
> Alex...
>
> From your scenario.
>
> I start the server.
> I have VNCServer as a service, which gets started when the server is
> started.
>
> A user goes to login, using VNC. How does the user 

RE: VNCServer configuration

[bruce]

Hi James/Wez!!

Thanks for the reply. This is what I was looking for, to determine that
there is a way to allow multiple users to be able to access VNC, without
having to have each user do an "ssh/start vncserver" and then login to
vnc!!!

If I understand what you write, you're stating that the Enterprise version
of VNC allows for persistent connections, to the user's desktop. So multiple
users can pretty much simply login to the appropriately configured
VNCServer, using a standard user/passwd login dialog. And that this process
uses the user's underlying system username/passwd...

This also has only a single session/service of VNCServer running, which is
started during the startup process.

Did I miss anything?

Thanks

PS. With regards to the nonpersistent connections, can you point me to
material on how to set this up. My primary goal is that the user not need to
do the "ssh, start vncserver, login" process, which requires the user to
know the session ID. If I understand you, you're saying that the vnc client
app would essentially cause the xinetd service to spawn a VNCServer session
when the user connects via the client. How does the VNC Server access the
user's linux/system username/passwd..


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of James Weatherall
Sent: Tuesday, June 19, 2007 3:12 AM
To: 'bruce'; 'Alex Pelts'
Cc: vnc-list@realvnc.com
Subject: RE: VNCServer configuration


Hi Bruce,

If you don't need your VNC sessions to be persistent then you can create an
xinetd service for VNC server, which will allow a new VNC-based X server to
be created for each incoming VNC Viewer connection.  The user then logs in
using the normal X11 authentication dialogs, and closing the VNC Viewer is
an implicit logout.

If you need persistent VNC sessions per-user, via a single entry point then
this can be achieved using VNC Enterprise Edition in conjunction with the
VNC Session Manager.  The Session Manager receives VNC Viewer connections &
authenticates users using their normal Unix logon credentials in order to
route them through to their existing VNC X server(s), or to create a new VNC
X server for them.

Regards,

Wez @ RealVNC Ltd


> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of bruce
> Sent: 18 June 2007 20:34
> To: 'Alex Pelts'
> Cc: vnc-list@realvnc.com
> Subject: RE: VNCServer configuration
>
> hi...
>
> there's still a confusion.
>
> i have a linux box:
> i have vncserver running on the box
> i want to have multiple users be able to remotely access the
>  server using vnc
>
>
> how can this be accomplished?
>
> normally, you need to know the "port" in use for the
> vncserver session. if
> you have mulitple users, each user won't know the port to use
> when logging
> in.
>
> also, how do you setup vncserver to use the underlying system
> user/passwd...
>
>
> thanks
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Alex Pelts
> Sent: Sunday, June 17, 2007 8:26 PM
> To: bruce
> Cc: vnc-list@realvnc.com
> Subject: Re: VNCServer configuration
>
>
> Vnc does not work like this. You will need to run multiple
> instances of
> vnc server, which is X server. This will quickly bring performance of
> your host down.
> Vnc designed to access one instance of X server remotely it is nothing
> like a windows terminal server as far as user environment is
> concerned.
> It is more like XP remote desktop.
>
> With vnc EE you can use unix login facilities so your users will have
> same password for vnc as they have for the rest of the system.
> What ever you are trying to do is not efficient with vnc but it can be
> done by starting multiple vnc servers and giving each user his own.
>
> Alex
>
> bruce wrote:
> > Hi..
> >
> > I'm trying to figure out how to setup VNC Server on linux
> boxes, so that I
> > can have users login, who can then access their own instance of the
> server.
> > This would require that they be able to log in without
> knowing the port
> > before logging in... I don't want the user to mix their
> session with the
> > session of someone else... Also, how do i go about
> configuring the system,
> > so the user can use their own system login user/passwd...
> >
> > thanks
> > ___
> > VNC-List mailing list
> > VNC-List@realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
> ___
> VNC-List mailing list
> VNC-List@realvnc.com
>

Keyboard cannot repeat in VNC

[bruce]

Hi all,
I have installed Fedora9 on my VMware. When I operate it under VMware,
everything is OK.
However, when I try to operate it using VNC view on Windows, the keyborad
can not repeat ( when pressing a key on the keyboard, it should repeat it
untill I release it. But this time it does not repeat it )
I have used Red Hat 9 and AS 4, this problem never happened.

 

  Wish for solutions. Thanks

 

Bruce.

 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

'pass special keys directly to server' not supported in Linux

[bruce]

Hi,

 

I have downloaded your Linux version of  vncviewer, however, there is not a
'pass special keys directly to server' option as it was there in a windows
version.

 

Is there any workaround for this?

 

Bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Inconsistent copy/paste

[Nepple, Bruce]

I'm running vnc 4 on windows and a vnc 4 server on linux
I'm also running vncconfig with all the boxes checked in the little window.
I'm running on an xfxe3 desktop.

I'm having a real hard time trying to characterize this problem
since it is inconsistent.

The symptoms change from day to day 

Currently, I can copy text in windows2k and middle mouse it into linux nedit,
but I can't middle mouse into linux vi.  But, if I select text in
linux nedit, I can middle mouse THAT into linux vi.

In the reverse direction I get weirdnesses also.  For example, I
select 15 lines data in a linux application, and when I paste in windows
I only get the first 2 lines.  If I middle mouse into linux  vi or nedit
I get all lines.

For a while things seemed to work, but now it's broken again.  Ask me tomorrow
and it will do something different --- maybe pasting into windows will work.
Right now the linux nedit ctl-v ctl-c copy/paste isn't working either, but
the middle mouse stuff within nedit works fine.

I tried exiting vncconfig and restarting it, rebooting windows,
and other things.  (everything but restarting the server)

Any ideas will be appreciated.

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

vncconfig clipboard loop

[Nepple, Bruce]

It seems that vncconfig can get into a clipboard feedback loop.

If I have both boxes checked (send and accept) at the server
and both boxes checked at the viewer when I select text in
nedit it just keeps creating clipboard buffers at the server
(as seen in xclipboard).

Is that the expected behavior?  (Seems like a bug to me.)

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

v4 Problem

[Meyer, Bruce]

I just installed v4 on a couple of servers.
Version 3.x works flawlessly. When I attempt to VNC through a VPN I get the
prompt for a password, I enter it and get an:

VNC Viewer: Error
Authentication failure

popup.

If I try to connect to a v3 VNC server, it work perfect. 
If I am on the local network, I can vnc to the machines fine. This only
happens while going through a VPN. (The same VPN that works with v3.)

Here is a weird thing:

Several nights this week, I can change the option on the viewer to:
User protocol v3.3 only, and would get through to one server, but not the
other.

I was able last night to vnc to a 3.3 server, then vnc to the 4.0 server
using the 3.3 client on the first machine.
Today,  can't vnc to any of the v4.0 machines.

OS is windows 2000 server, and windows 2000 Pro on the workstation, with a
Cisco PIX firewall at work, a Cisco vpn appliance at work, and the v4.0
Cisco vpn client at home going through a dLink wireless router, with a 64bit
WEP key. I don't think any of that would matter since it works with version
3 (vnc), and I am getting the password prompt.

whew. I am quite stumped. 


--
Bruce Meyer, CCNA, MCSE
Network Analyst
City of Columbia
[EMAIL PROTECTED] 
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: How to start up vncserver on linux automatically? - and VNC working on Linux

[Bruce Douglas]

then simply post the instructions/overview to the list in the body of the 
email no need for any attachment/docs...



-Original Message-
From: Angelo Sarto <[EMAIL PROTECTED]>
Sent: Feb 2, 2005 9:46 AM
To: Zach Dennis <[EMAIL PROTECTED]>
Cc: Eve Atley <[EMAIL PROTECTED]>, vnc-list@realvnc.com
Subject: Re: How to start up vncserver on linux automatically? - and VNC  
working on Linux

Attatchments get stripped from the list.even doc files I think.


On Wed, 02 Feb 2005 12:06:57 -0500, Zach Dennis <[EMAIL PROTECTED]> wrote:
> Eve Atley wrote:
> > I finally succeeded in getting VNC to serve on a Redhat Linux box. If anyone
> > wants the instructions I've laid out in a Word document (for people facing
> > the same problems perhaps), please let me know and I'll send it your way. My
> > problem was allowing port 5901 in the iptables firewall rules.
> >
> > Also, I start the vncserver by entering 'vncserver :1' via a terminal each
> > time. How can I make this run at boot time on a Redhat Linux machine?
> >
> 
> I'd say that if you post them to the list it will be nice for people who
>   view the archive while searching Google (this is archived right?).
> 
> Otherwise you may get an email in 6 months asking for the document.
> 
> Zach
> ___
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Problems with Setting up RealVNC in a networked pc

[Ordway, Bruce]

I'm not sure I fully understand your network or what you are trying to
do.
That being said, here's a few things I do.

At work, I have a VPN server with a public IP address 63.25.1.1 (all
addresses are examples) and a private IP address 10.0.0.1.
My office PC 10.0.0.2 has RealVNC server running.
My VPN server handles routing automatically.
>From my home PC, I connect to the Internet, I establish a VPN
connection, then I can connect to the office PC using the RealVNC
client.
I use my PC's LAN IP address 10.0.0.2 for the server in the RealVNC
logon box.

Have you tried adding a route?
I have to add a route in order for my home pc to be able to reach some
servers on a different subnet on my office LAN after I make the VPN
connection.
First I open a command window and type:
Ipconfig (to find out the ip address of my PPP connection)
Then I type - route add 192.168.0.0 mask 255.255.255.0
ipAddressOfMyPPPConnection

Sometimes I add an entry to my home PC's hosts file if I use the name of
my office PC a lot (my DNS servers don't know about my LAN )
new line in hosts file:
10.0.0.2  MyWorkPC


-Original Message-
From: Webmaster. Crafta.com [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 18, 2005 1:23 PM
To: vnc-list@realvnc.com
Subject: Problems with Setting up RealVNC in a networked pc

For instance, i have a public IP for my office network, but interlally 
my range is like 192.168.0.xx, ok internally i can access via VNC typing

the computer name, but what if i want to open a port in the router in 
order to access that networked pc via internet with a VNC client too?
5900 and 5800 in my router for the pc 192.168.0.199
and trying ot access it typing: MYREALIP:5900 or MYREALIP:5800 i tried 
using java web client and regualr client with no results...

wich setting im missing?

thanks
aldo
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Printing

[Ordway, Bruce]

Hi,
 
Is there any way to redirect a print to my local machine when I'm connected to 
a remote PC.
i.e. the data comes from the remote system but prints out on my local printer.
 
Thanks,
 
Bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: STUMPED - can connect via LAN but not via Internet

[Bruce Sellnow]

Hello Chris, et al
 
RE:  http://www.mail-archive.com/vnc-list@realvnc.com/msg24978.html
 
I have the same problem Chris listed here, but I think I need a few more
specifics. What ports are needed to forward? I had this working fine on my
old router with cable internet, but this Actiontec is not very user
friendly. Anyway, do we have to forward 5500, 5800, and 5900? And did you
have to set it for tcp AND udp?
 
My setup is that I have two pc's that I need to access. (false IP's listed
here for reference)
 
Static IP from ISP   175.152.15.67   
Internal Static IP's   100.25.15.61 & 100.25.15.62
 
Old Setup with Netgear Wireless Router
Port Forward: 5911  to  100.25.15.61:5911
   PC1 VNC Server set to (*) Ports Main: 5911
Port Forward: 5912  to  100.25.15.62:5912
   PC2 VNC Server set to (*) Ports Main: 5912
 
So VNC Viewer access from the WAN was simply 175.152.15.67:5911  or
175.152.15.67:5912
Worked great.
 
New Router: Actiontec GT704-WGv2
 
Current problem: VNC internally works fine. Right now, accessing from the
WAN, I can get a password prompt from VNC, it accepts my password, then the
screen goes black as it's 'loading' but never completes. It eventually times
out and disconnects. So I know I am close but don't have *everything* quite
right.
 
PC 1 - Static internal IP 100.25.15.61
   VNC Server set to (*) Ports Main: 5911  Http: 5811
PC 2 - Static internal IP 100.25.15.62
   VNC Server set to (*) Ports Main: 5912  Http: 5812
 
On the Actiontec, I have upgraded the firmware to 3.20.3.3.5.0.9.1.5
 
Under Security - Applications I have applied the following rules
 
PC1: 100.25.15.61
TCP  Port Start: 5911  Port End: 5911  Port Map Start: 5911
TCP  Port Start: 5811  Port End: 5811  Port Map Start: 5811
 
PC2: 100.25.15.62
TCP  Port Start: 5912  Port End: 5912  Port Map Start: 5912
TCP  Port Start: 5812  Port End: 5812  Port Map Start: 5812
 
I get the same result from each pc when I try to access from the WAN. I get
the password prompt, it accepts the password, then goes black as it tries to
load the desktop. Eventually it times out and disconnects. I know I'm
close...!
 

Bruce Sellnow
[EMAIL PROTECTED]
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

FW: RE: STUMPED - can connect via LAN but not via Internet

[Bruce Sellnow]

Here's more info
 
I have now set both TCP and UPD to forward ports for 5501, 5801, 5901.
 
I grabbed my notebook pc and set it in front of my desktop, got online here
at home, and I used the notebook to connect to my office pc using vnc. Then
I launched VNC on my office pc to connect back to my home desktop to test
this out.
 
Again, I get the VNC password prompt, it accepts, then a blank black desktop
screen with "Please wait - Initial Screen Loading..." The difference is,
that whilst sitting here in front of my desktop, I noticed the mouse
responding. So using my notebook and watching my desktop monitor, I was able
to execute mouse clicks and close and open programs. This lasts about 30
seconds and then VNC drops the connection.
 
weird, huh...?
 
 
 
~~~~
Bruce Sellnow
[EMAIL PROTECTED]
 

  _  

From: Bruce Sellnow [mailto:[EMAIL PROTECTED] 
Sent: Saturday, March 31, 2007 5:19 AM
To: 'vnc-list@realvnc.com'
Cc: '[EMAIL PROTECTED]'
Subject: RE: STUMPED - can connect via LAN but not via Internet


Hello Chris, et al
 
RE:  http://www.mail-archive.com/vnc-list@realvnc.com/msg24978.html
 
I have the same problem Chris listed here, but I think I need a few more
specifics. What ports are needed to forward? I had this working fine on my
old router with cable internet, but this Actiontec is not very user
friendly. Anyway, do we have to forward 5500, 5800, and 5900? And did you
have to set it for tcp AND udp?
 
My setup is that I have two pc's that I need to access. (false IP's listed
here for reference)
 
Static IP from ISP   175.152.15.67   
Internal Static IP's   100.25.15.61 & 100.25.15.62
 
Old Setup with Netgear Wireless Router
Port Forward: 5911  to  100.25.15.61:5911
   PC1 VNC Server set to (*) Ports Main: 5911
Port Forward: 5912  to  100.25.15.62:5912
   PC2 VNC Server set to (*) Ports Main: 5912
 
So VNC Viewer access from the WAN was simply 175.152.15.67:5911  or
175.152.15.67:5912
Worked great.
 
New Router: Actiontec GT704-WGv2
 
Current problem: VNC internally works fine. Right now, accessing from the
WAN, I can get a password prompt from VNC, it accepts my password, then the
screen goes black as it's 'loading' but never completes. It eventually times
out and disconnects. So I know I am close but don't have *everything* quite
right.
 
PC 1 - Static internal IP 100.25.15.61
   VNC Server set to (*) Ports Main: 5911  Http: 5811
PC 2 - Static internal IP 100.25.15.62
   VNC Server set to (*) Ports Main: 5912  Http: 5812
 
On the Actiontec, I have upgraded the firmware to 3.20.3.3.5.0.9.1.5
 
Under Security - Applications I have applied the following rules
 
PC1: 100.25.15.61
TCP  Port Start: 5911  Port End: 5911  Port Map Start: 5911
TCP  Port Start: 5811  Port End: 5811  Port Map Start: 5811
 
PC2: 100.25.15.62
TCP  Port Start: 5912  Port End: 5912  Port Map Start: 5912
TCP  Port Start: 5812  Port End: 5812  Port Map Start: 5812
 
I get the same result from each pc when I try to access from the WAN. I get
the password prompt, it accepts the password, then goes black as it tries to
load the desktop. Eventually it times out and disconnects. I know I'm
close...!
 

Bruce Sellnow
[EMAIL PROTECTED]
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Connecting to one of two boxes inside router

[Bruce Sellnow]

I'm using UltraVNC 1.0.2

I have this set up at work and I can access a multitude of pc's using this
configuration on my firewall. Internal IP's are assigned and static - my
actual IP's are obscured here for obvious reasons. 

Port Forwarding - TCP Protocol
Source -->> Destination
{Default IP}:5941  -->>  100.2.1.41:5900
{Default IP}:5942  -->>  100.2.1.42:5900
{Default IP}:5943  -->>  100.2.1.43:5900
{Default IP}:5944  -->>  100.2.1.44:5900

FWIW, I'm using UltraVNC 1.0.2 and I don't have to use double colons. From
the WAN, I just use our IP with one of the ports like this
152.50.65.13:5941
and I get to PC#1 without any problems.

I had the same thing set up at home with a Netgear router and it was working
fine. If I can't get this Actiontec router to do what I want, I might just
bridge it and go back to using the Netgear router.

~~~
Bruce Sellnow
<[EMAIL PROTECTED]>



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Nicholson, Rob
Sent: Monday, April 02, 2007 4:18 AM
To: 'Shobuz99'; vnc-list@realvnc.com
Subject: RE: Connecting to one of two boxes inside router

Don't forget, it's DOUBLE COLON between the IP address and the port. Well it
is on RealVNC.

24.212.250.132::5909

Cheers, Rob. 

PS. I really, really, really wish that reply went to the group. 

-Original Message-
From: Shobuz99 [mailto:[EMAIL PROTECTED] 
Sent: 30 March 2007 17:55
To: vnc-list@realvnc.com
Subject: Connecting to one of two boxes inside router

hello all,

I may've been here before with this question, but I don't recall the answer.

I apologize.. please indulge me.
First, I'm using UltraVNC 1.1.0.1. Viewer (Windows XP) I'm trying to connect
to one of two machines running UltraVNC server, behind a router. The router
has two machines on it, 192.168.1.100 and 192.168.1.141. 
I setup the router (BEFSR41 linksys) port forwarding with two vnc - VNC1
port 5900-5900 and VNC2 port 5909-5909. This is my office, I'm trying to
connect to.
When I try to connect with the viewer, I get a 'failed to connect to server'
error. I am using the external IP address and the port number when I use the
viewer, i.e., 24.212.250.132:5909 What am I doing wrong? 
I followed the port forwarding instructions from the portforward.com web
page, specific to my router type.

Is my port assignment of VNC1 and VNC2 not allowed?
I'm thinking that it is not; but am hoping that someone here can verify what
my connection problem is.
thank you for your help...
Rick (shobuz99)



 


The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: STUMPED - can connect via LAN but not via Internet

[Bruce Sellnow]

Okay thanks, but how do I address the MTU problem? I've even tried
connecting at "MODEM [19-128Kbit/s]-64 Colors" with exactly the same result.
I get connected, the password is accepted, but I get stuck on "Please wait -
Initial screen loading..."


~~~
Bruce Sellnow
<[EMAIL PROTECTED]>


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of evets dranem
Sent: Monday, April 02, 2007 3:43 AM
To: vnc-list@realvnc.com
Subject: Re: STUMPED - can connect via LAN but not via Internet

That sounds like a MTU issue

>New Router: Actiontec GT704-WGv2
>
> 
>
>Current problem: VNC internally works fine. Right now, accessing from the
>WAN, I can get a password prompt from VNC, it accepts my password, then the
>screen goes black as it's 'loading' but never completes. It eventually
times
>out and disconnects. So I know I am close but don't have *everything* quite
>right.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: STUMPED - can connect via LAN but not via Internet

[Bruce Sellnow]

Hey Chris!  Thanks!
 
I did locate that site early on, and I hadn't realized that I needed 5500. I
think I've since discovered that port 5500 is for 'host-initiated"
sessions...?  Not sure about that part, but I always launch from the viewer
side, and I've never forwarded 5500 before so I've never had an issue.
 
The part that I don't understand is how the Actiontec is going to know which
local IP I'm trying to get to. They list
Port Start
Port End
Port Map Start
...but I don't know exactly how to use those three boxes. Everything I've
seen says to place the same numbers in all three boxes, so that's what I've
done. The port forwarding is on a slightly different screen.
 
This is what I want. Assume internal IPs of 1.2.3.4  and 1.2.3.5 and
external IP of 10.20.30.40
 
Access from outside the LAN to inside
10.20.30.40:5901 ==>> 1.2.3.4:5901
10.20.30.40.5902 ==>> 1.2.3.5:5902
 
So I have a rule for 5901 and 5801 and 5501 and assigned those all to PC1
Then I have a rule for 5902 and 5802 and 5502 and assigned those all to PC2
Again, I've entered the same number in all three boxes.
 
I've created all these 'rules' in the Actiontec, and I've assigned them to
each pc as indicated. Like I said, I *know* I'm really close because I get
the password prompt, it accepts the password, and then I get the black
screen "Please wait...Initial Screen loading..."  
 
I just can't get PAST that point ..  AARRGgggh!!   Somebody HELP
me!
 
: - )

~~~ 
Bruce Sellnow 
<[EMAIL PROTECTED]> 


 

  _  

From: Chris Swain [mailto:[EMAIL PROTECTED] 
Sent: Saturday, March 31, 2007 10:17 PM
To: 'Bruce Sellnow'; vnc-list@realvnc.com
Subject: RE: STUMPED - can connect via LAN but not via Internet



Hi Bruce,

 

After receiving good advice from this list that told me that my problems
were related to port forwarding I followed the directions on this site:

http://portforward.com/english/routers/port_forwarding/Actiontec/GT704-WGv2/
VNC.htm

 

This site should answer your questions about ports 5500, 5800, 5900, tcp and
udp.

 

Hope this is of use.

 

Chris

 

  _  

From: Bruce Sellnow [mailto:[EMAIL PROTECTED] 
Sent: Saturday, March 31, 2007 5:19 AM
To: vnc-list@realvnc.com
Cc: [EMAIL PROTECTED]
Subject: RE: STUMPED - can connect via LAN but not via Internet

 

Hello Chris, et al

 

RE:  http://www.mail-archive.com/vnc-list@realvnc.com/msg24978.html

 

I have the same problem Chris listed here, but I think I need a few more
specifics. What ports are needed to forward? I had this working fine on my
old router with cable internet, but this Actiontec is not very user
friendly. Anyway, do we have to forward 5500, 5800, and 5900? And did you
have to set it for tcp AND udp?

 

My setup is that I have two pc's that I need to access. (false IP's listed
here for reference)

 

Static IP from ISP   175.152.15.67   

Internal Static IP's   100.25.15.61 & 100.25.15.62

 

Old Setup with Netgear Wireless Router

Port Forward: 5911  to  100.25.15.61:5911

   PC1 VNC Server set to (*) Ports Main: 5911

Port Forward: 5912  to  100.25.15.62:5912

   PC2 VNC Server set to (*) Ports Main: 5912

 

So VNC Viewer access from the WAN was simply 175.152.15.67:5911  or
175.152.15.67:5912

Worked great.

 

New Router: Actiontec GT704-WGv2

 

Current problem: VNC internally works fine. Right now, accessing from the
WAN, I can get a password prompt from VNC, it accepts my password, then the
screen goes black as it's 'loading' but never completes. It eventually times
out and disconnects. So I know I am close but don't have *everything* quite
right.

 

PC 1 - Static internal IP 100.25.15.61

   VNC Server set to (*) Ports Main: 5911  Http: 5811

PC 2 - Static internal IP 100.25.15.62

   VNC Server set to (*) Ports Main: 5912  Http: 5812

 

On the Actiontec, I have upgraded the firmware to 3.20.3.3.5.0.9.1.5

 

Under Security - Applications I have applied the following rules

 

PC1: 100.25.15.61

TCP  Port Start: 5911  Port End: 5911  Port Map Start: 5911

TCP  Port Start: 5811  Port End: 5811  Port Map Start: 5811

 

PC2: 100.25.15.62

TCP  Port Start: 5912  Port End: 5912  Port Map Start: 5912

TCP  Port Start: 5812  Port End: 5812  Port Map Start: 5812

 

I get the same result from each pc when I try to access from the WAN. I get
the password prompt, it accepts the password, then goes black as it tries to
load the desktop. Eventually it times out and disconnects. I know I'm
close...!

 



Bruce Sellnow
[EMAIL PROTECTED]
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

vnc setup like gotomypc.com?

[Bruce Pennypacker]

Hi all,

As the techie in my extended family I end up fielding a lot of support calls
from different family members.  I was thinking it'd be nice to be able to
remotely access their machines from home if the need arises and in general
VNC would be perfect for this. My only concern is poking holes necessary to
enable this since it would involve dealing with different routers &
firewalls, DHCP, etc.  I was thinking that a service similar to
gotomypc.comwould make more sense.  Both they and I would connect to a
proxy server of
some sort that would establish the vnc connection from my machine to their
machine.  I have a linux box with a static IP that I can set up as a proxy
but I'm not familiar with any tools to do what I envision.  Are there any
tools available like this?  Some sort of app that I can install on a linux
server that one person could log in as a "server" and one as a "client" to
establish a vnc connection between the two?

I know how to set up NAT routes, dynamic hostnames, etc. but I really don't
want to go that way.  I'm specifically interested in whether or not such an
application as I described exists.

-Bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: vnc setup like gotomypc.com?

[Bruce Pennypacker]

On 8/5/07, Sean Kamath <[EMAIL PROTECTED]> wrote:
>
>
> Open a port on *your* router, then forward that port to your machine
> you use VNC to control their machines.  Have them start vnc and
> connect to a "listening client" and point to your machine (if
> necessary, a dyndns hostname).
>
> Then you never need to configure their routers/nat/firewall, and it
> always "just works".
>
> For a while, I dropped shortcuts or whatever they're called on PCs
> (pifs?), that did winvnc4.exe -connect "my ipaddr", labeled them "get
> help" and would tell my mother "click on get help". :-)


This sounds like exactly what I would prefer.  I've never used the listening
client before so I figured I'd give it a shot.  I just tried running the
listening client on my workstation and ran "winvnc4.exe -connect "
on the machine I wanted to control but I keep getting an error "Unable to
locate existing VNC Server".  From what I've read the viewer listens on port
5500 so I have that opened in my firewall, and when I have the viewer
running in listen mode I can telnet to that port so I know the firewall is
set up properly.  Do I also need 5900 opened up as well or is there
something else I'm missing?

-Bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: vnc setup like gotomypc.com?

[Bruce Pennypacker]

On 8/7/07, Bruce Pennypacker <[EMAIL PROTECTED]> wrote:

>
> This sounds like exactly what I would prefer.  I've never used the
> listening client before so I figured I'd give it a shot.  I just tried
> running the listening client on my workstation and ran " winvnc4.exe-connect 
> " on the machine I wanted to control but I keep getting an
> error "Unable to locate existing VNC Server".  From what I've read the
> viewer listens on port 5500 so I have that opened in my firewall, and when I
> have the viewer running in listen mode I can telnet to that port so I know
> the firewall is set up properly.  Do I also need 5900 opened up as well or
> is there something else I'm missing?
>
> -Bruce
>

Never mind.  I figured it out.  It's not clear that the server needs to
already be running before you run the above command.  Thanks for all the
suggestions & help!

-Bruce
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Where is the outside IP?

[Bruce Como]

Hi,

 

Via the phone, I had my father install VNC server.  He started it in
user-mode and the icon appears in the taskbar.  So far, so good.

 

The only IP address he sees when he runs the mouse over the icon is his
local IP (192.168.0.100).  Obviously, I need the IP address Verizon is
giving his router.  Does VNC do this for me, or is this something I needed
to know ahead of time?

 

Thanks for your time.

 

Bruce

 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Log on using VNC

[Bruce K]

To whom it may concern:

When I attempt to log onto a computer using VNC, I am not able to send the 
control alt delete command to the console. The control alt delete command it 
being interpreted as a command for the workstation I am working from. I am 
sure there is some type of work around for this situation, but I have not 
been able to arrive at one.

Bruce


[EMAIL PROTECTED]


_
Join the worlds largest e-mail service with MSN Hotmail. 
http://www.hotmail.com
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: NT5 / Windows 2000 Server Problem -- session gets hung

[Bruce Lilly]

 From: "W. Curtiss Priest" <[EMAIL PROTECTED]>
 Date: Fri, 30 Aug 2002 10:10:42 -0400

Twice now, I have been in a session.  I have inadvertently
closed the VNC client.

Then, the client can no longer establish a connection.

We check.  VNC is STILL running as a Service.  If we stop
and then start VNC, then it works again.

In each instance there was an abnormal abort on one of the
running applications during the working session.

Known problem?  Perhaps solve by having VNC restart itself
at the end of each connection?

What exactly happens when you restart the client?
e.g. "Failed to connect to server"

What happens if you telnet to the server's port 5900 from the
client?

I've seen VNC server get screwed up and send RFB followed by
an endless repeat of clipboard data, which of course causes
vncviewer to fail to establish a session.

[...]
Build date of WinVNC.exe is 3/16/01 (how do you ask for the version ? :)

On the server, right-click on the VNC mini-icon on the taskbar
and select "About VNC".
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: NT5 / Windows 2000 Server Problem -- session gets hung

[Bruce Lilly]

>>>I do indeed get rfb 003.003 from the local, working VNC server,
>>>from inside the browser.  (some of us forget there is even
>>>a telnet client in browsers :)
>>>
>>>I still get, contacting the hung VNC server, after about a 20 second
>>>delay:
>>>
>>> "Could not open a connection to 216.87.100.43"

That indicates that there's nothing listening on port 5900.
It could be that the VNC service has exited.  If it is in
fact still running, it means that it's not listening again
after a client disconnects, or that something (e.g. a
so-called "personal firewall") is preventing the connection.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Multiple Servers on a Win Machine...

[Bruce Lilly]

> From: "Chad LaFarge" <[EMAIL PROTECTED]>
> Date: Wed, 28 Aug 2002 17:43:01 -0500

> Here is my goal:
> One user in Chicago must control one PC in St Louis
> Five users in New York, L.A., and Seattle must be able to view, but not control the 
>same
> PC
> 
> In other words, I need to give a demo to five remote users on a PC that I can't 
>access
> physically.
[...]
> Can anyone point me in the right direction for this?

If the 5 viewers are also using MS Windows, simply make sure that when
connecting they select "View only" on the options screen available via
the "Options..." button on the first VNCviewer window.  If you cannot
rely on the users to do that one simple thing, have somebody reliable
set up a session that way on thier PCs in advance, then save the
settings via the viewer's "Save settings as..." menu option. Then a
session can be subsequently started with the same options (in this case,
view only).
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Xf4vnc radeon_drv.o doesn't support OpenGL

[Bruce Lilly]

When using the Xf4vnc radeon_drv.o driver, programs
requiring OpenGL support fail, e.g.:

# xtraceroute
OpenGL not supported

With the normal Xfree86 driver, such programs work fine
(but of course there's no built-in vnc support).
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Xf4vnc radeon_drv.o doesn't support OpenGL

[Bruce Lilly]

>>>> From: Alan Hourihane <[EMAIL PROTECTED]>
>>>> Date: Sun, 13 Oct 2002 20:51:24 +0100

>>>>On Fri, Oct 11, 2002 at 07:52:15 -0400, Bruce Lilly wrote:
>>>>
>>>>> > From: Alan Hourihane <[EMAIL PROTECTED]>
>>>>>
>>>>>>What does 'glxinfo' say ?
>>>>>
>>>>># glxinfo
>>>>>name of display: :0.0
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>Error: couldn't find RGB GLX visual
>>>>>
>>>>>visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
>>>>>  id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
>>>>>--
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>0x21 16 tc  0  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>Xlib:  extension "GLX" missing on display ":0.0".
>>>>>0x22 16 dc  0  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
>>>>>
>>>>>
>>>>>>Also, DRI won't work with VNC, so don't load the "dri" module
>>>>>>in your XF86Config file. This will fallback to software mode OpenGL.
>>>>>
>>>>>:(  Anyway, the same problem exists without it loaded.
>>>>
>>>>
>>>>Are you sure you've got
>>>>
>>>>Load "glx"
>>>>
>>>>in your config file ?
>>>>
>>>>The radeon driver doesn't autoload this and it looks like your not
>>>>loading it.

Yes, I'n sure (recall that it works fine withe the standard Xfree86
radeon.o).  The relevant sections are currently:

Section "Module"
   Load "glx"
   Load "dbe"
   Load "type1"
   Load "speedo"
   Load "extmod"
   Load "freetype"
# dri is reportedly incompatible with the vnc drivers
#  Load "dri"
EndSection

# VNC modification entries ...
Section "Module"
   Load  "vnc"
EndSection

I have kept the standard driver and the Xf4vnc driver, and I can
use a symbolic link to select which is used.

# ls -l /usr/X11R6/lib/modules/drivers/*rad*
-rwxr-xr-x1 root root86221 Oct 10 20:59 
/usr/X11R6/lib/modules/drivers/radeon_drv.X4vnc.o
-rwxr-xr-x1 root root86221 Oct 10 21:02 
/usr/X11R6/lib/modules/drivers/radeon_drv.X4vnc.o.bak
lrwxrwxrwx1 root root   18 Oct 10 21:01 
/usr/X11R6/lib/modules/drivers/radeon_drv.o -> radeon_drv.X4vnc.o
-rwxr-xr-x1 root root87103 Mar 25  2002 
/usr/X11R6/lib/modules/drivers/radeon_drv.o.old
-rwxr-xr-x1 root root87103 Mar 25  2002 
/usr/X11R6/lib/modules/drivers/radeon_drv.o.orig

OpenGL programs work fine with the standard driver object file
*with no other changes*, though of course there's then no built-in
VNC support (even with vnc.so loaded).  With the Xf4vnc driver
object file *and no ther changes*, OpenGL programs don't work.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Xf4vnc radeon_drv.o doesn't support OpenGL

[Bruce Lilly]

>> From: Alan Hourihane <[EMAIL PROTECTED]>
>> Date: Mon, 14 Oct 2002 19:07:29 +0100

>>This is the problem. You can't have two Module Sections. Your meant
>>to put the 
>>
>>  Load "vnc"
>>
>>into your existing Module section.

Actually, I had tried to keep the modifications separate so as
to be able to keep track of them better.  It does work now
that I've consolidated the Moduule sections; thanks.  It's
still rather odd that there was no problem with the standard
radeon driver though, only with the vnc-modified one.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Xf4vnc radeon_drv.o doesn't support OpenGL

[Bruce Lilly]

 > From: Alan Hourihane <[EMAIL PROTECTED]>

> What does 'glxinfo' say ?

# glxinfo
name of display: :0.0
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual

visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
  id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
--
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x21 16 tc  0  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x22 16 dc  0  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None

> Also, DRI won't work with VNC, so don't load the "dri" module
> in your XF86Config file. This will fallback to software mode OpenGL.

:(  Anyway, the same problem exists without it loaded.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

x screen

[Aaron Bruce]

I am using vncserver on Red Hat linux 8.whatever is the newest. I am
using vnc viewer on xp. When I run vnc on my linux machine I can connect
just find to it from windows, however it will not let me run startx (my
gui) It says something about a pam error and maybe I don't have console
ownership. I am fairly new to linux and vnc, however I do know for a
fact that I have console ownership when I'm logged in as root. Any
suggestions would be appreciated.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

more vnc stuff on my l-box

[Aaron Bruce]

I used the http://www.sourcecodecorner.com/articles/vnc/linux.asp setup,
now what do I run if I want to have a gui through vnc?
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Implementing Audio into a Linux based system that uses VNC

[Bruce Lilly]

From: "William Hooper" <[EMAIL PROTECTED]>
Date: Tue, 12 Nov 2002 08:22:32 -0500



So you would have the VNC programmers not only add this component, but
also port it to the different platforms the VNC runs on, and try to keep
up with new versions/security of someone else's code?


Sound support need not use a particular implementation.  It might
be more efficient than reinventing the wheel, but it's not a
necessity.


Not to mention how "big" VNC might get adding this code (I haven't
looked so I don't know how "big" nasd would be).


So it's an open issue until somebody actually determines the size
implications.


Just saying "Add sound support" doesn't make it easy.  I for one agree
with the fact VNC does it's one thing well, why try to tack on more
things to make it more complex?


If the "one thing" is remoting the human-computer interface, VNC
lacks sound support, which is an integral part of the HCI, so cannot
be said to do that well.  If the "one thing" is mere remote frame buffer
display, then you're effectively arguing that mouse and keyboard support
should be ripped out to reduce size.  Is that really your opinion?

Some other requests for added features which are frequently proposed
(e.g. file transfer, printing) are unrelated to the HCI;
moreover, there are readily available auxiliary programs (e.g. ftp, lpr/lpd)
which provide those features.  The same cannot be said for sound support.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Accessing multiple VNC servers using only one SSH port?

[Bruce Atherton]

I've gone through the FAQ and mailing list looking for an answer to this 
problem, but so far I haven't seen anything relevant. Sorry if I just 
missed it.

I'm trying to figure out a way to use a single open port on a firewall to 
connect to one of several VNC servers. Something like this (apologies to 
the proportional font crowd):

-- VNC Server 1
|
  Client -> Internet -> Firewall -> SSH  ---|- VNC Server 2
port 22Server   |
-- VNC Server 3

If you already have a solution for this problem that works, I would love to 
hear about it. If not, then I have a way to get this behaviour but I don't 
know how to set it up currently, and would love some advice.

This isn't a hard problem from an architecture point of view. The SSH 
server could have a program run by the client that opened a socket to a 
named machine and port and that returned that socket on its standard out. 
The VNC client could have a facility for communicating over its standard 
in, piped in from the ssh client (after dealing with the password).

So, if a program on the SSH server was called "opensocket" and the firewall 
was configured to forward port 22 to the SSH server, on the client you 
could run something like:

ssh firewall.my.org opensocket vnc1.my.org 5901 | vncviewer -

and have it all just work, even if multiple clients are connecting to 
different servers across the firewall at the same time.

Due to blocking you may not want to use pipes, but you get the idea. Does 
anyone know of any way of accomplishing something like this?

Any ideas at all gratefully accepted. Thanks.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Accessing multiple VNC servers using only one SSH port?

[Bruce Atherton]

At 04:39 PM 11/18/2002 -0500, William Hooper wrote:


You don't mention what operating systems are involved


No, because I didn't think it was relevant. In my particular case, the 
machines can be any combination of Windows, Linux, and Solaris boxes that 
you want. Does that help?

, but I believe
this is answered on the "Using VNC with SSH" page (
http://www.uk.research.att.com/vnc/sshvnc.html ) under "more advanced
use".  All communication over the Internet is handled by SSH port
forwarding.


Unfortunately, that page does not deal with my usecase at all. It shows you 
how to forward a port in longer and longer chains of machines, but it does 
not (according to my reading of it) say anything about accessing multiple 
machines with a single forwarded port. In each case, the port is being 
forwarded to only one possible ultimate destination.

Let me describe the usecase in text instead of using a diagram, it may be 
clearer.

From home or on the road with my laptop, I often need to get access to one 
of several machines in my office, not just a terminal but the whole 
desktop. I may need to get at my workstation or a machine running automated 
tests or one of several servers. I don't know ahead of time exactly which 
of several machines I will need access to. There are several other 
developers in my office with the same need. What we all have to work with 
is a single SSH port that has been opened up in the firewall for remote access.

I think this scenario is probably fairly common. Running gotomypc on each 
of the machines would be a solution, but the company frowns on that as a 
security breach and is not willing to pay for subscriptions to it. So I am 
trying to find another way, and I was hoping that the combination of VNC 
and SSH might give it to me.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Accessing multiple VNC servers using only one SSH port?

[Bruce Atherton]

Thanks to everyone who replied. The answers have clarified my thinking so I 
can see where I went wrong in pondering the problem. I neglected to mention 
that the environment behind the firewall is NATed, so I got confused trying 
to figure out how the client could forward to an internal address.

Of course, the client does NOT resolve the internal address. Instead, it 
forwards the tunnel request to the SSHD daemon behind the firewall and lets 
it sort the routing out. And, as William pointed out, all the tunnelling 
does take place through port 22 on the firewall so there is no need for 
more ports. Just running multiple tunnels, each to a separate machine, 
cleanly solves the problem through the one port.

My apologies for wasting bandwidth on my sloppy thinking.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

logging out of display manager...

[Bruce Douglas]

Hi...

Relatively new to VNC.. I have the VNC server steup on a Linux box. I have
it configured to use GNOME as the display manager. I'm able to connect using
a client eith no problem. The issue I'm trying to better understand has to
do with logging out or stopping the session of VNC on the server. When I
logout of the session on the Linux box, (using the "Logout" button from
GNOME), the screen seems to still leave a term window running.

My question, is there a way to kill the session of the GNOME display window,
without killing the vncserver? Or, do I not quite uunderstand how to use
VNC. I assumed that once I had the VNC server running, I could more or less
remotely log into the Linux bos, using VNC to remotely display the desktop.
I'm really just looking for the right/correct way to shut down/kill the
desktop.

Also, if I want to allow multiple sessions/users to connect to the Linux
box, do I have to start multiple sessions/display windows during the initial
startup of VNC??

Thanks

Bruce Douglas
[EMAIL PROTECTED]
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC Viewer and Server, and port numbers/display numbers

[Bruce Douglas]

hi...

new to vnc.. so bear with me

isn't this what SSH is supposed to address...

Bruce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, December 11, 2002 9:53 AM
To: [EMAIL PROTECTED]
Subject: VNC Viewer and Server, and port numbers/display numbers


I run PCAnywhere in something of a 'stealth' configuration, with encryptions
and cryptic passwords, etc. to make it as difficult a possible for someone
to hack my home PC while it is listening on the internet for my connection.

Once in awhile PCAnywhere hangs and I can't get back in.  That's where VNC
is handy, because I can usually get in to my PC and fix whatever is wrong
with the PCAnywhere host.

I have VNC server listening on a non-standard and high port number, and also
have a large display number configured.  I have a very cryptic password as
well.

I feel like this is still a very insecure setup exposed to the net, because
VNCViewer only needs to be told the display number, it doesn't have to be
told the port number to connect to.  The display numbers aren't very big
numbers, so it wouldn't take a hacker long to loop through them all and find
the one I'm using.  Then crack my password and he is into my PC.

Are there any plans to be able to configure VNCServer such that VNCViewer
must also know the port number, in addition to the display number, before it
can connect?  That would help the security quite a bit I think.

If there is a way to do this now, I would like to know.  I've looked through
the online documentation but did not see anything to prevent VNCViewer from
connecting unless it knows the port number too.

Sorry for a long email, thank you for your time.

Regards,
Sue Morton
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: logging out of display manager...

[Bruce Douglas]

Chris,

Thanks for your response But I'm still confused What should be the
process for starting/using vnc...

Should I :
1) SSH into the Linux box
2) Start the vncserver - keep this window running (and how do i know the
correct display number)
3) Start my client
4) Kill the vncserver from the SSH term
5) Kill the SSH term

This effectively keeps a SSH Term running for the duration, while I'm
running VNC Client. But it  also kills the VNC server when finished...

OR...
1) SSH into the Linux box
2) Start the vncserver - create multiple windows, each with a different
display number
3) Have the user(s) start their client(s)

But don't I still need to know how to stop/restart the VNC session on the
Server. Otherwise, it   never gets released.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Christopher Tesla
Sent: Wednesday, December 11, 2002 9:03 AM
To: Bruce Douglas; [EMAIL PROTECTED]
Subject: RE: logging out of display manager...


What I have tried to do is force VNC to restart the session using a command
in the .twmrc menu called Restart.

I have several VNC sessions running on a RedHat 7.2 server.  I want each
user to be able to shutdown and restart their VNC connection if they want
(for instance, if they make any changes to their shell settings).

I thought that sending this command:

vncserver -kill :1 | sleep 3 | vncserver :1

would kill the VNC session running on port 1, wait, then restart the server
on port 1.  Well, the kill command works fine, but the session never starts
up again.

I even tried sending the commands via su:

su username -c "vncserver -kill :1 | sleep 3 | vncserver :1"

but that did the same thing.

The only way to make this work so far is I allow the users to Quit (not
Restart) and then I start their session manually.  Very stinky, but the
users don't restart their sessions too frequently.

If anybody has any ideas, I would be happy to hear them.

> -----Original Message-
> From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: logging out of display manager...
>
>
> Hi...
>
> Relatively new to VNC.. I have the VNC server steup on a
> Linux box. I have
> it configured to use GNOME as the display manager. I'm able
> to connect using
> a client eith no problem. The issue I'm trying to better
> understand has to
> do with logging out or stopping the session of VNC on the
> server. When I
> logout of the session on the Linux box, (using the "Logout"
> button from
> GNOME), the screen seems to still leave a term window running.
>
> My question, is there a way to kill the session of the GNOME
> display window,
> without killing the vncserver? Or, do I not quite uunderstand
> how to use
> VNC. I assumed that once I had the VNC server running, I
> could more or less
> remotely log into the Linux bos, using VNC to remotely
> display the desktop.
> I'm really just looking for the right/correct way to shut
> down/kill the
> desktop.
>
> Also, if I want to allow multiple sessions/users to connect
> to the Linux
> box, do I have to start multiple sessions/display windows
> during the initial
> startup of VNC??
>
> Thanks
>
> Bruce Douglas
> [EMAIL PROTECTED]
> ___
> VNC-List mailing list
> [EMAIL PROTECTED]
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: logging out of display manager...

[Bruce Douglas]

ok...

Here's what should be a simple question.. but I can't seem to find the
answer

Is there an easy way to determine which display device numbers are in use at
a given time?

Thanks...

Bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Christopher Tesla
Sent: Wednesday, December 11, 2002 10:29 AM
To: [EMAIL PROTECTED]
Subject: RE: logging out of display manager...


This is my process for starting VNC on my Linux box:

1) Telnet in the box

2)  I run a script, as root, that SUs as each user and starts a VNC server
on different ports:

su user1 -c "vncserver :1"
su user2 -c "vncserver :2"
su user3 -c "vncserver :3"
etc.

3)  Now each user can activate their client and connect to SERVER:x where x
is the port number assigned to them.


Now, lets say that user2 makes some changes to her .twmrc file (say, make
the background a different color).  That change will not take appear until
the VNC server is restarted.  The way it works now:

1) I telnet into server
2) I SU as user2
3) I run "vncserver -kill :2"
3) I run "vncserver :2"
4) I exit SU
5) I quit telnet

Now the user can re-connect to their port (2) and they will see the changes
they have made.  And actually, I have a script for each user that does steps
2-4 above.  So I just run "vncrestart-user2" as root and it does it all for
me.

What I want is a method for the user to perform steps 2-4 on their
own...without having to telnet into the server and run the commands from the
shell.  But if user2 is connected via VNC and they run a script that should
shut down their vnc session, wait, then restart it...the restart command
never takes.

I hope this answers your question, although it raises one of my own!  :)

> -Original Message-
> From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 1:06 PM
> To: Christopher Tesla; [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> Chris,
>
> Thanks for your response But I'm still confused What
> should be the
> process for starting/using vnc...
>
> Should I :
>   1) SSH into the Linux box
>   2) Start the vncserver - keep this window running (and
> how do i know the
> correct display number)
>   3) Start my client
>   4) Kill the vncserver from the SSH term
>   5) Kill the SSH term
>
>   This effectively keeps a SSH Term running for the
> duration, while I'm
> running VNC Client. But italso kills the VNC server when
> finished...
>
> OR...
>   1) SSH into the Linux box
>   2) Start the vncserver - create multiple windows, each
> with a different
> display number
>   3) Have the user(s) start their client(s)
>
>   But don't I still need to know how to stop/restart the
> VNC session on the
> Server. Otherwise, it     never gets released.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Christopher Tesla
> Sent: Wednesday, December 11, 2002 9:03 AM
> To: Bruce Douglas; [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> What I have tried to do is force VNC to restart the session
> using a command
> in the .twmrc menu called Restart.
>
> I have several VNC sessions running on a RedHat 7.2 server.
> I want each
> user to be able to shutdown and restart their VNC connection
> if they want
> (for instance, if they make any changes to their shell settings).
>
> I thought that sending this command:
>
> vncserver -kill :1 | sleep 3 | vncserver :1
>
> would kill the VNC session running on port 1, wait, then
> restart the server
> on port 1.  Well, the kill command works fine, but the
> session never starts
> up again.
>
> I even tried sending the commands via su:
>
> su username -c "vncserver -kill :1 | sleep 3 | vncserver :1"
>
> but that did the same thing.
>
> The only way to make this work so far is I allow the users to
> Quit (not
> Restart) and then I start their session manually.  Very
> stinky, but the
> users don't restart their sessions too frequently.
>
> If anybody has any ideas, I would be happy to hear them.
>
> > -Original Message-
> > From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, December 11, 2002 11:41 AM
> > To: [EMAIL PROTECTED]
> > Subject: logging out of display manager...
> >
> >
> > Hi...
> >
> > Relatively new to VNC.. I have the VNC server steup on a
> > Linux box. I have
> > it configured to use GNOME as the display manager. I'm able
> > to connect using
> > a client eith no problem. The issue I'm trying to bet

RE: logging out of display manager...

[Bruce Douglas]

ok...

another question... if I have created multiple VNC sessions/displays such
that I'm able to connect using a client. If I kill my client, how do I stop
someone else from being able to access my desktop if they connect to their
vnc client using the same display number.

I ask this because it appears that when i setup the vncserver, I give it a
passowrd, which is also required for each client connecting to the linux
box. However, the password doesn't change, so anybody could access my
desktop... assuming they know the vncserver password. Is there a way to have
"multiple" passwords, one each for a different display/user????

thanks...

bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Christopher Tesla
Sent: Wednesday, December 11, 2002 11:06 AM
To: Bruce Douglas; [EMAIL PROTECTED]
Subject: RE: logging out of display manager...


This is not 100% true all the time, but...

If you go to your /tmp/.X11-unix directory there will be a file for each
server that is running.  For instance:

/tmp/.X11-unix
ls -a
X0
X1
X2
X3
X4

Means you have a VNC server running on ports :0 :1 :2 :3 :4

Again, I have had instances where the VNC server was down, but the X file
was still there.  But in most cases this will give you the proper info.

C-ya
Chris

> -Original Message-
> From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 1:59 PM
> To: Christopher Tesla; [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> ok...
>
> Here's what should be a simple question.. but I can't seem to find the
> answer
>
> Is there an easy way to determine which display device
> numbers are in use at
> a given time?
>
> Thanks...
>
> Bruce
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Christopher Tesla
> Sent: Wednesday, December 11, 2002 10:29 AM
> To: [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> This is my process for starting VNC on my Linux box:
>
> 1) Telnet in the box
>
> 2)  I run a script, as root, that SUs as each user and starts
> a VNC server
> on different ports:
>
> su user1 -c "vncserver :1"
> su user2 -c "vncserver :2"
> su user3 -c "vncserver :3"
> etc.
>
> 3)  Now each user can activate their client and connect to
> SERVER:x where x
> is the port number assigned to them.
>
>
> Now, lets say that user2 makes some changes to her .twmrc
> file (say, make
> the background a different color).  That change will not take
> appear until
> the VNC server is restarted.  The way it works now:
>
> 1) I telnet into server
> 2) I SU as user2
> 3) I run "vncserver -kill :2"
> 3) I run "vncserver :2"
> 4) I exit SU
> 5) I quit telnet
>
> Now the user can re-connect to their port (2) and they will
> see the changes
> they have made.  And actually, I have a script for each user
> that does steps
> 2-4 above.  So I just run "vncrestart-user2" as root and it
> does it all for
> me.
>
> What I want is a method for the user to perform steps 2-4 on their
> own...without having to telnet into the server and run the
> commands from the
> shell.  But if user2 is connected via VNC and they run a
> script that should
> shut down their vnc session, wait, then restart it...the
> restart command
> never takes.
>
> I hope this answers your question, although it raises one of
> my own!  :)
>
> > -Original Message-
> > From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, December 11, 2002 1:06 PM
> > To: Christopher Tesla; [EMAIL PROTECTED]
> > Subject: RE: logging out of display manager...
> >
> >
> > Chris,
> >
> > Thanks for your response But I'm still confused What
> > should be the
> > process for starting/using vnc...
> >
> > Should I :
> > 1) SSH into the Linux box
> > 2) Start the vncserver - keep this window running (and
> > how do i know the
> > correct display number)
> > 3) Start my client
> > 4) Kill the vncserver from the SSH term
> > 5) Kill the SSH term
> >
> > This effectively keeps a SSH Term running for the
> > duration, while I'm
> > running VNC Client. But it  also kills the VNC server when
> > finished...
> >
> > OR...
> > 1) SSH into the Linux box
> > 2) Start the vncserver - create multiple windows, each
> > with a different
> > display number
> > 3) Have the user(s) start their client(s)
> >
> > But don't I still need to know 

RE: logging out of display manager...

[Bruce Douglas]

chris...

my bad... I kind of realized this after I issued the question My
problem/question came as I was using the same linux accoutn for all my
tests

However, the user still has to "know" which display id matches his/her
account

thanks...

bruce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Christopher Tesla
Sent: Wednesday, December 11, 2002 12:12 PM
To: Bruce Douglas; [EMAIL PROTECTED]
Subject: RE: logging out of display manager...


What you need to do is make the password different depending on what user
account you use to create the VNC session.

For instance,

Linux account: user1
Linux password: user1-pwd

As root, I issue the command "su user1".  Then, as user1, I issue the
command "vncserver :1".  If this is the first time I have ever run the
command I will be prompted for the password.  I put in "user1-pwd".  Now
there is a VNC session running on the Linux box on port 1.

Using the client, I connect to LINUXBOX:1.  It prompts me for a password.
The password will be the Linux password of user1.

So if you set it up this way, the only way someone could connect to your VNC
session running on a specific port is if they know your Linux password
(which they don't, because you follow good password protocols!).

What you don't want to do is have a generic VNC password that everyone knows
for your Linux user account or (gasp) the root account.  Each user should
have their own Linux account, with a VNC server session running on a
specific port for that account with the VNC password the same as their login
password.

C-ya
Chris



> -Original Message-
> From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 2:51 PM
> To: Christopher Tesla; [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> ok...
>
> another question... if I have created multiple VNC
> sessions/displays such
> that I'm able to connect using a client. If I kill my client,
> how do I stop
> someone else from being able to access my desktop if they
> connect to their
> vnc client using the same display number.
>
> I ask this because it appears that when i setup the
> vncserver, I give it a
> passowrd, which is also required for each client connecting
> to the linux
> box. However, the password doesn't change, so anybody could access my
> desktop... assuming they know the vncserver password. Is
> there a way to have
> "multiple" passwords, one each for a different display/user
>
> thanks...
>
> bruce
>
>
> -----Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Christopher Tesla
> Sent: Wednesday, December 11, 2002 11:06 AM
> To: Bruce Douglas; [EMAIL PROTECTED]
> Subject: RE: logging out of display manager...
>
>
> This is not 100% true all the time, but...
>
> If you go to your /tmp/.X11-unix directory there will be a
> file for each
> server that is running.  For instance:
>
> /tmp/.X11-unix
> ls -a
> X0
> X1
> X2
> X3
> X4
>
> Means you have a VNC server running on ports :0 :1 :2 :3 :4
>
> Again, I have had instances where the VNC server was down,
> but the X file
> was still there.  But in most cases this will give you the
> proper info.
>
> C-ya
> Chris
>
> > -Original Message-
> > From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, December 11, 2002 1:59 PM
> > To: Christopher Tesla; [EMAIL PROTECTED]
> > Subject: RE: logging out of display manager...
> >
> >
> > ok...
> >
> > Here's what should be a simple question.. but I can't seem
> to find the
> > answer
> >
> > Is there an easy way to determine which display device
> > numbers are in use at
> > a given time?
> >
> > Thanks...
> >
> > Bruce
> >
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Christopher Tesla
> > Sent: Wednesday, December 11, 2002 10:29 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: logging out of display manager...
> >
> >
> > This is my process for starting VNC on my Linux box:
> >
> > 1) Telnet in the box
> >
> > 2)  I run a script, as root, that SUs as each user and starts
> > a VNC server
> > on different ports:
> >
> > su user1 -c "vncserver :1"
> > su user2 -c "vncserver :2"
> > su user3 -c "vncserver :3"
> > etc.
> >
> > 3)  Now each user can activate their client and connect to
> > SERVER:x where x
> > is the port number assigned to them.
> >

RE: Linksys & VNC still not working

[Bruce Douglas]

Lorenzo,

In the event you haven't already done this... Make sure you're able to go
from your client to your server, assuming that both are behind the
firewall... Better yet, make sure you can use VNC to go from your client to
the server without the router. In other words, can you set up a direct
connection from your client PC to your server with VNC without the router?

Also provide additional information as to the physical setup/applications
used. Are these systems Windows/Linux, are you using SSH tunneling, etc...

Give us a rough overview of how your setup is configured.

Using VNC/Linksys/SSH works... I'm doing it now. My server is sitting behind
a AT&T cable moden, with a Linksys router. I use Putty to set up a SSH
tunnel. I can remotely access my linux boxes.

The issue that you have to do is make sure the router forwards the
connection to the correct port. In order to do this you need to make sure
that you can actually get to the server without the router. This also lets
you look at the IP/port that VNC is really using when you make the
connection. After you have verified that you have the actual IP/port, you
can configure the router to forward the external incoming IP/port to the
internal IP/port.

It gets tricky if you use tunneling as you still have to setup the SSH app
to do a redirect/forward but it's doable...

Let us know what you find out...

Regards,

Bruce
[EMAIL PROTECTED]




-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Lorenzo Gutierrez
Sent: Friday, December 13, 2002 10:20 PM
To: [EMAIL PROTECTED]
Subject: Linksys & VNC still not working


Greetings,

I've completed a thorough search through the posting
to configure my router appropriatly to no avail. Can
someone help?

I have a linksys router BEFW11S4 with the latest
firmware installed.  I use Comacst cable internet
access.

I have the following configurations on the router:
Filters:
Enable MTU 1492
Disabel Block WAN Request
Forwarding:
5900 to 6000 TCP [IP of LAN side server] Enable
5800 to 5800 TCP ["] Enable

Nothing enabled under UPnP nor Port Triggering

When testing this out from a computer WITHIN and
OUTSIDE my LAN using the external IP of router
(68.35.xxx.xxx), it's Default Getway IP(68.35.xxx.x),
and it's LAN IP address (from within the LAN of
course) WITH and WITHOUT the ":5900" port designation
(i.e., 68.35.###.###:5900).  It waits for a bit like
it's going to connect then I get an error "Connection
to Server Failed"  (So close yet so far).

I've tried DHCP enabled and disabled.  I'm at a loss.
I want to play too!  I'd appreciate some guidance.

Sincerely frustrated,

Lorenzo


=
Regards,

Lorenzo Gutierrez
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

vnc .. black vnc client screen

[Bruce Douglas]

Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix box (GNOME) as I should)

In keeping everything simple, I'm trying to fire up a Windows VNC Client to
talk to a Linux VNC Server.

However, When I run the VNC Client (Windows) a black window is displayed.
This used to work before (I think)!!! I've done a lot of rewiring/etc.. I
can't really say that everything has actually worked on this box!!

I run vncserver on the unix box. It appears that I have multiple VNC
displays running. I'm new to unix, so I don't know how to go about actually
checking to see which displays are actually running.

Any help/assistance would be greatly appreciated. Or any pointers to online
docs/etc

Thanks

Bruce Douglas
[EMAIL PROTECTED]

PS. As I stated, I could have sworn that I had everything working at one
time!!!
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc .. black vnc client screen

[Bruce Douglas]

ps...

I notice that the Windows Client consumes all the Windows CPU resources

regards.

Bruce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: vnc .. black vnc client screen


Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix box (GNOME) as I should)

In keeping everything simple, I'm trying to fire up a Windows VNC Client to
talk to a Linux VNC Server.

However, When I run the VNC Client (Windows) a black window is displayed.
This used to work before (I think)!!! I've done a lot of rewiring/etc.. I
can't really say that everything has actually worked on this box!!

I run vncserver on the unix box. It appears that I have multiple VNC
displays running. I'm new to unix, so I don't know how to go about actually
checking to see which displays are actually running.

Any help/assistance would be greatly appreciated. Or any pointers to online
docs/etc

Thanks

Bruce Douglas
[EMAIL PROTECTED]

PS. As I stated, I could have sworn that I had everything working at one
time!!!
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc .. black vnc client screen

[Bruce Douglas]

ps...

my xstartup file (.vnc/xstartup) is

/
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &

gnome-session &
/////

-bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: vnc .. black vnc client screen


Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix box (GNOME) as I should)

In keeping everything simple, I'm trying to fire up a Windows VNC Client to
talk to a Linux VNC Server.

However, When I run the VNC Client (Windows) a black window is displayed.
This used to work before (I think)!!! I've done a lot of rewiring/etc.. I
can't really say that everything has actually worked on this box!!

I run vncserver on the unix box. It appears that I have multiple VNC
displays running. I'm new to unix, so I don't know how to go about actually
checking to see which displays are actually running.

Any help/assistance would be greatly appreciated. Or any pointers to online
docs/etc

Thanks

Bruce Douglas
[EMAIL PROTECTED]

PS. As I stated, I could have sworn that I had everything working at one
time!!!
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc .. black vnc client screen

[Bruce Douglas]

hi...

my lserver2:2.log file follows:

03/01/03 08:57:12 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
03/01/03 08:57:12 Copyright (C) 2002 RealVNC Ltd.
03/01/03 08:57:12 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
03/01/03 08:57:12 All Rights Reserved.
03/01/03 08:57:12 See http://www.realvnc.com for information on VNC
03/01/03 08:57:12 Desktop name 'X' (lserver2:1)
03/01/03 08:57:12 Protocol version supported 3.3
03/01/03 08:57:12 Listening for VNC connections on TCP port 5901
03/01/03 08:57:12 Listening for HTTP connections on TCP port 5801
03/01/03 08:57:12   URL http://lserver2:5801
SESSION_MANAGER=local/lserver2:/tmp/.ICE-unix/904
Loaded background '0x8097490
AUDIT: Fri Jan  3 08:57:19 2003: 896 Xvnc: client 4 rejected from local host
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Unable to open desktop file
applications:///Office/redhat-word-processor.desktop
 for panel launcher: Error reading file
'applications:///Office/redhat-word-proc
essor.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-presentations.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-presentati
ons.desktop': File not found
--More--(84%)


my xstartup is below...

[root@lserver2 root]# more .vnc/xstartup
#!/bin/sh

unset SESSION MANAGER

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &
gnome-session &


I still cnnot figure out why i'm getting a blck screen when i try to connect
via a Windows vncviewer. I believe whatever I'm experiencing is also causing
my Windows box to consume all CPU cycles. As I stated earlier... the http
java client performs as I expect.

thanks

bruce
[EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:47 PM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


ps...

my xstartup file (.vnc/xstartup) is

/
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &

gnome-session &
/////

-bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: vnc .. black vnc client screen


Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix box (GNOME) as I should)

In keeping everything simple, I'm trying to fire up a Windows VNC Client to
talk to a Linux VNC Server.

However, When I run the VNC Client (Windows) a black window is displayed.
This used to work before (I think)!!! I've done a lot of rewiring/etc.. I
can't really say that everything has actually worked on this box!!

I run vncserver on the unix box. It appears that I have multiple VNC
displays running. I'm new to unix, so I don't know how to go about actually
checking to see which displays are actually running.

Any help/assistance would be greatly appreciated. Or any pointers to online
docs/etc

Thanks

Bruce Douglas
[EMAIL PROTECTED]

PS. As I stated, I could have sworn that I had everything working at one
time!!!
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc .. black vnc client screen

[Bruce Douglas]

-Original Message-
From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 3:33 AM
To: 'Bruce Douglas'
Subject: RE: vnc .. black vnc client screen


hi...

ok.. now this is simply getting more confusing

i've decided to go back and start fom the beginning...

how does one completely remove/uninstall the vnc package. (is there an
uninstall rpm function within linux??)

what are the correct steps for building/installing a vnc server for a redhat
(8.0) linux platform???

i've seen plenty of msgs that point to a "/etc/sysconfig/vncservers" file. I
don't have this file on any of the boxes where i've selected vnc from the
linux/redhat distro when i was installing linux. in fact, i can't seem to
find vnc on any of the boxes where i've tried to install vnc as part of the
linux install process. (i've only had it initially work when i did the vnc
install by hand...)

so, in essence, i'm trying to find some form of docs/pointers to a sequence
of steps for installing the VNC server on a linux box in a repeatable
fashion

the docs that i found on the realvnc site weren't that helpful.

by the way, where does the vncservers file come from, and what should be in
it. is there any doc/set of docs that describes the various setup files
required and what they should include.

Thanks

Bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 10:11 PM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


hi...

my lserver2:2.log file follows:

03/01/03 08:57:12 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
03/01/03 08:57:12 Copyright (C) 2002 RealVNC Ltd.
03/01/03 08:57:12 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
03/01/03 08:57:12 All Rights Reserved.
03/01/03 08:57:12 See http://www.realvnc.com for information on VNC
03/01/03 08:57:12 Desktop name 'X' (lserver2:1)
03/01/03 08:57:12 Protocol version supported 3.3
03/01/03 08:57:12 Listening for VNC connections on TCP port 5901
03/01/03 08:57:12 Listening for HTTP connections on TCP port 5801
03/01/03 08:57:12   URL http://lserver2:5801
SESSION_MANAGER=local/lserver2:/tmp/.ICE-unix/904
Loaded background '0x8097490
AUDIT: Fri Jan  3 08:57:19 2003: 896 Xvnc: client 4 rejected from local host
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Unable to open desktop file
applications:///Office/redhat-word-processor.desktop
 for panel launcher: Error reading file
'applications:///Office/redhat-word-proc
essor.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-presentations.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-presentati
ons.desktop': File not found
--More--(84%)


my xstartup is below...

[root@lserver2 root]# more .vnc/xstartup
#!/bin/sh

unset SESSION MANAGER

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &
gnome-session &


I still cnnot figure out why i'm getting a blck screen when i try to connect
via a Windows vncviewer. I believe whatever I'm experiencing is also causing
my Windows box to consume all CPU cycles. As I stated earlier... the http
java client performs as I expect.

thanks

bruce
[EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:47 PM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


ps...

my xstartup file (.vnc/xstartup) is

/
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &

gnome-session &
/

-bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: vnc .. black vnc client screen


Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix box (GNOME) as I should)

In keeping everything simple, I'm trying to fire up a Windows VNC Client to
talk to a Linux VNC Server.

However, When I run the VNC Client (Windows) a black window is displayed.
This used to work before (I think)!!! I've done a lot of rewiring/etc.. I
can't really say that everything has actually worked on this box!!

I run vncserver on the unix box. It appears that I have multiple VNC
displays running. I'm new

RE: Windows client consuming CPU resources

[Bruce Douglas]

I do have the latest viewer/server from realvnc as of jan3, 2003!!

thanks

bruce...



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Carl
Sent: Saturday, January 04, 2003 4:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Windows client consuming CPU resources


Bruce,

> I notice that the Windows Client consumes all the Windows CPU
resources

Are you sure you have the latest version?  I remember older version used to
eat away at the CPU but the latest is really low overhead and stable.

Carl
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc .. black vnc client screen

[Bruce Douglas]

update...

went back to the beginning...

for server:
1) loaded redhat 8.0 linux onto a clean box
2) copied latest version of VNC server from realvnc site (rpm for redhat
7.3)
(didn't know how to build the tar version, but this shouldn't be an issue)
3) modified xstartup file for gnome
4) rebooted linux box

i'm not going through any firewalls.. the client box is a windows 2000 box.
the server is
a linux redhat 8.0 box.

for client:
1) verified via the java browser... http://foo.com:5801 (works)
2) used the vncviewer client
the client starts a window. the window is blank/black. gnome does not seem
to start

the log file results are:

===
[root@lserver1 root]# more .vnc/lserver1:2.log
04/01/03 06:45:01 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
04/01/03 06:45:01 Copyright (C) 2002 RealVNC Ltd.
04/01/03 06:45:01 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
04/01/03 06:45:01 All Rights Reserved.
04/01/03 06:45:01 See http://www.realvnc.com for information on VNC
04/01/03 06:45:01 Desktop name 'X' (lserver1:2)
04/01/03 06:45:01 Protocol version supported 3.3
04/01/03 06:45:01 Listening for VNC connections on TCP port 5902
04/01/03 06:45:01 Listening for HTTP connections on TCP port 5802
04/01/03 06:45:01   URL http://lserver1:5802
SESSION_MANAGER=local/lserver1:/tmp/.ICE-unix/1028
Loaded background '0x8095970
Xlib:  extension "RENDER" missing on display ":2.0".
Xlib:  extension "RENDER" missing on display ":2.0".
Xlib:  extension "RENDER" missing on display ":2.0".
Unable to open desktop file applications:///Internet/redhat-email.desktop
for pa
nel launcher: Error reading file
'applications:///Internet/redhat-email.desktop'
: File not found
Unable to open desktop file
applications:///Office/redhat-word-processor.desktop
 for panel launcher: Error reading file
'applications:///Office/redhat-word-proc
essor.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-presentations.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-presentati
ons.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-spreadsheet.desktop fo
r panel launcher: Error reading file
'applications:///Office/redhat-spreadsheet.
desktop': File not found
Xlib:  extension "RENDER" missing on display ":2.0".

04/01/03 06:45:38 Got connection from client 192.168.1.3
04/01/03 06:45:38 Protocol version 3.3
04/01/03 06:46:01 Client 192.168.1.3 gone
04/01/03 06:46:01 Statistics:
04/01/03 06:46:01   key events received 0, pointer events 4
04/01/03 06:46:01   framebuffer updates 0, rectangles 0, bytes 0


==

the xstartup file is:

---
#!/bin/sh
#unset SESSION MANAGER

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

unset SESSION MANAGER

gnome-session &
#bed twm &
---

the bottom line.. i'm still having the same issues that i've been dealing
with
for the past couple of days... the weird thing is that this was initially
working,
or at least i thought it was...




[root@lserver1 root]#
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Saturday, January 04, 2003 3:38 AM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


-Original Message-
From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 3:33 AM
To: 'Bruce Douglas'
Subject: RE: vnc .. black vnc client screen


hi...

ok.. now this is simply getting more confusing

i've decided to go back and start fom the beginning...

how does one completely remove/uninstall the vnc package. (is there an
uninstall rpm function within linux??)

what are the correct steps for building/installing a vnc server for a redhat
(8.0) linux platform???

i've seen plenty of msgs that point to a "/etc/sysconfig/vncservers" file. I
don't have this file on any of the boxes where i've selected vnc from the
linux/redhat distro when i was installing linux. in fact, i can't seem to
find vnc on any of the boxes where i've tried to install vnc as part of the
linux install process. (i've only had it initially work when i did the vnc
install by hand...)

so, in essence, i'm trying to find some form of docs/pointers to a sequence
of steps for installing the VNC server on a linux box in a repeatable
fashion

the docs that i found on the realvnc site weren't that helpful.

by the way, where does the vncservers file come from, and wha

RE: vnc .. black vnc client screen

[Bruce Douglas]

jack...

thanks for your help... the following are the steps i took (prior to seeing
your response).

for server:
1) loaded redhat 8.0 linux onto a clean box
2) copied latest version of VNC server from realvnc site (rpm for redhat
7.3)
(didn't know how to build the tar version, but this shouldn't be an issue)
3) modified xstartup file for gnome
4) rebooted linux box
5) logged in and started vncserver (vncserver:1, vncserver:2)

i'm not going through any firewalls.. the client box is a windows 2000 box.
the server is
a linux redhat 8.0 box.

for client:
1) verified via the java browser... http://foo.com:5801 (works)
2) used the vncviewer client xxx.yyy:1 (:2,:3)
(if i didn't have the ip address/password correct, an error would display)
the client starts a window. the window is blank/black. gnome does not seem
to start

the log file results are:

===
[root@lserver1 root]# more .vnc/lserver1:2.log
04/01/03 06:45:01 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
04/01/03 06:45:01 Copyright (C) 2002 RealVNC Ltd.
04/01/03 06:45:01 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
04/01/03 06:45:01 All Rights Reserved.
04/01/03 06:45:01 See http://www.realvnc.com for information on VNC
04/01/03 06:45:01 Desktop name 'X' (lserver1:2)
04/01/03 06:45:01 Protocol version supported 3.3
04/01/03 06:45:01 Listening for VNC connections on TCP port 5902
04/01/03 06:45:01 Listening for HTTP connections on TCP port 5802
04/01/03 06:45:01   URL http://lserver1:5802
SESSION_MANAGER=local/lserver1:/tmp/.ICE-unix/1028
Loaded background '0x8095970
Xlib:  extension "RENDER" missing on display ":2.0".
Xlib:  extension "RENDER" missing on display ":2.0".
Xlib:  extension "RENDER" missing on display ":2.0".
Unable to open desktop file applications:///Internet/redhat-email.desktop
for pa
nel launcher: Error reading file
'applications:///Internet/redhat-email.desktop'
: File not found
Unable to open desktop file
applications:///Office/redhat-word-processor.desktop
 for panel launcher: Error reading file
'applications:///Office/redhat-word-proc
essor.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-presentations.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-presentati
ons.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-spreadsheet.desktop fo
r panel launcher: Error reading file
'applications:///Office/redhat-spreadsheet.
desktop': File not found
Xlib:  extension "RENDER" missing on display ":2.0".

04/01/03 06:45:38 Got connection from client 192.168.1.3
04/01/03 06:45:38 Protocol version 3.3
04/01/03 06:46:01 Client 192.168.1.3 gone
04/01/03 06:46:01 Statistics:
04/01/03 06:46:01   key events received 0, pointer events 4
04/01/03 06:46:01   framebuffer updates 0, rectangles 0, bytes 0


==

the xstartup file is:

---
#!/bin/sh
#unset SESSION MANAGER

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

unset SESSION MANAGER

gnome-session &
#bed twm &
---

the bottom line.. i'm still having the same issues that i've been dealing
with
for the past couple of days... the weird thing is that this was initially
working,
or at least i thought it was...

regards...

-bruce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 8:09 AM
To: Bruce Douglas
Subject: RE: vnc .. black vnc client screen


You need to read the linux RPM documentation. Try entering the command man
RPM in a terminal window. Basically the RPM command to remove a package is
rpm -e  packagename.

Basically you need to set up an a display on your linux machine so the
viewer can connect. If you accept the vnc default  the manager will be
something other than KDE. Just envision that you are connecting to a
different console on your linux machine and you must set it up with a
window manager and then an x display.

You control which console you connect to with the :1, :2, etc after the ip
address entry in the viewer.

If your are going from windows to windows or from linux to windows you are
stuck with display :0 so you and the local user see the same thing.

cheers

 ps: I am not at work but I am using VNC from my SuSE 8.1  linux machine
at home to talk to my Win2KK machine at work running Domino/Lotus R6 to
send this

.jack bunce
 Dorsey & Balaban LLP
 voice (860)346-5244
 fax (860)347-9706
 [EMAIL PROTECTED]



"Bruce Douglas" &l

RE: vnc .. black vnc client screen

[Bruce Douglas]

To all...

I'm ready to bribe for help!!! either that or go pay  for windows or
set up my boxes for target practice... to who ever is able to help... maybe
a book from amazon!!!

very rarely am i this frustrated over setting something up...

thanks!!



-Original Message-
From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 3:38 AM
To: '[EMAIL PROTECTED]'
Subject: RE: vnc .. black vnc client screen




-Original Message-----
From: Bruce Douglas [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 3:33 AM
To: 'Bruce Douglas'
Subject: RE: vnc .. black vnc client screen


hi...

ok.. now this is simply getting more confusing

i've decided to go back and start fom the beginning...

how does one completely remove/uninstall the vnc package. (is there an
uninstall rpm function within linux??)

what are the correct steps for building/installing a vnc server for a redhat
(8.0) linux platform???

i've seen plenty of msgs that point to a "/etc/sysconfig/vncservers" file. I
don't have this file on any of the boxes where i've selected vnc from the
linux/redhat distro when i was installing linux. in fact, i can't seem to
find vnc on any of the boxes where i've tried to install vnc as part of the
linux install process. (i've only had it initially work when i did the vnc
install by hand...)

so, in essence, i'm trying to find some form of docs/pointers to a sequence
of steps for installing the VNC server on a linux box in a repeatable
fashion

the docs that i found on the realvnc site weren't that helpful.

by the way, where does the vncservers file come from, and what should be in
it. is there any doc/set of docs that describes the various setup files
required and what they should include.

Thanks

Bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 10:11 PM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


hi...

my lserver2:2.log file follows:

03/01/03 08:57:12 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
03/01/03 08:57:12 Copyright (C) 2002 RealVNC Ltd.
03/01/03 08:57:12 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
03/01/03 08:57:12 All Rights Reserved.
03/01/03 08:57:12 See http://www.realvnc.com for information on VNC
03/01/03 08:57:12 Desktop name 'X' (lserver2:1)
03/01/03 08:57:12 Protocol version supported 3.3
03/01/03 08:57:12 Listening for VNC connections on TCP port 5901
03/01/03 08:57:12 Listening for HTTP connections on TCP port 5801
03/01/03 08:57:12   URL http://lserver2:5801
SESSION_MANAGER=local/lserver2:/tmp/.ICE-unix/904
Loaded background '0x8097490
AUDIT: Fri Jan  3 08:57:19 2003: 896 Xvnc: client 4 rejected from local host
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Xlib:  extension "RENDER" missing on display ":1.0".
Unable to open desktop file
applications:///Office/redhat-word-processor.desktop
 for panel launcher: Error reading file
'applications:///Office/redhat-word-proc
essor.desktop': File not found
Unable to open desktop file
applications:///Office/redhat-presentations.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-presentati
ons.desktop': File not found
--More--(84%)


my xstartup is below...

[root@lserver2 root]# more .vnc/xstartup
#!/bin/sh

unset SESSION MANAGER

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &
gnome-session &


I still cnnot figure out why i'm getting a blck screen when i try to connect
via a Windows vncviewer. I believe whatever I'm experiencing is also causing
my Windows box to consume all CPU cycles. As I stated earlier... the http
java client performs as I expect.

thanks

bruce
[EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:47 PM
To: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


ps...

my xstartup file (.vnc/xstartup) is

/
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#bed twm &

gnome-session &
/

-bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bruce Douglas
Sent: Friday, January 03, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: vnc .. black vnc client screen


Hi...

A simple question (I hope!!). I can run the vnc browser (java) and I see the
unix bo

RE: vnc .. black vnc client screen

[Bruce Douglas]

Hey!!!

To all who've seen/responded to my posts regarding the issue, I thank you.
It appears that the problem of a blank/black screen can be caused by having
too many applications running on the client machine.

I'm not sure as to what the magic number of applications is, nor am I sure
as to what might be the actual cause (ie, memory shortage, lack of sockets,
etc...) I simply know that under certain circumstances, if you have too many
applicatins running on your client machine, you will experience a
blank/black screen when connecting to the VNC Server using a VNC client.

I will try to write up what I've seen/experienced and get it to the VNC
team.

In the mean time, if you think you've got everything setup correctly, start
closing applications!!!

I've tried to do a quick search and have not come across anything that
indicates this to be a known problem.


Regards,

Bruce



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bill Cassady
Sent: Saturday, January 04, 2003 4:56 PM
To: Bruce Douglas
Cc: [EMAIL PROTECTED]
Subject: RE: vnc .. black vnc client screen


> Xlib:  extension "RENDER" missing on display ":2.0".
> Unable to open desktop file applications:///Internet/redhat-email.desktop
> for pa
> nel launcher: Error reading file
> 'applications:///Internet/redhat-email.desktop'
> : File not found
> Unable to open desktop file
> applications:///Office/redhat-word-processor.desktop
>  for panel launcher: Error reading file
> 'applications:///Office/redhat-word-proc
> essor.desktop': File not found
> Unable to open desktop file
> applications:///Office/redhat-presentations.desktop
> for panel launcher: Error reading file
> 'applications:///Office/redhat-presentati
> ons.desktop': File not found
> Unable to open desktop file
> applications:///Office/redhat-spreadsheet.desktop fo
> r panel launcher: Error reading file
> 'applications:///Office/redhat-spreadsheet.
> desktop': File not found
> Xlib:  extension "RENDER" missing on display ":2.0".


Bruce-

It looks to me that your install files are not where X expects to find
them.

I would suggest a couple of things:

1) Check your XF86Config file, (in my system in the /etc directory),
and see where it instructs you to put the fonts and the rgb files;
then make sure that the vncserver program puts them there.
After making any needed changes to vncserver file then rerun the
install program.

(modifying the xstartup file will not suffice)

2) To make things easy on yourself, before getting into the complexity
of gnome, specify a lean-and-mean window manager; if you don't like
twm I would recommend icewm: it's simple, fast, beautiful and
functional. (That step IS in the xstartup file, no?)

I believe that if you reduce the complexity of your configuration and
check each element step-by-step you may have better success.

And -- Oh, yes...check the .X.err file in yr home directory and see
if X itself is reporting errors.

I hope this message will be helpful to you...

-Bill Cassady
___
On Sat, 4 Jan 2003, Bruce Douglas wrote:

> Date: Sat, 4 Jan 2003 10:46:21 -0800
> From: Bruce Douglas <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: vnc .. black vnc client screen
>
> update...
>
> went back to the beginning...
>
> for server:
> 1) loaded redhat 8.0 linux onto a clean box
> 2) copied latest version of VNC server from realvnc site (rpm for redhat
> 7.3)
>   (didn't know how to build the tar version, but this shouldn't be an
issue)
> 3) modified xstartup file for gnome
> 4) rebooted linux box
>
> i'm not going through any firewalls.. the client box is a windows 2000
box.
> the server is
> a linux redhat 8.0 box.
>
> for client:
> 1) verified via the java browser... http://foo.com:5801 (works)
> 2) used the vncviewer client
>   the client starts a window. the window is blank/black. gnome does not
seem
> to start
>
>   the log file results are:
>
> ===
> [root@lserver1 root]# more .vnc/lserver1:2.log
> 04/01/03 06:45:01 Xvnc version 3.3.6 - built Dec  2 2002 10:54:00
> 04/01/03 06:45:01 Copyright (C) 2002 RealVNC Ltd.
> 04/01/03 06:45:01 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
> 04/01/03 06:45:01 All Rights Reserved.
> 04/01/03 06:45:01 See http://www.realvnc.com for information on VNC
> 04/01/03 06:45:01 Desktop name 'X' (lserver1:2)
> 04/01/03 06:45:01 Protocol version supported 3.3
> 04/01/03 06:45:01 Listening for VNC connections on TCP port 5902
> 04/01/03 06:45:01 Listening for HTTP connections on TCP port 5802
> 04/01/03 06:45:01   URL http://lserv

Linksys Routers..Port Forwarding...Putty.. VNC!!

[Bruce Douglas]

Evening... (or morning...)

I can no longer tell!! Once again I'm faced with the issue of tunneling
through my router to get to my Vncserver box. (At one point I thought this
was working. I rebuilt the Linux box, but this wouldn't/shouldn't have
affected the router.)

The Setup:

++
| External World |
++
 ^
 |(12.222.33.11)
 v
+-+
| Firewall/Router | (198.222.33.1)
|(Linksys)|<--+
+-+   |
| (Internal Network)
|
v
+--+
|  |
|  |
v  v
   +--+   +---+
   |  |   |   |
   |  Linux Box   | (192.222.33.4)| Windows 2K Box|
(192.222.33.5)
   | (VNCServer)  |   | (VNC Client)  |
   |  |   |  (PuTTY)  |
   +--+   |   |
  +---+



In keeping things simple, I decided to make sure I could use a Putty client
to get to the Linux box. In the above scenario, I'm able to get to the Linux
box from the Windows box with no problem. Using PuTTY, and staying within
the Firewall, I'm able to hit the Linux box and log in ok. (Putty's default
settings are used.)

When I attempt to use the PuTTY client from the Windows Box, and hit the
Linux box by going through the router, I have an issue. Within the Putty, I
use the external address of the Router. I have the port forwarding set so
that port 22 is forwarded to port 22 of the Linux Box. I would have expected
this to work! However, PuTTY times out. At this point, I'm still using the
default settings within Putty.

The default settings should be sufficient to allow this to work as I'm not
trying to perform anything unusual, especially given the fact that it works
if I hit the Linux box while inside the firewall!


My question: What might be preventing this from working?

The filter settings are:

  SPI:  Enable x Disable
  Block WAN Request:Enable x Disable
  Multicast Pass Through: x Enable   Disable
  IPSec Pass Through: x Enable   Disable
  PPTP Pass Through:  x Enable   Disable
  Remote Management:Enable x Disable
  Remote Upgrade:   Enable x Disable
  MTU:x Enable   Disable

My ultimate goal is to once and for all, get the router/VNC/PuTTY all
working to provide SSH access to the VNCServer on the Linux box from outside
the Firewall.

Thanks...

-Bruce

(PS. I've spent a great deal of time trying to track down information
relating to this issue on the 'net. I also looked through some of the past
VNC archives. I thought I had seen information relating to what I'm
experiencing, but I can't seem to find it now)
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: tight encoding in realvnc?

[Bruce Douglas]

hey...

couple of quick questions... as i was going through past msgs.. and the VNC
docs... couldn't find a suitable answer...

a vnc client app doesn't log the user into the machine. you apparently have
to have a copy of the vncserver running on the server machine... is it
possible to have multiple users log onto a machine, each with their own
login/user environment. if so, how is it done? pointers would be
appreciated.

here's why i ask. i currently have a vncserver running on my box... i set it
up running through putty. however, if another user were to also point their
vnc client to my box, and use the same display id... wouldn't they also see
what i'm displaying...??? unless i shut the vncserver down/logged off the
box when i was done

basically.. i'm trying to determine the best/correct way to fire up the
vncserver such that each user has their on copy/own display environment...

is it perhaps best to require each person to 1st establish a secure
connection via ssh... and then port forward the vnc client through the ssh
connection if this is the case, how do i stop someone from pointing a
vncclient and connecting to a vaild vnc display on the server machine. i
can't simply block the vnc port coming into the vnc server box.. or can
i?? i'm using linux RH 8.0 as the vnc server

if you can simply block access to the given port, how would you do it???

thanks...

-bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

vnc security... port access... users...

[Bruce Douglas]

sorry for the wrong subject on the last one...


hey...

couple of quick questions... as i was going through past msgs.. and the VNC
docs... couldn't find a suitable answer...

a vnc client app doesn't log the user into the machine. you apparently have
to have a copy of the vncserver running on the server machine... is it
possible to have multiple users log onto a machine, each with their own
login/user environment. if so, how is it done? pointers would be
appreciated.

here's why i ask. i currently have a vncserver running on my box... i set it
up running through putty. however, if another user were to also point their
vnc client to my box, and use the same display id... wouldn't they also see
what i'm displaying...??? unless i shut the vncserver down/logged off the
box when i was done

basically.. i'm trying to determine the best/correct way to fire up the
vncserver such that each user has their on copy/own display environment...

is it perhaps best to require each person to 1st establish a secure
connection via ssh... and then port forward the vnc client through the ssh
connection if this is the case, how do i stop someone from pointing a
vncclient and connecting to a vaild vnc display on the server machine. i
can't simply block the vnc port coming into the vnc server box.. or can
i?? i'm using linux RH 8.0 as the vnc server

if you can simply block access to the given port, how would you do it???

thanks...

-bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Securing VNC by using a firewall/router and SSH

[Bruce Douglas]

hi...

in researching how to properly secure the VNC Server, it appears that the
basic question comes down to how one can configure a SSH client application
appropriately. (If I open up the firewall.. I can easily connect to the VNC
Server.)

In the following diagram, the client is outside the firewall, the VNC
Service is behind the firewall. The firewall is permits only port 22 which
is forwarded to the VNC Server. The VNC Server is running SSHD as well.
(External IPs are for discussion...)

+-+
| External Client |
  |   VNC Client| (12.123.45.xx)
  |  PuTTY  |
+-+
 ^
 |
 v
+-+
| Firewall/Router | (23.222.45.yy)
|(Linksys)|<--+
+-+ (192.168.1.1) |
| (Internal Network)
|
v
+--+
|  |
|  |
v  v
   +--+   +---+
   |  |   |   |
   |  Linux Box   | (192.168.1.55)| Windows 2K
Box|(192.222.33.5)
   | (VNCServer)  |   | (VNC Client)  |
   |(SSHD)|   |  (PuTTY)  |
   +--+   |   |
  +---+

So here's the question(s):
1) Can the above situation work? IE, can the client PuTTY application be
setup to allow a VNC "tunnel" to be created, allowing communication to occur
between the VNC Client/Server over port 22?

I believe it should be possible. However, when I've tried to set up the
PuTTY client application, it appears that I have something configured
incorrectly. (I have the latest version of the Windows PuTTY)

Under the Session Options
Host Name/IP : 23.222.45.yy (The router/firewall IP address)
Port:   22 (The SSH port, only port open on the firewall)
Protocol: SSH

Under SSH Options:
Tunnels:
Forwarded Source Port: 5901
Forwarded Destination: 23.222.45.yy:5901

I've also tried this setting as well...
Tunnels:
Forwarded Source Port: 5901
Forwarded Destination: 12.123.45.xx:5901


Neither setup for the Tunnels appears to work. Using either setup, I can get
into the Linux box and log on, establishing the SSH tunnel. However, when I
fire up the VNC Client, I am unable to establish a connection with the VNC
Server on the linux Box. The VNC Server is working as I am able to see it on
the Linux Box.

I have tried to establish connections using:
23.222.45.yy:1
23.222.45.yy:5901

12.123.45.xx:1
12.123.45.xx:5901

The thought being that one has to establish a connection with either the
port on the router or the port on the local client machine which would then
be forwarded to the VNC Server.

This setup doesn't seem to work.

So... The end question is how should the PuTTY/VNC be configured to allow
one to go through the firewall and establish a VNC connection using the SSH
tunnel

thanks in advance for any pointers...

-bruce

ps... I recall seeing some directions to this at one time from a google
search.. however, a couple of the sites with the information now appear to
be down
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Securing VNC by using a firewall/router and SSH

[Bruce Douglas]

William...

thanks for the input... your suggestions worked... which implies that the
putty application more or less needs to know the internal ip/port prior to
running... not sure i want to expose this to my end user.. but for now..
should be ok

i may consider creating my own version of putty for my users, and hardcoding
the internal ip/port within the app. wouldn't be too difficult...

but for now.. thanks for the advice...

-bruce


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of William Hooper
Sent: Sunday, January 19, 2003 1:54 PM
To: 'VNC'
Subject: Re: Securing VNC by using a firewall/router and SSH


- Original Message -----
From: "Bruce Douglas" <[EMAIL PROTECTED]>


[snip]
> I believe it should be possible. However, when I've tried to set up the
> PuTTY client application, it appears that I have something configured
> incorrectly. (I have the latest version of the Windows PuTTY)
>
> Under the Session Options
> Host Name/IP : 23.222.45.yy (The router/firewall IP address)
> Port: 22 (The SSH port, only port open on the firewall)
> Protocol: SSH
>
> Under SSH Options:
> Tunnels:
> Forwarded Source Port: 5901
> Forwarded Destination: 23.222.45.yy:5901
[snip]

Try using the internal IPs (in your example 192.168.1.55).  Trying to use
your external IP isn't working because the SSH server is trying to connect
to your firewall.

[snip]
> I have tried to establish connections using:
> 23.222.45.yy:1
> 23.222.45.yy:5901
>
> 12.123.45.xx:1
> 12.123.45.xx:5901
[snip]

In order to use the SSH tunnel you would have the VNCviewer connect to
localhost:5901.

--
William Hooper

Whatever you delete today, you desperately need tomorrow
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

running a web browser over ssh using putty...

[Bruce Douglas]

hey!!

thanks again for all the help you guys gave over the last couple of days on
my vnc/router/ssh issue...

a quick question.. it occured to me that since SSH establishes a secure
"tunnel" between the client and the server. If I run a web server and make
the appropriate port changes to puTTY, I should be able to remotely access
my internal web server, without having to open up any port other than 22 on
my router.

I did a quick test and I seem to keep getting my Router's (Linksys)
config/mgmt page. Has anyone else done this, or have you seen any pointers
that might describe how to set it up.. assuming I'm missing something
here

thanks

-bruce

ps. If you want to get a feel for how my network is setup, check out the
earlier thread...
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

VNC /CVS

[Bruce Douglas]

hey...

a quick question. has anyone tried to set up a CVS Server and a
VNCServer on the same linux box. I have Redhat 8.0. In looking at some
information, I'm wondering if this kind of situation might not pose some
sort of conflict within SSH as it tries to work with both applications...

thanks

bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

small bugs in vncviewer 3.3.3r1

[Bruce Lilly]

Hi,

vncviewer -h (as distributed with SuSE 8.0 Intel) gives:

VNC viewer version 3.3.3r1 with SSH tunneling support

usage: vncviewer [] [:]
 vncviewer [] -listen []
 vncviewer [] -tunnel :

 are standard Xt options, or:
-shared
-viewonly
-fullscreen
-passwd 
-encodings  (e.g. "raw copyrect")
-bgr233
-owncmap
-truecolour
-depth 


The first usage line is incorrect, and should be:

usage: vncviewer [] []:

i.e. the colon before the display number is NOT optional.
The same may apply to the -listen version.
And the -h flag should probably be self-documenting.

Best regards,
Bruce Lilly
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

shared root window session on Linux

[Bruce Lilly]

I've managed to get a shared VNC session on Linux such that
the session started at the root X window (a.k.a. console)
is sharable via VNC.  It is fairly easy to do (once one
figures out some of the undocumented features and options
of vncserver).  Here's the procedure for SuSE Linux 8.0
(Intel), using kdm as the display manager:

1. (obviously) the vnc package, X, and a suitable display
manager need to be installed. xfstt is also helpful.
2. configure xfstt to run in run levels 3 and 5. The
YaST2 system -> run level editor can be used.
3. edit the vncserver (in /usr/X11/bin) script to
configure a suitable default color depth, default
xstartup file contents, and font paths.
I use a depth of 16 and the following for the font path:
$cmd .= " -fp /usr/lib/X11/fonts/misc/";
$cmd .= ",/usr/lib/X11/fonts/misc:unscaled";
$cmd .= ",/usr/lib/X11/fonts/75dpi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/100dpi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/URW";
$cmd .= ",/usr/lib/X11/fonts/Speedo";
$cmd .= ",/usr/lib/X11/fonts/cyrillic:unscaled";
$cmd .= ",/usr/lib/X11/fonts/latin2/misc:unscaled";
$cmd .= ",/usr/lib/X11/fonts/latin7/75dpi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/japanese:unscaled";
$cmd .= ",/usr/lib/X11/fonts/hellas/misc:unscaled";
$cmd .= ",/usr/lib/X11/fonts/hellas/75dpi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/hellas/100dpi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/hellas/Type1";
$cmd .= ",/usr/lib/X11/fonts/misc/sgi:unscaled";
$cmd .= ",/usr/lib/X11/fonts/75dpi";
$cmd .= ",tcp/localhost:7101";
YMMV (the last is for use with xfstt). I use the
following for the default xstartup (edit $HOME/.vnc/xstartup
also if vnc has already been used):
$defaultXStartup
 = ("#!/bin/sh\n\n".
"xrdb \$HOME/.Xresources\n".
"xsetroot -solid grey\n".
"#xterm -geometry 80x24+10+10 -ls -title \"\$VNCDESKTOP Desktop\" &\n".
"#twm &\n".
"kde &\n");
4. put a shell script named vnc in /usr/X11/bin,
containing the following three lines (edit the
geometry and dpi arguments to suit local conditions):
#!/bin/sh
vncserver -geometry 1024x768 -once -alwaysshared -dpi 94
vncview
5. put a shell script named vncview in /usr/X11/bin,
containing the following 3 lines:
#!/bin/sh
display=$(ls -t $HOME/.vnc/*:*.* | head -1 | cut -d: -f2 | cut -d. -f1 )
vncviewer -fullscreen -passwd $HOME/.vnc/passwd :$display
6. Add three entries to the login session manager via
the KDE Control Center, System -> Login Manager
"Sessions" tab. The entries should be "vnc",
"vncview", and "vncviewer".
7. Add "vnc" to the list of window managers in
/usr/X11/bin/wmlist (in case startx is used).

To use:
At the login session window, select "vnc" from the
session type drop-down menu.  The vnc server will be
started (usu. on :1) and a full-screen vnc viewer
window will be opened connecting to the server using
the root window for the viewer.  Remote connections
specify host:1 (unless for some reason the server has
started on a different X display).  If the vnc viewer
in the root window is prematurely closed or crashes,
but the Xvnc server is still running, one can use the
"vncview" session selection in the login window to
reconnect to the vnc server without starting an
additional KDE (or other window manager) session.

Caveats:
It is presumed that the most recent $HOME/.vnc/*:*.*
file corresponds to the session established at login.
If additional sessions are established for the same
user, and the "vncview" session is used to try to
reconnect after closing the root vnc viewer, that
might not be the case. Use the "vncviewer"
session as described above to manually connect to the
correct vnc server (then one can use F8 to get a full
screen viewer). Obviously, errors in editing critical
files can cause problems; use the instructions above
at your own risk.

Pleasant surprises:
The vnc viewer in the root window can be used with
keyboard shortcuts (e.g. ALT + TAB to switch program
windows in the KDE session).  Of course that won't work
from a MS Windows version of the VNC viewer.

Q&A:
Q: Why bother? On UNIX, you don't need to share the
console session -- you can start an additional user
session for each viewer [blah, blah, blah...]
A: Additional separate window manager sessions (i.e.
other than the root window desktop session) don't
permit doing what the VNC description states:
"[...] you can leave your desk, go to another machine,
whether next door or several hundred miles away, reconnect
to your desktop from there and finish the sentence you were
typing. Even the cursor will be in the same place".
That description DOES apply with a shared root window
session.
Q: How do I do this for Red Hat [or other] Linux?
A: I don't know. Experiment.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: shared root window session on Linux

[Bruce Lilly]

> Date: Mon, 10 Jun 2002 10:19:04 +0200
> From: "Beerse, Corni" <[EMAIL PROTECTED]>

> xfstt??? What's that (I have not found time to get a SuSE 8 copy.)

X font server for TrueType fonts (which VNC apparently can't
handle in the font path).

> The last line adds the local font server. Best to choose between the
> fontserver and a fully specified fontpath. My idea, only specify the
> fontserver here (-fp tcp/localhost:7101)

See above.  I'm not sure if xfstt also serves bitmap and Type1 fonts
(if so, then that might be OK).  There would probably be a tradeoff
between speed and memory use.

> Other users: read the console fontpath from the local xserver with `xset -q`
> and specify that here. I found "-fp unix/:7100"

xset -q will list directories that VNC can't handle (e.g truetype).
Port 7100 is typically xfs (X font server for bitmap fonts).

I grabbed the lines from /etc/X11/XF86Config (this is version 4.2)
and put them in vncserver, then ran it. Then examined the log file
to see which ones it complained about and removed them from vncserver,
also added the one for xfstt.

If you use xset -q from within a VNC session, don't forget to also
specify -display host:0 !


> Some alternate routes to accuire similar behavoure:
> For XF86 version 4 users: http://xf4vnc.sourceforge.net/. This includes the
> acceleration of the standard X11 server. Problem here (for the momemt): Only
> linux, Only intel, not all display drivers are supported at the moment.

XF86 is difficult enough to get set up correctly, and vendor updates
might override a driver substitution.  Also, xf4vnc either uses no
password or a specific user's VNC password, whereas my method will
use the VNC password for whatever user is logged in at the console.

Here, X objects to the syntax of some of the lines given at the URI:

Option "rfbport" 5900
Option "httpport"5800

I get error messages like:

Parse error on line 164 of section Device in file /etc/X11/XF86Config
"5800" is not a valid keyword in this section.

Apparently, the lines should be

Option "rfbport" "5900"
Option "httpport""5800"

And some of the references to input and screen sections may need to
be revised to match the relevant entries in XF86Config.

-
Additional caveats not mentioned in the original:

Some care is required when running X programs, as they will be
running with Xvnc.  For example, running SuSE's SaX2 (X configuration
utility) would probably be a very bad idea as it would overwrite
XF86Config.

While this may be unrelated to the VNC changes, here, the "logout"
item in the KDE (v3) menu unfortunately doesn't end
the session.  However, the button on the lock/logout applet does
work. An alternative way to end a session is to send a SIGTERM
signal to the Xvnc process.

Other resources:
An article by Jeremy D. Impson appeared in the January 2002 issue
of Linux Journal.  It takes a somewhat different approach. While
the article states "The scheme we discuss can work on any Linux
distribution", SuSE is different enough from Red Hat 7.1 that the
method outlined in the article definitely does not work for SuSE
(primarily because of the way SuSE provides a session selection).
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: vnc loses kbd input in full screen

[Bruce Lilly]

>>> From:
>>>
>>> Michal Kochanowicz <[EMAIL PROTECTED]>
>>> Date:
>>>
>>> Wed, 12 Jun 2002 10:29:37 +0200

>>>Hi
>>>
>>>I'm using linux vncviewer to connect to windows 2000. After switching to
>>>full screen vnc loses keyboard input. All keys are received by terminal
>>>from which vncviewer was started (fo example pressing ctrl-c terminates
>>>viewer). I'm not sure if it's vncviewer's problem, beacuse if I start
>>>vncviewer from plain xterm (even without window manager) it works OK in
>>>full screen. The problem appears when vncviewer is running under KDE.
>>>
>>>Can you suggest any solution? Or maybe I should report it to the KDE
>>>team?


Are you using kdm as the display manager?  Do you have the same problem
if you start a vncserver on the linux box and connect vncviewer to it
(on the same machine)?


>>> From:
>>>
>>> "Hartmut M. Bromkamp" <[EMAIL PROTECTED]>
>>> Date:
>>>
>>> Wed, 12 Jun 2002 11:32:04 +0200 (CEST)
>>> To:
>>>
>>> [EMAIL PROTECTED]

>>>I reply to your msg because I have similar problems with the Linux TightVNC viewer 
>against Windows 2000 servers. I have two Win2000 machines, called A (running Windows 
>2000 Professional) and B (running Windows 2000 Server) for now:
[...]
>>>bromkamp@machine # vncviewer B
>>>VNC server supports protocol version 3.3 (viewer 3.3)
>>>Password: 
>>>VNC authentication succeeded
>>>Desktop name "B"
>>>Connected to VNC server, using protocol version 3.3
>>>VNC server default format:
>>>  16 bits per pixel.
>>>  Least significant byte first in each pixel.
>>>  True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
>>>Using default colormap which is TrueColor.  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
>>>Using shared memory PutImage
>>>vncviewer: read: Connection reset by peer

^
[...]


>>>bromkamp@machine # vncviewer B
>>>VNC server supports protocol version 3.3 (viewer 3.3)
>>>Password: 
>>>VNC authentication succeeded
>>>vncviewer: VNC server closed connection

^^

These lines clearly show that it is the server running on the MS Windows
machines which is crashing.  First make sure that you have the latest
display driver for your hardware and that you have the latest service
pack installed for the "operating" system (W2k seems to be stalled at
SP2, which is now more than a year old).  If that doesn't help, report
details here about the display card and driver; maybe somebody had
similar problems with the same setup.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: vnc loses kbd input in full screen

[Bruce Lilly]

> From: Michal Kochanowicz <[EMAIL PROTECTED]>
> Date: Wed, 12 Jun 2002 21:15:27 +0200

>>Are you using kdm as the display manager?  Do you have the same problem
>>
> Yes.
> 
> 
>>if you start a vncserver on the linux box and connect vncviewer to it
>>(on the same machine)?
>>
> Yes.


Next thing to check is compatibility of your linux and vnc.  Which
linux distribution and version are you running?  And where did you
get the vnc binaries (with distribution/downloaded as binaries/compiled
from source/other)?
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: vnc loses kbd input in full screen

[Bruce Lilly]

> From: Michal Kochanowicz <[EMAIL PROTECTED]>
> Date: Thu, 13 Jun 2002 18:34:50 +0200

>>Next thing to check is compatibility of your linux and vnc.  Which
>>linux distribution and version are you running?  And where did you
>>
> PLD (current).
> 
> 
>>get the vnc binaries (with distribution/downloaded as binaries/compiled
>>
>>From the distro.
> 
> 
>>from source/other)?
>>
> If you think It can help I can compile it myself. Should I try?


I'm not familiar with PLD; if the vendor offers support,
you might try contacting them to find out if they have
seen the problem.

It couldn't hurt to try compiling from source. If that
results in working binaries, your problem is solved. If
compiling with shared library objects doesn't work, try
static linking.
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

WinCE.Net VNC Server

[Bruce Heck]

I have seen several threads regarding VNC Viewer for WinCE, but I am in need 
of a VNC server.  I'm using some embedded computer boards that run WinCE.Net 
v4.2 with an Intel Xscale processor (ARM equivalent).  Does anyone know of a 
version currently available or what would be required to port the current 
WinVNC to CE?

--bruce

_
On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Multiple Workstations

[Neild,Bruce]

Hello Everyone:
I have been researching a method to run a GUI application on multiple
workstations in the same network.  The application can be launched from
the command line directly or via a batch file on a single workstation.
It needs the desktop to interact with other GUI components.
I would like to use a scheduling program on a master workstation or
server (W2K or XP) to launch this application on other multiple
workstations not in use by any other user.
I looked into psexec and it would launch the application, however
without the GUI desktop it could not run correctly.  From everything I
have read it looks like some sort of remote utility such as VNC would be
needed to accomplish my goal.
Can VNC installed as a server on multiple W2K or XP workstations be
started from one master workstation?  I do not have a problem with
serializing the launch on the remote workstations.
Thanks for the help.

=
=
This communication, together with any attachments hereto or links contained
herein, is intended for the use of the intended recipient(s) only and may
contain information that is confidential or legally protected. If you are not
the intended recipient, you are hereby notified that any review, disclosure,
copying, dissemination, distribution or use of this communication is STRICTLY
PROHIBITED.  If you have received this communication in error, please notify
the sender immediately by return e-mail message and delete all copies of the
original communication, along with any attachments hereto or links herein,
from your system.
=
=
The Travelers E-mail System  made this annotation on 01/14/2004
09:54:31 AM.
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Multiple Workstations

[Neild,Bruce]

I should clarify a few items.

1) The GUI on the client workstation needs to be available only to that
workstation.

2) Once I have launched the application that uses the GUI I could
disconnect as long as the application keeps running.  There is nothing I
want or need to see on the desktop.  

3) This process needs to be repeatable.  If the application ends and
closes I need to be able to reset the workstation state to begin the
process over with a clean start.  

4) The application is a purchased product.  I know it can be launched
from the command line when you are logged on at a workstation.  I need
to do this from a remote machine and with multiple instances.

Thanks


-Original Message-
From: Tim Wood [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 14, 2004 6:00 PM
To: Neild,Bruce
Cc: [EMAIL PROTECTED]
Subject: Re: Multiple Workstations

At 06:53 AM 01/14/04, you wrote:
>Hello Everyone:
>I have been researching a method to run a GUI application on multiple
>workstations in the same network.  The application can be launched from
>the command line directly or via a batch file on a single workstation.
>It needs the desktop to interact with other GUI components.
>I would like to use a scheduling program on a master workstation or
>server (W2K or XP) to launch this application on other multiple
>workstations not in use by any other user.

If you write your application in X (probably Unix/Linux hosted, unless
there's an X library for Windows), it'll be easy: have your "slave"
workstations run the application instances, with their $DISPLAYs pointed
at the master server's Xvnc instance.  Then connect to that Xvnc
instance with vncviewer from anywhere and see all the app. instances.  I
think there's an obstacle to aggregating all the displays if the
application is Win32, even with VNC server or Term. Server on Windows
slave boxes, because there's no facility to aggregate all those virtual
desktops from the slave machines onto one display (physical or virtual).
(A VVNC might do it. :)  However if you don't mind having one vncviewer
process for each slave desktop, then yes, a VNC desktop running as a
service (for automatic startup) on each slave box makes sense.

YMMV, FWIW, HTH, etc.
TW





==
This communication, together with any attachments hereto or links contained herein, is 
intended for the use of the intended recipient(s) only and may contain information 
that is confidential or legally protected. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, dissemination, distribution 
or use of this communication is STRICTLY PROHIBITED.  If you have received this 
communication in error, please notify the sender immediately by return e-mail message 
and delete all copies of the original communication, along with any attachments hereto 
or links herein, from your system.
==
The Travelers E-mail System  made this annotation on 01/15/2004 06:49:07 AM.
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

VNC xstartup examples?

[Ordway, Bruce]

Hi,

I've only been experimenting with VNC for a few days now.
So far I think it's wonderful.

Now I'm wondering if I can get a little more pizzazz in my desktop.
Has anybody got a window manger like Gnome or KDE running with VNC?

It looks like it's just a matter of editing $HOME/.vnc/xstartup
But, I'm still a novice so I'm not too adventurous yet.
Is this right & if so, do any of you have an example you can share?

Thanks,
Bruce Ordway
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Multiple VNC connections from the internet

[Ordway, Bruce]

Hi,

I've been trying VNC out for a few days now & I really like it.
This is great for running multiple PC's on my LAN.
I'm wondering if I can access them from the web.
Here's my situation.

I have a Cisco 675 DSL modem, it has a 5 user public IP's and a
non-routable internal address. ( A couple of the public ip's are already
used for mail and web servers)
The Cisco is hooked up to a FreeBSD firewall/NAT box.
Then I have a few PC's using 10.0.0.xxx addresses on my LAN that I would
like to reach via VNC.

Do any of you think it's possible to allow connections to MULTIPLE VNC
servers that are on my LAN?
This would be a pretty fancy trick, I can't quite imagine what setup
would be necessary.

Thanks,

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: MultiCasting VNC

[Bruce Anderson]

It already exists:

TeleTeaching @ University of Trier
platform-independent recording and transmission of arbitrary content



Papers:

*   Transparent TeleTeaching: by Peter Ziewer and Helmut Seidl,
 Contribution to ASCILITEJ2002



BA-
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

(no subject)

[Bruce Osborn]

Please Help!

Our VNC was working fine until we changed our IP address of our server
(redhat 6.1).
Now no matter what we do we get the grey screen.
We are using the Windows viewer to connect  to the Linux Box.

Bruce Osborn
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

FW: max clients exceeded

[Nepple, Bruce]

I looked back through a couple months mail and saw nothing on this issue:

How can I increase the number of X clients that I can run in a VNC session?

How many clients should I be able to start?

I think I get quite a few less than I used to get with Xmanager so it seems
that vncserver is limiting it somehow.

I am running on an ancient sunOS 5.8

Xvnc version 3.3.6 - built Nov 26 2002 15:55:02

VNC viewer version 3.3.6 - built Nov 26 2002 15:44:38
Copyright (C) 2002 RealVNC Ltd.
Copyright (C) 1994-2000 AT&T Laboratories Cambridge.

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: FW: max clients exceeded

[Nepple, Bruce]

The error message I am getting is:

Xlib: connection to "localhost:11.0" refused by server
Xlib: Maximum number of clients reached

How can I get to the bottom of what resource is limited?

Bruce


> -Original Message-
> From: Corni Beerse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 01, 2004 4:30 AM
> To: Nepple, Bruce
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: max clients exceeded
> 
> 
> Nepple, Bruce wrote:
> 
> > I looked back through a couple months mail and saw nothing 
> on this issue:
> > 
> > How can I increase the number of X clients that I can run 
> in a VNC session?
> 
> I think that is all related to 'other' resources:
> - max memory per process (Xvnc needs to handle it all
> - max sockets and such per process/user
> - max processes per user
> 
> well, actually it's not Xvnc that sets a limit, its the entire system.
> 
> > 
> > How many clients should I be able to start?
> 
> Roughly as much as on the console, except when shared 
> resources are in use, then 
> that might give a limit on the grand total over the sessions.
> 
> > 
> > I think I get quite a few less than I used to get with 
> Xmanager so it seems
> > that vncserver is limiting it somehow.
> 
> As far as I know, there are no limitations build into Xvnc.
> 
> On the other hand, if comparing with similar products, both 
> can have different 
> optimalisations and reach some limitations at an other number 
> of clients.
> 
> > 
> > I am running on an ancient sunOS 5.8
> > 
> > Xvnc version 3.3.6 - built Nov 26 2002 15:55:02
> > 
> 
> An other version can have an other limit, just als an other 
> product can have.
> 
> 
> CBee
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: FW: max clients exceeded

[Nepple, Bruce]

The error message I am getting is:

Xlib: connection to "localhost:11.0" refused by server
Xlib: Maximum number of clients reached

How can I get to the bottom of what resource is limited?

Bruce


> -Original Message-
> From: Corni Beerse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 01, 2004 4:30 AM
> To: Nepple, Bruce
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: max clients exceeded
> 
> 
> Nepple, Bruce wrote:
> 
> > I looked back through a couple months mail and saw nothing 
> on this issue:
> > 
> > How can I increase the number of X clients that I can run 
> in a VNC session?
> 
> I think that is all related to 'other' resources:
> - max memory per process (Xvnc needs to handle it all
> - max sockets and such per process/user
> - max processes per user
> 
> well, actually it's not Xvnc that sets a limit, its the entire system.
> 
> > 
> > How many clients should I be able to start?
> 
> Roughly as much as on the console, except when shared 
> resources are in use, then 
> that might give a limit on the grand total over the sessions.
> 
> > 
> > I think I get quite a few less than I used to get with 
> Xmanager so it seems
> > that vncserver is limiting it somehow.
> 
> As far as I know, there are no limitations build into Xvnc.
> 
> On the other hand, if comparing with similar products, both 
> can have different 
> optimalisations and reach some limitations at an other number 
> of clients.
> 
> > 
> > I am running on an ancient sunOS 5.8
> > 
> > Xvnc version 3.3.6 - built Nov 26 2002 15:55:02
> > 
> 
> An other version can have an other limit, just als an other 
> product can have.
> 
> 
> CBee
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Media players

[Ordway, Bruce]

Hi,

Just wondering if this is possible.
If I start a media player on a remote PC using VNC,
And I start and .avi with video and audio
Is there any way to get the audio and video on my local PC?

I know this is a stretch, but I figure maybe some clever person had
figured this out.

Thanks,
Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

VNC vs. TS

[Ordway, Bruce]

Hi,

I've seen a few older threads regarding VNC vs. Windows Terminal Server.
Since things change so fast I thought I'd ask what people think about
the two today.

Obviously there is a great price advantage with VNC.
Are there any cases where you would feel you must use Windows Terminal
Server instead of VNC?

Also, one of our software vendors is working on the next release of
their application. They are going to use .NET. Users will have a thin
client connected to "services" on a Win2K box. Details are sketchy at
this point but I'm already wondering what impact this might have on my
the ability to use VNC servers and VNC viewers. Knowing software vendors
as I do, I'm afraid that this might be locking me into Terminal Server
somewhere down the road.

Thanks,

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

VNC vs. TS part II

[Ordway, Bruce]

Please let me rephrase my original question.
I have about 15 remote users.
In fact remote may be a misnomer, they could be called disconnected
users right now.
The CRM application we use connects to a WinNT RAS server occasionally
and replicates.
We are upgrading our CRM application & it doesn't replicate anymore.
Instead, looks like a user connects using Windows Terminal server and
uses the application "live".

When I started adding up the cost of a Terminal Server and all of the
client licenses... made me sad.

I haven't done the math yet but I wonder if it wouldn't be cheaper (and
easier?) to set up 15 PC's in the back room. They could each run the
client CRM software and a VNC Server. PC's are pretty darn cheap these
days.

Would this be insane?

If not, then what if we go even further.
How about fewer PC's sliced up using VMWare?
Possible?
Cool or UnCool?

Thanks,

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

vnc through two machines

[Nepple, Bruce]

I looked around and didn't see an answer to this.  I know I could play around and 
*eventually*
get it right, but I'm sick of playing around this week.

Windows machine running vnc viewer tunnels through ssh to linux1 machine (over 
internet)

Now, how do I tunnel from linux1 machine to linux2 machine where vnc session is running

Can this all be done with the ssh connection to the first machine from windows, or do 
I have to
open another ssh link between linux1 and linux2 with some sort of forwarding

And, if it's being done with a single ssh, can putty do it?

windows (vnc viewer) ---> pub net > firewall --->linux1 >priv net > linux2 
(vnc server)

If vncserver runs on linux1, I know what to do.  It's the extra hop to linux2 that 
puzzles me.

Thanks for saving me from the adventure game of figuring this out.  I don't need it 
this week

Bruce
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: vnc through two machines

[Nepple, Bruce]

Replying to you directly was an accident.  Here is the posting for all to read

Thanks, I'll try it tonight when I get home.  Hopefully putty can do this.

Bruce


-Original Message-
From: Jerome R. Westrick [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 21, 2004 10:53 PM
To: Nepple, Bruce
Subject: RE: vnc through two machines


Bruce please reply to list,
so other people can learn from this...

Then I might not have to answer the same thing to them!

No Since you seam to be confortable with the linux syntax
where goes:  ssh -L 5902:linux2:5902 [EMAIL PROTECTED]
Means:

Connect to linux1, singon as user
Tunnel traffic from 5902 (on my machine)
to linux2:5902

Noe that linux2 is resolved on linux1, so it can be any
address linux understands (such as 192.168.x.y)

Note that only the mymachine:5902 <--> linux1 is encrypted,
the traffic linux1 <--> linux2:5902 is not encrypted, not compressed...

you can use this method to get to any machine inside local net 
which includes linux.

This is so usefull that the linux versions of vnc often have a -via (ssh-server)
shortcut...

vncviewer linux2:2 -via [EMAIL PROTECTED] will do exactly the same thing, and connect 
you
to vnc on Linux2 (works with tightvnc, but for some reason shortcut missing from real 
vnc)

Jerry



On Thu, 2004-07-22 at 03:49, Nepple, Bruce wrote: 
Are you saying that I need to start another ssh session on linux1  "ssh -L 
5902:linux2:5902"

So, I start putty to linux1 (giving me an ssh session from windows to linux1),
then, in the shell I started on linux1 I ssh to linux2 "ssh -L 5902:linux2:5902 
linux2", then start my vnc viewer on my windows
machine and it will see the vncserver on linux2.  Sounds easy enough. 

Do I need to open anything in the reverse direction?  I tried it here at work and it 
didn't work, but
my setup is suspect.

on linux2 I ssh to linux1, then back to linux2 "ssh linux2 -L 5902:linux2:5902".  

If I connect vnc to linux2:5902, it works (since that's where the server is), but
if I try linux1:5902 it fails to connect.







> -Original Message-
> From: Jerome R. Westrick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 21, 2004 4:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: vnc through two machines
> 
> 
> Tunnel through the Linux1 to Linux2...
> 
> 
> Tunnel  Local 5902:Linux2:5902
> 
> 
> On Thu, 2004-07-22 at 01:06, Nepple, Bruce wrote:
> > I looked around and didn't see an answer to this.  I know I 
> could play around and *eventually*
> > get it right, but I'm sick of playing around this week.
> > 
> > Windows machine running vnc viewer tunnels through ssh to 
> linux1 machine (over internet)
> > 
> > Now, how do I tunnel from linux1 machine to linux2 machine 
> where vnc session is running
> > 
> > Can this all be done with the ssh connection to the first 
> machine from windows, or do I have to
> > open another ssh link between linux1 and linux2 with some 
> sort of forwarding
> > 
> > And, if it's being done with a single ssh, can putty do it?
> > 
> > windows (vnc viewer) ---> pub net > firewall --->linux1 
> >priv net > linux2 (vnc server)
> > 
> > If vncserver runs on linux1, I know what to do.  It's the 
> extra hop to linux2 that puzzles me.
> > 
> > Thanks for saving me from the adventure game of figuring 
> this out.  I don't need it this week
> > 
> > Bruce
> > ___
> > VNC-List mailing list
> > [EMAIL PROTECTED]
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
> ___
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: 4.0 Client Crashes every few hours

[Nepple, Bruce]

I wish I could find it in the documentation.  Certainly can't find it on the
vncserver man page, or in any windows vnc viewer documentation, or a entry anywhere
in the vnc viewer options for a value or some checkbox to disable it.  Not in the FAQ
either.

Be nice if you gave us a hint as to WHAT documentation might contain this tasty tidbit.

Bruce



> -Original Message-
> From: James Weatherall [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 10, 2004 8:23 AM
> To: 'Joe Perrone'
> Cc: [EMAIL PROTECTED]
> Subject: RE: 4.0 Client Crashes every few hours
> 
> 
> Joe,
> 
> "The client dissappears after about 2 or 3 hours" suggests 
> that it's simply
> the idle timeout on the connections, causing them to be 
> dropped.  Please
> read the documentation for details on select a longer timeout 
> if required.
> 
> Wez @ RealVNC Ltd.
>  
> 
> > -Original Message-
> > From: Joe Perrone [mailto:[EMAIL PROTECTED] 
> > Sent: 10 August 2004 16:21
> > To: James Weatherall
> > Subject: RE: 4.0 Client Crashes every few hours
> > 
> > No, what I meant by checking the Catalyst I mean that I 
> > checked the exact ports on the Cisco Catalyst switch that all 
> > 3 pc's are connected to and none of them have any reset 
> > sockets or bad packets.  The client dissapears after about 2 
> > or 3 hours regularly.  The Host is running Win XP and the 
> > clients are W2k professional.
> > 
> > -Joe
> > 
> > -Original Message-
> > From: James Weatherall [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, August 10, 2004 11:17 AM
> > To: Joe Perrone
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: 4.0 Client Crashes every few hours
> > 
> > 
> > Joe,
> > 
> > Please provide more detail regarding VNC Viewer 
> > "dissappearing", such as
> > how long the viewer had been connected, etc.  Information on the
> > platforms in use may also be useful.
> > 
> > What do you mean by "the Catalyst ports"?
> > 
> > Please read the documentation regarding shared connections.
> > 
> > There doesn't appear to be anything crashing, from what you've
> > described, just a connection getting closed.
> > 
> > Wez @ RealVNC Ltd.
> > 
> > 
> > > -Original Message-
> > > From: Joe Perrone [mailto:[EMAIL PROTECTED]
> > > Sent: 10 August 2004 16:06
> > > To: James Weatherall
> > > Subject: RE: 4.0 Client Crashes every few hours
> > > 
> > > James,
> > > 
> > > I just confirmed again that the Viewer just disspeared and
> > > both users had "Shared" selected.  No network issues I 
> > > checked the Catalyst ports.
> > > Is there a way to make all new connections "Shared" and what 
> > > do you think about the crashing?
> > > -Joe
> > > 
> > > -Original Message-
> > > From: James Weatherall [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, August 10, 2004 9:45 AM
> > > To: Joe Perrone; [EMAIL PROTECTED]
> > > Subject: RE: 4.0 Client Crashes every few hours
> > > 
> > > 
> > > Joe,
> > > 
> > > Please provide more detail regarding VNC Viewer "crashing".
> > > Many users
> > > use the term "crash" when they simply mean that the viewer 
> > has closed,
> > > which is most often caused by network issues.
> > > 
> > > Wez @ RealVNC Ltd.
> > > 
> > > 
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED]
> > 
> > > > On Behalf Of Joe Perrone
> > > > Sent: 10 August 2004 13:18
> > > > To: [EMAIL PROTECTED]
> > > > Subject: 4.0 Client Crashes every few hours
> > > > 
> > > > Hello,
> > > > 
> > > > I have a client (w2k) that controls a server (running XP) 
> > They both 
> > > > have the latest service packs on them.  The VNC Viewer 
> > app crashes 
> > > > regularly every 3-4 hours.  I tried it on another 
> client with the 
> > > > same results.  Is their a bug in the VNC server or a 
> service pack 
> > > > for the VNC server for XP?
> > > > Otherwise, perhaps the connection settings we are using are 
> > > > the problem.  BTW, the old version 3.x version of VNC used in 
> > > > this exact situation never crashed in this exact environment. 
> > > > Any suggestions?
> > > > 
> > > > Any help would be greatly appreciated as we use VNC clients
> > > every day.
> > > > 
> > > > [Using VNC Viewer Version 4.0 6/15/04 build. With 
> associated 4.0 
> > > > server. Color level = Low, ]
> > > > 
> > > > 
> > > > 
> > > > -Joe
> ___
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Changing Idle timeout of Xvnc Server (was RE: 4.0 Client Crashes every few hours)

[Nepple, Bruce]

OK --- I found the info on the Xvnc manpage.  On the vncserver manpage it wasn't
real obvious that I needed to also read the Xvnc manpage.  Also be nice if vncserver -h
said something like "More Options available through Xvnc -help"  The Xvnc manpage
is very explicit about checking the vncserver manpage.

 
The timeout is *VERY* annoying, BTW. Why was the default behavior changed?

Starting the server, add -IdleTimeout 0 to the vncserver command line

The timeout can be changed in an existing server (display :1) with the command:
 vncconfig -display :1  IdleTimeout=0

I'm assuming that 0 will disable the timeout, and that the set value will be used, 
rather than
only the value read at startup (I'll know in a couple hours).

Bruce

> -Original Message-
> From: Alex K. Angelopoulos [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 12, 2004 5:47 PM
> To: Nepple, Bruce; [EMAIL PROTECTED]
> Subject: Re: 4.0 Client Crashes every few hours
> 
> 
> You're not seeing it in VNCViewer because the server is what 
> drops them. The 
> IdleTimeout is mentioned in the release notes 
> (release-notes.htm) but most 
> importantly in winvnc.html. The GUI config is on the 
> Connections tab for the 
> server.  The actual documentation from wincnc.html below; you 
> may way to 
> just do a "find" in that page for IdleTimeout since it will 
> be formatted 
> more nicely. :)
> 
> IdleTimeout=(seconds)
> Disconnect idle clients after
> 
> An idle client is one which has transmitted no keyboard or 
> pointer events 
> for more than a certain length of time. The VNC Server can be 
> configured 
> with a threshold, expressed in seconds, after which idle 
> clients will be 
> disconnected to conserve resources. If the threshold 
> specified is zero 
> seconds then connections will never timeout. The default idle 
> timeout is one 
> hour.
> 
> Note that pointer and keyboard events received from clients 
> will prevent 
> their connection timing out even if the VNC Server is configured to 
> otherwiseignore those events (see below).
> 
> 
> 
> Nepple, Bruce wrote:
> > I wish I could find it in the documentation.  Certainly 
> can't find it
> > on the
> > vncserver man page, or in any windows vnc viewer documentation, or a
> > entry anywhere
> > in the vnc viewer options for a value or some checkbox to 
> disable it.
> > Not in the FAQ either.
> >
> > Be nice if you gave us a hint as to WHAT documentation might contain
> > this tasty tidbit.
> >
> > Bruce
> >
> >
> >
> >> -Original Message-
> >> From: James Weatherall [mailto:[EMAIL PROTECTED]
> >> Sent: Tuesday, August 10, 2004 8:23 AM
> >> To: 'Joe Perrone'
> >> Cc: [EMAIL PROTECTED]
> >> Subject: RE: 4.0 Client Crashes every few hours
> >>
> >>
> >> Joe,
> >>
> >> "The client dissappears after about 2 or 3 hours" suggests
> >> that it's simply
> >> the idle timeout on the connections, causing them to be
> >> dropped.  Please
> >> read the documentation for details on select a longer timeout
> >> if required.
> >>
> >> Wez @ RealVNC Ltd.
> >>
> >>
> >>> -Original Message-
> >>> From: Joe Perrone [mailto:[EMAIL PROTECTED]
> >>> Sent: 10 August 2004 16:21
> >>> To: James Weatherall
> >>> Subject: RE: 4.0 Client Crashes every few hours
> >>>
> >>> No, what I meant by checking the Catalyst I mean that I
> >>> checked the exact ports on the Cisco Catalyst switch that all
> >>> 3 pc's are connected to and none of them have any reset
> >>> sockets or bad packets.  The client dissapears after about 2
> >>> or 3 hours regularly.  The Host is running Win XP and the
> >>> clients are W2k professional.
> >>>
> >>> -Joe
> >>>
> >>> -Original Message-
> >>> From: James Weatherall [mailto:[EMAIL PROTECTED]
> >>> Sent: Tuesday, August 10, 2004 11:17 AM
> >>> To: Joe Perrone
> >>> Cc: [EMAIL PROTECTED]
> >>> Subject: RE: 4.0 Client Crashes every few hours
> >>>
> >>>
> >>> Joe,
> >>>
> >>> Please provide more detail regarding VNC Viewer
> >>> "dissappearing", such as
> >>> how long the viewer had been connected, etc.  Information on the
> >>> platforms in use may also be useful.
> >>>
> >>> What do you mean by "the Catalyst

Re: VNC Security

[Andy Bruce - softwareAB]

This is a very interesting question to me. In my own case, I do have SSH 
setup thru Cygwin (http://www.cygwin.com/) for my local network and I 
use VNC thru that connection when I need to manage my own stuff 
remotely. However, I have to admit that when I use VNC to aid remote 
clients (which happens quite frequently) I don't worry about encryption 
whatsoever.

FWIW, here's my approach:
1. I don't even try to explain setting up an SSH daemon to them. I 
simply have them install the VNC server in user-mode and start it.

2. If I can't explain to them in 5 min or less how to do port 
forwarding, I just have them connect directly to their cable/dsl modem.

3. Get the debugging and/or support done.
4. Have them stop the VNC server. Since it isn't running as a service, 
it won't start up next time and so won't be a security risk.

5. Tell them to turn off port forwarding from the router (if they could 
grok it), or just have them connect their PC back to the router and 
their router back to the cable/dsl modem. In either case, 5900 isn't 
available to the outside world so there's no risk even if they were 
running VNC in service-mode.

I have to agree with Steve that this is, for all practical purposes, a 
non-existent security risk. The only things that could go wrong:

a. "Somebody" is sniffing the packet stream while the VNC passwords are 
being exchanged, and, during that 20 minute interchange, cracks the 
password and logs onto the VNC server. Of course, we would notice this 
problem on both ends!

b. I have never captured the data shared between client and server 
(screen/UI deltas) and so have no idea if these pose a security risk or not.

c. While the VNC server is running and they are connected to the 
internet (port forwarding has the same problem as direct connect) a port 
sniffer detects that 5900 is available and immediately zooms in thru 
some VNC security hole. Wez would know a lot more about this possibility 
than me, though!

Am I missing something here?
Steve Bostedor wrote:
I'd like to know if anyone has any working examples of why an
unencrypted VNC session over the Internet is seen as such a horrible
security risk.  I understand that unencrypted ANYTHING over the Internet
lends the chance for someone to decode the packets (assuming that they
capture every one of them) but in reality, what are the real risks here
and has anyone successfully captured a VNC session from more than 2
router hops away and actually gotten any meaningful information from it?
I've captured a big chunk of a LOCAL session using Ethereal and the only
thing that I can see that is usable is the password exchange.  Agreed
that this could be a problem if someone just happened to be sniffing
your local LAN segment at that exact moment and happened to capture your
encrypted VNC password, he could crack the password and log in himself.
But how paranoid is it to go through all of the trouble of setting up
SSH to avoid that when you could just change your VNC password often and
make sure that your local LAN is reasonably secure from prying eyes?
How about once it gets out on the Internet?  Packets bounce all over the
place on the Internet.  What are the odds that someone out there will
pick your VNC packets out of all of the millions of packets running
through the back bone routers without being noticed, capture enough of
them to possibly replay a session, and actually have the patience or the
tools to do so.  I've scoured the web out of this curiosity, looking for
a tool to put VNC packets together into something useful for a hacker.
There's nothing.  Nada.  

So, I guess that what I'm asking is; what all of the fuss is about?
Your POP3 password likely gets passed unencrypted but we're being asked
to be paranoid about an encrypted VNC password?  This is all coming from
a discussion that I had with someone over the merits of using SSH with
VNC over the internet for a 10 minute VNC session.
Does anyone have anything that's not hypothetical?  Is there a tool that
I'm missing out there that does more than just crack a VNC password?
Does anyone know of any reported security breaches where VNC was a
weakness?  
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Am I an ID10T? (Listening Viewer confusion)

[Andy Bruce - softwareAB]

   1.  Use  the  System  Menu  in  top  left  of viewer (VNC Icon for the
   window).
   2. Select Options.
   3. Select Inputs tab.
   4. Voila
   Andy
   Jim W Le Gros wrote:

Hi

Ok so I understand the uses of this feature, as a newbie, I have figured
that in default viewer mode it is the settings (Options > Inputs) that sets
the limits of a viewers ability to control the remote system, so where are
the parameters that need to be set by the initiator of a session that allow
the viewer to "Only VIEW" and not have input control of the server for
educational purposes.

Also is this option available if the viewer is java browser client?

Thanks,

Jim.

Jonathan Morton [EMAIL PROTECTED]

Sun Sep 29 16:10:01 2002

*   Previous message: Am
  I an
ID10T? (Listening Viewer confusion)
*   Next message: tightvnc

error ???
*   Messages sorted by: [

date ] [

thread ] [

author ]

  _

Essentially, it lets you initiate the connection from the server
instead of the client.  The client/viewer listens for an incoming
connection from the server.  On the server, there's an 'add new
client' (for Windows, YMMV) option...that's what it does.  D)

There are three commonly-useful situations for this feature:

- If the server is behind a firewall, the viewer may not be able to
initiate a connection to it directly.  Sending a message by some
other means, that triggers the server to initiate the connection
instead, is a good workaround.

- In a classroom or other presentation situation, it's not a good
idea to have to hand out passwords to the server, and rely on each
viewer to have "shared" and "view only" set.  Making the reverse
connection can eliminate each of these problems.

- In a tech-support situation, the server may not be running all the
time due to privacy concerns, and obtaining the correct IP address
and password from an "ordinary user" can be problematic.  Setting up
a shortcut to make a reverse-connection to the tech-support viewer
eliminates a lot of frustration.

--
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Question regarding port numbers.

[Andy Bruce - softwareAB]

Before anything else, see the numerous posts (and occasional 
flame--"lazy???") on Why Open VNC Connections Are a Bad Idea.

>1. Given that the router assigns its own IP addresses to each PC in 
our network (192.168.1.101, 102, 103, etc.) how do we assign port 
numbers to each PC so that each of the 4 PCs in the network can be 
access concurrently... if this is possible?

Use your Windows TCP/IP settings to set a static IP address. Use a 
number < 100 for each machine.

>2. Can we assign ports other than 5900 to the other PC's?
You can, certainly. However, you only need to do this if you're exposing 
your VNC servers to the outside world. In that case, you'll have a 
separate port for each machine in the router, and the router will 
forward them appropriately.

To change the VNC Server port, simply double-click the VNC icon in the 
taskbar and go to the Connections tab. You can set the port there.

> 3. Can the VNC server recognize and establish communications through 
other port numbers?  If so, what port numbers should we assign to each PC.

I think this is really #2, restated.
>One last question.  Realistically, excluding the impact of slow 
connect speeds, how many people are permitted to connect to one server 
to see what an instructor is doing on the desktop of that server.

Well, Wez would know more than me. But assuming you're VNC server box is 
reasonably speedy then the bottleneck will be your remote students and 
their access and machine speeds. I have connected up to 18 sessions on a 
single VNC server without any real problems on the VNC server (P6, 
2.7gHz, 2GB sync d/ram, fast video card).

GL
Andy
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: VNC Security

[Andy Bruce - softwareAB]

First--I believe we're talking apples and oranges. VNC is not an 
appropriate solution for a true corporate network unless a firewall and 
a secure link is available (and even then is dodgy). My scenario is this:

 a. Random user in cyberspace has a problem.
 b. User installs VNC under direction of tech support:
 i. strong password
 ii. not installed as service
 iii. temporary port forwarding only
 c. User allows remote person to login, generally for 20-30 mins.
 d. User stops VNC server process and disables port forwarding
My point was that, for all practical purposes, this scenario has zero 
risk. Let's talk about what happens if an attacker does happen to be 
watching data packets and does manage to break the password during that 
session:

1. The attacker is still subject to limitations of the VNC data 
protocol. For the attacker to gain real hidden control, he would have to 
have the VNC server software accept his own third-party program via 
remote copy and execute.

2. Unless the attacker had that type of attack, he would have access 
only to mucking with the primary (zero) desktop in Windows, so no danger 
of a hidden desktop there. (VNC simply doesn't support anything other 
than primary desktop, as my remote users with Fast User Switching have 
found to their chagrin.) To take control of the situation, the hijacker 
would have to send keyboard/mouse commands to that desktop to activate 
some process during the hijack process. Therefore, I most certainly 
would notice it. The only exception is if the attacker simply mucked 
with the Windows registry, perhaps to navigate to a tainted Web site 
upon next login. That's a larger issue than whether VNC is secure.

3. As stated above, I explicitly instruct my users not to install VNC as 
a service, and then to stop the server process when we're done (and then 
turn off port forwarding). So, even if the attacker did get into the 
machine and cause a password reset--it won't help. The VNC service won't 
be running when the user next boots the machine. And if it was running, 
the port forwarding and Windows firewall would prevent the attacker from 
getting access to it again.

Only Wez and the user community can let me know if there are any 
security flaws in VNC that allow the remote system to execute physical 
programs simply based on passed data packets commands. I was under the 
impression that the only way that the VNC client executes programs is by 
sending keystrokes/mouse clicks to the remote system. (In other words, 
no type of "exec" function built into the protocol.) Therefore, the VNC 
server itself isn't ever executing any software via API calls--instead, 
VNC simply passes keyboard/mouse input to the OS and it's the OS that's 
does the execution. And the user is watching the desktop on at least one 
side of the connection.

So--while the effort to trap/break in to a VNC server may be well worth 
the effort for a corporate network with access to a rich mine of data, 
in my example it doesn't apply.

Andy
Mike Miller wrote:
On Tue, 19 Apr 2005, Andy Bruce - softwareAB wrote:
I have to agree with Steve that this is, for all practical purposes, 
a non-existent security risk. The only things that could go wrong:

a. "Somebody" is sniffing the packet stream while the VNC passwords 
are being exchanged, and, during that 20 minute interchange, cracks 
the password and logs onto the VNC server. Of course, we would notice 
this problem on both ends!

I don't know if it is possible to crack the VNC password, but I don't 
agree that you would necessarily notice this on both ends.  If the 
attacker were to log into the session when you weren't using it, he 
could then make some changes to your system (for Windows) that would 
allow him more access to your machine later.  If you were using 
Windows he could start up another VNC desktop that you might not 
notice, and he could use a different password if he wanted to (by 
copying the vnc password file, changing the password, and copying it 
back).

I hope that it is hard to crack the passwords.  I think it is hard to 
do it but I'd like to hear more about that.

Mike
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: VNC Security

[Andy Bruce - softwareAB]

Beat that horse...
---CUT---
Scenario C is assuming the following points.
1.  A single remote user with a software firewall, who doesn't belong to
a larger corporation, a one person organization.  You're supporting them
as a contractor.
At your location, setup a SSH server available on the internet with
password logins disabled and keys for various users who need your
support.  On their machine a PuTTY configuration (or similar client)
with all the port forwards setup and the connection details configured.
Have the client connect initiate the putty connection (as simple as a
double click) which forwards the port for VNC to the SSH server on a
predestined port.  Connect to this port and take over their machine.
Total user work required, double clicking on a PuTTY connection.
---CUT---
A. the user doesn't have putty installed. Someone (meaning me) has to talk them thru it. 
("now type -L 5900:localhost:5900, oh wait, not the number one, but the letter L ah 
heck...")
B. much of the time, the user can't spell "port forwarding", much less do it. 
Hence in many situations they are connected to internet directly and we just tell them to 
have windows firewall allow VNC server port access.
C. If the user can get this setup without too much assistance, they can setup 
their own SSH daemon and let me come in under RDO or VNC or whatever. So the 
conversation is moot.
Andy
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: VNC Security

[Andy Bruce - softwareAB]

---BEGIN CUT---
In all of these scenarios, you do the setup before hand.  All of these
scenarios are easily installed, and configured as a tech, and are as
simple as 1-3 clicks for a user, no config, because everything (ssh
keys, vpn preshared keys, etc) are all saved and stored in advance.
A moment of setup in advance saves you hours of support later.
---END CUT---
I couldn't agree more. However, in my case I don't have access to these remote 
users PCs. They don't work for me or any particular company. In the usual case, 
they call in with a problem out of the blue. Sometimes I can help them without 
logging in. Sometimes I can't.
For our internal boxes, I happen to use either the full Cygwin package or at least openssh for the 
users I work with. Then they just open port 22 (I normally don't want them to keep even that open) 
and I login and get work done. While I wouldn't call getting an SSH daemon setup on windows 
*correctly* a "moment" (google "sshd problems windows" for why...) it's well 
worth the effort. Public/private keys are even better. It's just that in many situations it's not 
possible to do the setup before hand.
Regards,
Andy
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: double posts

[Andy Bruce - softwareAB]

I'm trying this--for this message I'm removing all the auto-generated TO 
and CC and just putting in [EMAIL PROTECTED]

Let's all just do that when responding to messages and I bet the problem 
disappears.

Andy
Collins, Kevin [MindWorks] wrote:
I've gotten some duplicates a week or more later (this happened more
than 1 time)...
Kevin 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Yann Renard
Sent: Tuesday, May 03, 2005 7:46 AM
To: Erik Soderquist; vnc-list@realvnc.com
Subject: Re: double posts
Erik Soderquist wrote:
 

is it just me or is this list double posting everything?
   

Erik,
I think the reply mechanism, replying to the original sender email 
address better than to the list, and ccing the message to the list gives

two messages to some people. Maybe this is configurable on the list side
so the reply automatically sends messages to the list (only once), 
better than sending it to the original poster.

I wonder why this is done this way.
Regards,
Yann
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Changing the port number in code

[Andy Bruce - softwareAB]

The problem is the client. When connecting to a server, you can specify 
the port offset from 5900 via "x:" in the connect string. I 
don't know how to make the client use a different base.

Regards,
Andy
Angelo Sarto wrote:
If I may ask, why hardcode?  The configuration allows any port to be selected?
--Angelo
On 5/5/05, Tony <[EMAIL PROTECTED]> wrote:
 

Ok, i am sure its been brought up before, but i need to change, and
hardcode the port #.
59xx will not work, i need to move it to a lower port due to firewall
restrictions that are
out of our control, and using SSH/etc for port redirection isnt
practical since im using
systemtools' STRCM to load workstations remotely.
This wont need to be changed on the fly, so doing it in the actual code
makes the most
sense.
Since I'm not a C++ person, can anyone point me to all the proper places
to do this im
sure if i know where to go, i can figure out what to do once im there.
Or is it going to more work then i can do, and I just need to find a C guy ?
Oh, and no, we cant afford to just go buy a commercial version that
supports this.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
   

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: How do you know that VNC is being sent through SSH?

[Andy Bruce - softwareAB]

Well--

1. Don't expose your VNC port on the internet. Just expose the SSH port.

2. If you do connect to the VNC server in question, you're going thru SSH.

Andy


Greg Berrill wrote:

I am setting up my VNC software and am going to make the connection be 
tunnelled through SSH. i was just wondering how do you know that the 
VNC connection is going through the SSH tunnel?

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Screen freezing in VNC4.1.1 over SSH

[Andy Bruce - softwareAB]

I think you are confusing SSH timeouts (which I get sporadically myself 
when connecting to my business LAN) with the VNC freeze. In my 
experience, the VNC freeze only occurs when the underlying network 
connection itself hangs. Although it may appear that the problem is 
VNC-related (since you can start another session presumably without 
restarting your SSH tunnelling client), the symptom you report happens 
only when there is a problem with the underlying network connection. VNC 
is simply the innocent consumer of that connection.


As far as I know, the only solution to your problem is to work thru the 
SSH connectivity problems. I have one Windows-based client company who 
has allowed the single port 22 to be opened (specifically for my use in 
fact) since they do not wish to give me corporate VPN access. As I 
mentioned above, that particular connection times out, freezes up, and 
does other strange things which their "normal" VPN connection does not 
do. You're in luck since you appear to have some control over your 
connection to the remote Linux box; I suggest that you turn on debugging 
on the SSH daemon on that box to get detailed information about what's 
going on. In my case, the network folks (all M$NE certified, and 
therefore useless for any real work) simply shrug their shoulders and 
brush me off.


Good luck,

Andy

Mark wrote:


I have been having problems with sessions hanging when running VNC
over SSH. I will have a session open, and after some time find that
the screen has frozen. Refreshing the screen doesn't help, however if
I close the session I can open another one just fine (though it seems
to take a few seconds longer to reconnect than it did originally).
This happens in the following circumstances:

* if I minimize the VNC session window for about 15 or more minutes,
the session always freezes immediately after I maximize (I have a
batch file printing the time continually and the time is current when
I maximise, but does not continue to update). If I minimise and then
maximise after a couple of minutes, the session does not freeze. If I
maximise between 2 and 15 minutes the session sometimes freezes
(almost always after 5 minutes).
* if the session is not minimised but just in the background, the
session usually freezes but after a more variable and longer length of
time.
* sometimes the session freezes when I am using it actively. Again,
length of time is variable.

The setup I am using is as follows:

VNC Client (RealVNC Free 4.1.1) on Win XP Pro
|
Linux firewall running NAT
|
ADSL Router running NAT
|
|
ADSL Router running NAT
|
Linux Firewall running NAT & OpenSSHd
|
Remote machine (RealVNC Free 4.1.1 server) on Win XP Pro
-session timeout set to 6 seconds

The only port open on the remote Linux firewall is 22, and I set up a
SSH tunnel from local client (with PuTTY) to the remote Linux
Firewall, which then forwards VNC traffic to the remote VNC server.

I don't see any problem with the SSH session when the VNC session
hangs (nothing in the SSH log, SSH terminal session is fine). I have
also reproduced the problem connecting from different PCs.

I do get an entry in the Windows event log of the VNC server
(connection reset by peer 10054), but this entry is logged after the
time session froze, so presumably it is a result of the freeze not the
cause?

If I put the remote machine in front of the Linux firewall (ie just in
ADSL router NAT) and connect directly (ie no SSH tunnel) the
connection is stable and does not hang.

Any assistance in fixing this would be most appreciated.

thanks

mark.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Work simultaneously on both computers

[Andy Bruce - softwareAB]

Sure VNC does.

You just set the preferences to allow multiple clients to connect to the 
same machine. I do that all the time. Helpful when other developers and 
myself both need to look at the desktop for a given remote box with a 
problem.


Andy

John Aldrich wrote:


Ahh... You want two people to be able to use the same PC at the same time. I
don't believe VNC will let you do that. Terminal Server might, but the app
would also have to be capable of running two copies at the same time, which
might be a problem.

As Rob said, with Linux, it would be definitely be possible to do what you
want natively, but I don't think it's going to be easily do-able in Windows.

-Original Message-
From: Pedro Sousa [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 08, 2005 11:59 AM
To: 'Rob Nicholson'; 'John Aldrich'; 'Pedro Sousa'; vnc-list@realvnc.com
Subject: RE: Work simultaneously on both computers


Thank you for your answers.
John, I tried to look for the answer in the sites referred but I couldn't
find anything related to it. Like says Rob, I'm not sure also that this is
possible.
What I really want is to work from my remote PC in a program allocated in
the host computer while someone works at the same time in the host in
another program.
Is there any way to do that? May be another program?
This would be very useful, because I could use a licensed program in any pc
without breaking the legal contract.
Thank you for your help,

Pedro.

-Mensagem original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Em nome
de Rob Nicholson
Enviada: segunda-feira, 6 de Junho de 2005 17:51
Para: 'John Aldrich'; 'Pedro Sousa'; vnc-list@realvnc.com
Assunto: RE: Work simultaneously on both computers

Are your sure about this? The poster appears to want to be able to have two
users logged into the *same* PC and see different desktops. For Windows
environment, what he's describing is something like terminal server with
maybe Citrix.

With Linux and a windowing interface, I believe it's possible but that's not
my area of speciality.

Rob.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Aldrich
Sent: 06 June 2005 14:16
To: 'Pedro Sousa'; vnc-list@realvnc.com
Subject: RE: Work simultaneously on both computers

Yes. You have to read the FAQ on how to do it, but there is an easy way to
have VNC show :0. By default this is not done. You need to start the VNC
Server at boot. Go to http://faq.gotomyvnc.com and read the FAQ there, then
go to www.realvnc.com and read the faq there. Between the two (and the list
archives) you should be able to find the answer. This is actually a
fairly-common question.
John

-Original Message-
From: Pedro Sousa [mailto:[EMAIL PROTECTED]
Sent: Monday, June 06, 2005 7:11 AM
To: vnc-list@realvnc.com
Subject: Work simultaneously on both computers


Dear Sirs,



Can I use VNC to work in an application from the host computer, while
someone in the host pc can still work in a different application? F.i.: I'm
accessing the host pc to work in the accounting software, while another
person is writing a letter in the host at the same time. Or what is showing
in the desktop of the host pc is exactly what I can see in my remote pc?

Thank you for your help,



Pedro
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Re: Non-fixed IP addresses

[Andy Bruce - softwareAB]

As long as the hostnames are resolvable (normally the case in any type 
of DHCP environment) then this is a non issue. The bigger issues are that:


1. The students will know that they are being watched (threads in this 
group indicate that can't be turned off).


2. You need to ensure that that there's no way for port 5900 to be 
accessed on any target machine from outside the firewall.


Andy

Elizabeth Bentley wrote:


I am thinking of adding VNC to our school network to allow me to monitor use
of computers in our library.
I spoke to the technician about it and he seemed to think that one problem
would be that our work stations do not have fixed IP addresses but are
allocated a different one each time they are switched on/logged on.

We use Novel Netware.

Could you let me know whether this is a real problem or one that can be
solved?

EB
---
Elizabeth Bentley, Head of Learning Resources
Northbrook C of E School, London, UK
mailto:[EMAIL PROTECTED]
---
School Librarians Network is a forum where UK school librarians can exchange
news, views and ideas and give each other mutual support.
To subscribe send a blank email to: <[EMAIL PROTECTED]>
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list