The freeze up and jerky mouse most of us are referring to is in a LAN
invironment and not through the internet.
So if your having problems over the internet also, then it doesn't matter
what form of connection is used.
Terry Houchins
Network Coordinator
Fujikoki America
Dallas, TX 75234
"Michael Salem"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.uk> cc:
Sent by: Subject: Windows freeze - workaround
vnc-list-admin@r
ealvnc.com
11/13/2002 05:18
AM
Please respond
to vnc-list
There have been several postings about VNC freezing and disconnecting
with viewers running under Windows. Mainly Win98, I think, but
possibly other versions too.
I have this problem; VNC works perfectly on a local network for me,
but when connected over a Virtual Private Network via the Internet
there are always problems when using any of the available VNC viewers
for WIndows.
The underlying VPN connection is rock-solid; the network can be
browsed, files transferred (without VCN), etc. with _no_ problems
ever.
At best the VNC connection is reasonably good; the mouse cursor is a
bit jerky and sometimes "sticks" for a few seconds. After a few
minutes (perhaps 10 minutes) the connection breaks, but can be
reconnected immediately.
At worst, after the connection is established the mouse moves very
jerkily, sometimes taking 30 seconds to catch up; after a short time
(from a few seconds to a couple of minutes) the connection breaks,
even if mouse and keyboard haven't been touched.
The type of behaviour depends entirely upon the particular client
machine. One of my machines is so bad that I consider the others
"good", but in reality the connection is merely less unreliable.
I don't have a wide breadth of equipment: I am generalising on
results with four machines over the same VPN (implemented by the VPN
support built into a Vigor 2200USB router at the server end). Clients
connect via a dialup modem connection, or ADSL (no difference).
The Subject line promised a workaround: I have found that if I
connect via Java with a Web browser (Internet Explorer 6) I get a
connection which has been much better. So far I have used it very
little, but have done things from the worst machine that would have
required 2 or 3 reconnections before. The cursor movement seems freer
and less jerky.
To use a browser, Java support must be enabled. Over a VPN, simply
enter the address as http://machine_name:5800 (for the default port,
0). I find it useful to work full-screen: F11 with Internet Explorer.
I should expect the same technique to work over a non-private (and
insecure) Internet connection.
The VNC server must be configured to support Java. One of mine
wasn't; so I connected unreliably and enabled Java support online.
There is obviously a problem with VNC viewer for Windows. From my
experience I conclude that it is not a conflict with the core
components of Windows 98 itself (LAN connections are fine). It may be
a conflict with the VPN support modules. I don't know if it is the
"fault" of VNC viewer or Microsoft.
I hope this is of use to people with the freezing/disconnecting
problem, and possibly to developers. If anybody would like me to test
experimental viewers, I have a nice unreliable system to do it on!
Best wishes,
--
Michael Salem
_______________________________________________
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
