Hi Mike,
This sounds like some sort of networking issue with the host operating
system or network environment. Are you connecting via a VPN?
Cheers,
--
Wez @ RealVNC Ltd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Cavanagh
Sent: 16
Hi Derek,
UltraVNC is based upon our old VNC 3.3 codebase, but is not VNC-compatible.
I'm not sure what it is that you mean is crashing, so it's hard to say
what the problem might be.
Cheers,
--
Wez @ RealVNC Ltd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
No, no, I'm a 100% sure we still need to pass through Add/Remove
programs (ARP) to install softwares.
Three months ago, I installed VNC 4.1.2 Free edition on a new Windows
Server 2003 (Standard Edition). I forgot then to use ARP to install it.
Later on, when I tried to connect to VNC,
After wondering why I wasn't able to cut/paste from Winblows to my Linux
VNC session, I found it was because I wasn't running vncconfig. So. I
added it to my xstartup. However, this didn't work. This is what I
added to xstartup:
vncconfig -display=:1 -nowin
And this is the result, from
Hi Steve,
The problem is not with running UltraVNC alongside a standard VNC server -
UltraVNC is based on the old VNC 3 system, which used different registry
keys, etc, but with protocol compatibility. UltraVNC uses a custom protocol
that although based on RFB is not fully compatible with it.
I have both installed on a win 2000 server no problem
except I keep the con fig slightly different of course
James Weatherall wrote:
Hi Derek,
UltraVNC is based upon our old VNC 3.3 codebase, but is not VNC-compatible.
I'm not sure what it is that you mean is crashing, so it's hard to say
Hi Derek,
Command-line parameters override any parameters read from the registry, and
VNC 4 series servers do not write to the registry. Parameters not specified
on the command-line will be read from the registry, so you need to specify
all parameters that you want to pin down on the
I am afraid that you are mistaken - you may be thinking of the old Windows
NT Terminal Server Edition, for which there were special requirements for
software installation.
Cheers,
--
Wez @ RealVNC Ltd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
No VPN. I am on the same LAN, same network switch. No Hops, No
bridges, etc.
I am leaning towards a resource issue within the server (SBS 2003 R2).
Strange it only happens to this server and none of my other PCs (they
are win xp sp2 and win 2000 sp4).
-Original Message-
From: James
