RE: server closed connection unexpectedly

2007-01-30 Thread James Weatherall
Jcn50,

Now that you have access to the system again, can you check the VNC Server's
"Connections: closed" log events corresponding to the failed connections, to
find out what was preventing connections from working?  If the system had
something else hogging the CPU at higher priority than winvnc4.exe, I'd
expect some sort of write timeout error, but it would be interesting to
check, since the problem may actually have been much lower-level.

As a general rule, winvnc4.exe runs at the Normal priority and this is fine
even if something else starts using lots of CPU at that priority, because
the two processes will then get half of the available CPU cycles each, in
principle.  The fact that this isn't what you were seeing suggests that it
was something else, like a virus scanner or some other high-priority
process, that had gone rogue.

You don't really want to run your VNC Server at a higher priority - if you
do that then it takes priority over the programs you're using it to access,
which almost certainly isn't what you want.  What you actually want is for
VNC Server to be guaranteed up to, say, 20% of the available CPU cycles, if
it wants them, so that it never gets starved of CPU and never starves any
other processes.  Unfortunately, this isn't an arrangement that Windows
provides any in-built support for.

Cheers,

Wez @ RealVNC Ltd.


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: 28 January 2007 11:28
> To: vnc-list@realvnc.com
> Subject: Re: server closed connection unexpectedly
> 
> Hi Mick,
> 
> 
> > As far as I know, if the application crashed and we're 
> talking here about
> > a
> > Windows machine, then someone needs to physically access it 
> to reboot it.
> 
> I am so lucky... after 10 hours I can finally connect: the 
> offending soft
> was killed by DrWatson!
> 
> 
> > If
> > it is a Linux OS with MMF running in Vmware or WINE then 
> you should be
> > able
> > to ssh into it and kill the offending application.
> 
> Is there an alternative of ssh for Windows?...
> 
> One thing I would like to do too: start the vnc server with a high
> priority thread! There's the command "-service", there's 
> nothing I could
> add to increase the CPU priority?..
> 
> 
> jcn50.
> ___
> 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 Bug: Display comes back on wrong screen...

2007-01-30 Thread James Weatherall
Hi Kevin,

As a test, you could try VNC Viewer Enterprise Edition, which handles
multi-monitor setups correctly as far as I'm aware.

I'm not sure what you mean about "save the geometry of the display" - the
server determines the size of its own desktop, so perhaps you mean the
position of the viewer window on-screen?

Cheers,

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Benton
> Sent: 26 January 2007 19:18
> To: vnc-list@realvnc.com
> Subject: VNC Bug: Display comes back on wrong screen...
> 
> Hi all,
> 
> I looked at the active issues list on realvnc.com, and didn't 
> see this:
> 
> If RealVNC client is disconnected from the server on a multi-monitor 
> system, and the display was on the second monitor, when the 
> connection 
> is restored, it does not restore the original position of the 
> display in 
> Windows XP Pro.  For example, my #1 display has my start bar, 
> email, and 
> other tools running on it.  My second monitor is running a 
> full-screen 
> display to a remote system (laptop in this case).  That second system 
> goes away briefly (for whatever reason - hibernating in this 
> case), but 
> is brought back with the same IP, etc., I want the 
> full-screen display 
> to be restored on the secondary monitor so it won't interfere with my 
> view on my primary monitor.
> 
> It would also be extremely helpful if there was a way to specify that 
> RealVNC should save the geometry of the display for the next time I 
> display a particular host:session.
> 
> I'm using RealVNC 4.1.2 Free on all my systems.
> 
> Thanks in advance for your help / support / software! :-)
> 
> Kevin
> 
> -- 
> 
> [demime 1.01d removed an attachment of type text/x-vcard 
> which had a name of kevin.benton.vcf]
> ___
> 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: 5900 is open, but no connection happens! Screenshot....

2007-01-30 Thread James Weatherall
Brian,

What is the error you get when trying to connect?

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Brian Utley
> Sent: 25 January 2007 23:46
> To: vnc-list@realvnc.com
> Subject: 5900 is open, but no connection happens! Screenshot
> 
> here is a screenshot of my router settings.  I've been trying 
> to connect for
> a couple days but no dice.  Is there something else I need to 
> do besides
> port forwarding?
> 
> http://www.bingwalker.com/VNC.png
> 
> -- 
> Brian Utley
> 
> M: 801-541-9856
> W: 801-756-5137
> 
> 
> http://www.bingwalker.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


RE: Help

2007-01-30 Thread James Weatherall
Hi,

Another set of simple tests:

1)  Reboot the computer.
2)  Try connecting - this will presumably fail with an error.  What is the
error?
3)  Log on.
4)  Try connecting - this will presumably work.
5)  Lock the system.
6)  Try connecting - this will presumably work.
7)  Unlock & logoff the system.
8)  Try connecting - does this work?  If not, what is the error message?

Regards,

Wez @ RealVNC Ltd.


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Lim, Ying
> Sent: 25 January 2007 14:26
> To: James Weatherall; vnc-list@realvnc.com
> Subject: RE: Help
> 
> Thanks James.  
> 
> I do wait for a long time before connecting; but I am still 
> not able to figure out how to eliminate the error ...no cause 
> and no way to look.
> 
> 
> -Original Message-
> From: James Weatherall [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 25, 2007 3:15 AM
> To: Lim, Ying; 'Seak, Teng-Fong'; vnc-list@realvnc.com
> Subject: RE: Help
> 
> 
> Lim,
> 
> When the machine first comes up, try waiting a five minutes 
> or so before
> connecting.  Windows quite often gets into a strange state 
> where it takes a
> very long time to start services when booting.
> 
> Regards,
> 
> Wez @ RealVNC Ltd.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


RE: Uninstalling the mirror driver

2007-01-30 Thread James Weatherall
Hi Voor,

When you reboot the system, the device should be gone - this is why the
(un)installer prompts you to reboot.  If that hasn't happened for some
reason, you can simply select "Uninstall" from the Device Manager to remove
the driver following the next reboot.

I'm not sure what you mean by "uninstall it for some testing".  If you just
want to stop VNC Enterprise/Personal Edition from using it, you can select a
different Capture Method from the VNC Server Properties dialog.

Regards,

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of voor
> Sent: 26 January 2007 18:50
> To: vnc-list@realvnc.com
> Subject: Uninstalling the mirror driver
> 
> I installed the latest version of the RealVNC mirror driver (1.7), and
> now I'd like to uninstall it for some testing.  But after removing it
> via Add/Remove Programs in Control Panel and rebooting, the mirror
> driver is still being used, and now the driver's entry in Add/Remove
> is gone.  How do I remove the driver from the system?  Can I just boot
> into Safe Mode and delete vncmirror.sys and vncmirror.dll, or will
> this cause the system to hang as it searches for an non-existant
> driver?
> ___
> 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: server closed connection unexpectedly

2007-01-30 Thread mailing
Dear James Weatherall,


> Now that you have access to the system again, can you check the VNC
> Server's
> "Connections: closed" log events corresponding to the failed connections,
> to
> find out what was preventing connections from working?  If the system had
> something else hogging the CPU at higher priority than winvnc4.exe, I'd
> expect some sort of write timeout error, but it would be interesting to
> check, since the problem may actually have been much lower-level.

I have this in the log events, plenty of these:
- Connections: accepted >> thus giving me the password prompt
- Connections: closed (GetDC failed: Operation successful (0))

I don't know why the "Operation successful" appears(??)...since I got
"server closed connection unexpectedly" from the VNC Viewer. No timeout
event.

What is your diagnostic?...


> As a general rule, winvnc4.exe runs at the Normal priority and this is
> fine
> even if something else starts using lots of CPU at that priority, because
> the two processes will then get half of the available CPU cycles each, in
> principle.  The fact that this isn't what you were seeing suggests that it
> was something else, like a virus scanner or some other high-priority
> process, that had gone rogue.

Maybe it could be a virtual memory failure: 900 MB was remaining on the
disk, I cleaned it up. But it wouldn't bring the "GetDC failed" event,
would it?
Sometimes I noticed that Windows has sockets' problems: can't attribute
new socket. But this problem is irrelevant here since the other services
on the machine were working fine.


> You don't really want to run your VNC Server at a higher priority - if you
> do that then it takes priority over the programs you're using it to
> access,
> which almost certainly isn't what you want.  What you actually want is for
> VNC Server to be guaranteed up to, say, 20% of the available CPU cycles,
> if
> it wants them, so that it never gets starved of CPU and never starves any
> other processes.  Unfortunately, this isn't an arrangement that Windows
> provides any in-built support for.

I guess I want somethingthat doesn't fail (^0^)...
More seriously: if a software is hanging on the system, I'd better kill
the process than let it jeopardizing the machine. I guess a higher
priority could be helpful.


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


RE: RealVNC Enterprise "Connection Refused (111)"

2007-01-30 Thread James Weatherall
The log shouldn't be empty after a reboot - it should have the log for the
server when it was running before you rebooted.

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of volatile.memory
> Sent: 29 January 2007 19:06
> To: vnc-list@realvnc.com
> Subject: Re: RealVNC Enterprise "Connection Refused (111)"
> 
> After a clean boot, the log is empty. Upon trying to connect to  
> localhost:1 it reads...
> 
> Fatal server error:
> Server is already active for display 1
> If this server is no longer running, remove /tmp/.X1-lock and start  
> again
> 
> v.m
> 
> On Jan 23, 2007, at 12:47 PM, James Weatherall wrote:
> 
> > The server appears to be closing the connection for some reason.   
> > What does
> > the server error-log say?
> >
> > Regards,
> >
> > Wez @ RealVNC Ltd.
> >
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On Behalf Of volatile.memory
> >> Sent: 23 January 2007 10:42
> >> To: vnc-list@realvnc.com
> >> Subject: Re: RealVNC Enterprise "Connection Refused (111)"
> >>
> >> OK, after tracking down three problems (incorrect etc/alternatives
> >> set for vncserver and vncviewer, and an incorrect entry for the
> >> server in the Xvnc file), I now have the system pointing to all the
> >> correct executables. Config is still the same as first post, except
> >> "server" entry now points (correctly) to /usr/local/bin/Xvnc
> >>
> >> Now, when connecting locally...
> >>
> >> $ vncviewer localhost :1
> >>
> >> I get...
> >>
> >> VNC Viewer Enterprise Edition E4.2.7 for X - 
> >> ...
> >> TcpSocket: connected to 127.0.0.1::5901
> >> CConn: connected to host localhost port 5901
> >> CConn: fopen: Permission denied (13)
> >> CConn: Encryption set to 'Server'
> >> CConn: Closed: read/select: Connection reset
> >> by peer (104)
> >>
> >> This sure seems like a configuration thing to me. What next?
> >>
> >> Thanks,
> >> v.m
> >>
> >> On Jan 17, 2007, at 5:38 AM, James Weatherall wrote:
> >>
> >>> 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 connecting to it.  If you can
> >>> connect then
> >>> that rules out the latter problem, leaving only xinetd
> >>> configuration issues,
> >>> for which you'll need to look at the xinetd logs.
> >>>
> >>> Cheers,
> >>>
> >>> Wez @ RealVNC Ltd.
> >>>
> >>>
>  -Original Message-
>  From: [EMAIL PROTECTED]
>  [mailto:[EMAIL PROTECTED] On Behalf Of volatile.memory
>  Sent: 16 January 2007 18:28
>  To: vnc-list@realvnc.com
>  Subject: Re: RealVNC Enterprise "Connection Refused (111)"
> 
>  I did that initially to no avail, so I did a reboot of the
> >> system to
>  ensure all config files were picked up... still no go.
> 
>  v.m
> 
>  On Jan 16, 2007, at 5:27 AM, James Weatherall wrote:
> 
> > Have you HUPed the xinetd service, to get it to read the /etc/
> > xinetd.d/Xvnc
> > configuration file?
> >
> > Regards,
> >
> > Wez @ RealVNC Ltd.
> >
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On Behalf Of 
> volatile.memory
> >> Sent: 15 January 2007 20:18
> >> To: vnc-list@realvnc.com
> >> Subject: RealVNC Enterprise "Connection Refused (111)"
> >>
> >> I have installed RealVNC Enterprise x86 4.2.7 (with temp lic.
> >> key) on
> >> Ubuntu 6.10 via the tarball.
> >>
> >> My /etc/xinetd.d/Xvnc file is :
> >>
> >> service Xvnc
> >> {
> >>  type = UNLISTED
> >>  disable = no
> >>  socket_type = stream
> >>  protocol = tcp
> >>  wait = yes
> >>  user = root
> >>  server = /usr/bin/Xvnc
> >>  server_args = -inetd :1 -query localhost -geometry
> >> 1024x768 -
> >> depth 16 -once -fp /usr/share/X11/fonts/misc
> >> -DisconnectClients=0 -
> >> NeverShared passwordFile=/root/.vncpasswd
> >>  port = 5901
> >> }
> >>
> >> The service is up and running. Firewall (for testing 
> purposes) is
> >> off.
> >>
> >> Using command-line on the local machine...
> >>
> >>$ vncviewer localhost:1
> >>
> >> gives me...
> >>
> >>VNC Viewer Enterprise Edition E4.2.7 for X - built Dec
> >> 22 2006 11:54:07
> >>Copyright (C) 2002-2006 RealVNC Ltd.
> >>See http://www.realvnc.com for information on VNC.
> >>
> >>Thu Jan 11 20:48:09 2007
> >>TcpSocket:   connect failed:unable to connect to host:
> >> C

RE: Connection refused 10061 - XP to Win95

2007-01-30 Thread James Weatherall
Mark,

Please refer to http://www.realvnc.com/faq.html#natrouter for tips on these
sorts of network error.

Cheers,

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Mark Evans
> Sent: 27 January 2007 21:56
> To: vnc-list@realvnc.com
> Subject: Connection refused 10061 - XP to Win95
> 
> Hi,
>  
> I am trying to use RealVNC to connect from my usual XP PC to 
> a 'remote' Win95 machine downstairs, but keep getting the
> Connection Refused message.
>  
> The set-up is as follows:
>  
> LinkSys BESFR81 gateway, connected to internet, local IP 192.168.1.1.
> -- Win95 PC is connected to this, and has a static IP of 192.168.1.111
>  
> LinkSys WRT54GC router, connected to BESFR81, local IP 192.168.1.2.
> -- WinXP PC is connected to this, and has a DHCP IP - usually 
> 192.168.1.101.
>  
> I can browse either machine's Shared Documents folder from 
> the other PC via My Network Places.
>  
> To try and solve the problem, I have also set up port 
> forwarding on both routers to enable port 5900 to be forwarded to
> the Win95 PC, but this has not helped.
>  
> Any help and suggestions cheerfully received!
>  
> 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


Read: connection aborted (10053)

2007-01-30 Thread francoisch
hello

Here is one more info on this problem.

I just set up another remote VNC connection between my PC with a another PC
(different from the one I usually connect to) with this result (so far):
- the connection is alive after more than an hour (while my usual remote VNC
connection does not last more than 15-30 min.)
- the transmission speed is around 500 kbit/s, rather slow compared to my usual
remote connection (around 750 kbit/s)
- this PC = Linux, link = ADSL (Freebox + router)

As a reminder, my other VNC connection, on my local WiFi network, keeps running
with absolutely no trouble at all, at a speed = 1,5 mbit/s.

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