Hello,
we use VNC via SSH. This works great on most of our servers. We do have
one server that does not act as it should be. When launching the vncviewer
on my pc, the VNC-windows opens and closes immediately. The
/var/adm/X2msgs -file contains the following.
16/04/03 09:27:52 All Rights
Hello,
Firstly, I'm very impressed with VNC - very reliable, and it seems to do
just what I'm looking for.
However I have a question,
I will be installing VNC on systems for my client so that our engineers
can remotely configure and diagnose systems on site.
The client I am working
A Google search turns up many results:
http://www.google.com/search?hl=enie=ISO-8859-1q=palm+vncbtnG=Google+Search
I have used several versions of PalmVNC successfully. Most recently I
tried version 2.0.1, but I've also used version 1.40, at least. It
certainly works, although the small screen
Is there an alwaysshared for windows in the works? I see a few posts in the archives
referencing it to enforce sharing from the server on *nix, but I tried for my Windows
server and gently reminded that it is not a valid option.
3.3.7, Win2k
Thank you.
Chad
Is the best way to connect to someone with dialup, using vnc, by finding out
the temporary real world IP address they are assigned at that time you want to
connect to them. Or can you connect the normal way with vnc and enter the name
of the pc and port number. (ex. host:5800). I guess why I
This is wierd. When I run a certain application in a VNC window, it's
invisible. The host and client are both Win 2K, and the application is a .NET
Windows Forms application. Earlier versions of the application run fine over
VNC. The application clearly runs (and is visible) on the host and in
-Original Message-
From: Joel E. Lieberman, Ph.D. [mailto:[EMAIL PROTECTED]
I am still not having any success with getting the VNC Server to run in
the
alwaysshared mode on Linux. I start the server with the command:
vncserver -alwaysshared . The server starts and runs fine -
Chad LaFarge said:
Is there an alwaysshared for windows in the works? I see a few posts in
the archives
referencing it to enforce sharing from the server on *nix, but I tried for
my Windows
server and gently reminded that it is not a valid option.
3.3.7, Win2k
Thank you.
Chad
Look at
CBee
Thanks for your latest reply. I dont want to be a pain, but your
explanation seems to partially contradict the VNC documentation. Here is an
excerpt from the docs:
*
-alwaysshared
Always treat new clients as shared (i.e. ignore client's shared flag).
-nevershared
Never treat new clients
My reply was based on my old experience, If the documentation says something
else, then it shoud be like that. If not, it's a bug (in the documentation
or in the tool...) Hence report it as such.
CBee
-Original Message-
From: Joel E. Lieberman, Ph.D. [mailto:[EMAIL PROTECTED]
Sent:
CBee
I was afraid to call it a bug until someone could confirm that I wasnt
simply making a mistake in using the software. Hopefully a number of other
experienced users are reading this and will either correct me or confirm
that it is a bug.
Again, thanks for all the effort you have put into
Hello Kevin,
KF == Kevin Faust [EMAIL PROTECTED] writes:
KF This is pretty basic, but... You can specify a non-standard port
KF when running vncserver by using the -rfbport option
KF How do you specify the non-standard port when trying to connect to
KF that server using vncviewer ???
Perhaps
Well... dead keys in winvncviewer 3.3.7 actually do not work and all patches
I found in this mailing list are not satisfactory to me, so I wrote my own
patch to make dead keys OK for me (Swiss french keyboard). I do not have
info about other national keyboards with dead keys, but it should work
gvillaran said:
Hey, im a newbie and im trying to install vnc on a RH9 server, and i
want to access it with and Win XP.
I have a problem when i connect from linux to windows everything is
fine, but when i connect from XP to Redhat i only get a gray screen with
the mouse, i can move the mouse
... resent with patch inline ...
Well... dead keys in winvncviewer 3.3.7 actually do not work and all patches
I found in this mailing list are not satisfactory to me, so I wrote my own
patch to make dead keys OK for me (Swiss french keyboard). I do not have
info about other national keyboards
Joel
I have tested with VNC 3.3.7 on Redhat 7.2, and I don't have your problem. I
start the server with vncserver -alwaysshared. Then I start two viewers in
non-shared mode, and they both stay connected. If I start the server with
just vncserver, then the first viewer is kicked out when the
It does work - I've do it with my PC Pro Camera all the time from work. I
am using the default VNC server settings.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Matt Debouge
Sent: Tuesday, May 27, 2003 4:32 PM
To: [EMAIL PROTECTED]
Subject: VNC and
How would people go about using VNC over a dialup connection? We need to connect to
some laptops, some older running Win95, some newer
running Win2k.
None have an internet account, so we have to dialin, then connect with VNC.
I think we have it working ok on Win95, however on Win2k, you setup the
Hi
I'm having problems to start the vncserver in my solaris workstation. In my
log i get:
29/05/03 12:21:18 Xvnc version 3.3.7 - built Feb 28 2003 18:43:51
29/05/03 12:21:18 Copyright (C) 2002-2003 RealVNC Ltd.
29/05/03 12:21:18 Copyright (C) 1994-2000 ATT Laboratories Cambridge.
29/05/03
19 matches
Mail list logo
