I downloaded the latest version of VNC and installed it on 2 machines on my
LAN behine a router. One of the machines is connected to the router via a
wireless connection, the second on an ethernet connection to the router.Router
is then connected to a broadband modem. Both machines were behind Kerio's 2.14
firewall and the VNC was installed in XP Pro with service pack 1 installed.
VNC worked in the situation over the locan LAN with the XP Pro
software.Settings are default for VNC server and viewer.
Now here is the problem:
I sent the VNC software to a friend and he installed it on his slow Pentium
120 computer with Win98 installed.. He then connected to his dialup compuserve
account via a modem, fired up the VNC server, and then I tried to connect with
the VNC viewer using the XP Pro box that connects to the router via the
ethernet connection. No changes were made to the setup that had run
successfully with the local computer that is connected to the router
wirelessly. VNC found the computer on the ip adddress, asked for the password,
and made the connection. From his computer, he sees the mouse move once and
then nothing. His system is active otherwise. I see his computer screen but no
movement and mouse activity on my part causes no activity on his computer. The
XP Pro computer eventually shows VNC is nt responding and I have to kill the
program. We tried this several times, even exited the Kerio firewall, with the
same results. THis computer is multibooted with Win98, W2K, RedHat 8.0 also
loaded in separate partitions. The W2K with SP 3 exhibited the same behavior
and blue screen with an IRQL_NOT_EQUAL error ( usually a driver problem). W2K
does not have a firewall installed. The Win98 version on this machine works
with the Win98 version on his machine.
I want to use this software to remotely support seniors at a retirement home
that have a mixture of Microsoft OSes, but mainly Win98 and WinME, although
the XP numbers are increasing as people add new machines. I realize I can use
the builtin XP remote software with XP users but would prefer to use on
approach.

Anyone got ideas on why VNC would exhibit this behavior on XP Pro and W2K?
Thanks in advance
BJ
BJ
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to