Hi,
In that case, it sounds like the xinetd configuration you're using isn't
correct, xinetd can't read it, you're not running xinetd, or you're
connecting to the wrong computer by mistake.
The latter problem can be ruled out by running vncserver :1 to start a
desktop on display 1, then try conne
Hi Dave,
We're working on it but I'm afraid I can't give a definite date.
Cheers,
Wez @ RealVNC Ltd.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Network Dave
> Sent: 12 January 2007 15:22
> To: vnc-list@realvnc.com
> Subject: Windows Vista
Ray,
The thing to do is examine the log files for the desktops you're running on
the two systems. If you find that one machine has problems with the
xstartup apps connecting to the desktop then check the DISPLAY environment
variable. We've heard of problems in the past both where X apps can't
co
Wez,
Which logs are you asking to check? I meant to include in my original
note, the VNC log for both hosts has the same info... is there a 'logging
level' to change in VNC?
Working host:
Xvnc Free Edition 4.1.2 - built May 12 2006 17:52:56
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.r
>From what you've described, it almost looks like the xstartup script isn't
being run. Are you sure that the user's xstartup script is readable and
executable, and that they "vncserver" Perl script hasn't been modified from
the out-of-the-box version?
Wez @ RealVNC Ltd.
> -Original Message-
hallo,
i have problem with VNC-Server on Workstations with 24-Bit Colordepth
(Matrox G550 @ 1680*1050). The vnc-server-task use 100% of CPU (AMD
Athlon64 3500+, 1GB RAM). If i switch to 16Bit or switch to
[EMAIL PROTECTED] the CPU is normaly at 2-3%.
any idea? not change the Matrox-Card's :-
James / Mick,
Thank you both for your prompt response to this inquiry. The Symantec logs
indicate that, per the VNC pass rule that I added, it is ignoring traffic. I
tried adding both the VNC executable to the allowed list as well as TCP port
5900. Norton disables the WinXP firewall