Wez,
We use VNC internally on our trusted network. Also, I have downloaded
version 4.1.2, but not had the opportunity to deploy it yet.
Regarding my server question, I see the following messages in the
application log:
Connections: closed: 192.168.11.51::4749 (Clean Disconnection)
-- when I close my VNC window
Connections: closed: 192.168.11.51::1238 (Timed Out) -- when the
server quits responding and I eventually see the reconnect message.
Occasionally:
Connections: closed: 192.168.10.49::1342 (write: Connection
aborted (10053)) -- I think this is when it fails to re-paint the screen
completely, aborts, and prompts to re-connect
Server Time Out:
Typically, the server Times Out, prompts to re-connect, and all is fine.
Sometimes, the server will Time Out, prompt for re-connect, Connects
with no response and Times Out again. I have seen this happen up to 15
times in a row. If it happens more than 5 times in a row, I typically,
answer no to re-connect, wait a few minutes, and then I can re-connect
again.
During these events, the re-connect paints the entire screen again and
then I either have control or the session is still timing out and
eventually prompts to re-connect.
This only happens on my SBS server system. No other PC device running
Server Mode has this problem. Just the new SBS Server.
As I said, during these Time Out periods, I can communicate with the
server on other services without problem. Just not VNC.
In regards to Teng-Fond Seak's question: I installed VNC by launching
the EXE, not via Add/Remove Programs.
Thanks,
Mike
-----Original Message-----
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Friday, November 16, 2007 2:29 AM
To: Mike Cavanagh; vnc-list@realvnc.com
Subject: RE: windows 2003 connection loss
Mike,
Firstly, VNC Free Edition is not designed to be used directly over an
untrusted network. Additionally, VNC Free Edition 4.1.1 had a security
vulnerability, so you should upgrade any machines that are using it to
version 4.1.2 immediately.
As for the lack of response from the server, this usually indicates some
sort of networking issue, e.g. dodgy wireless router, misconfigured VPN
or
third-party firewall/anti-virus software interference. You can check
the
Application Event Log of the server computer for errors and
"disconnected"
messages to determine why the original connection was closed by the
server.
Cheers,
--
Wez @ RealVNC Ltd
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mike Cavanagh
> Sent: 15 November 2007 23:06
> To: vnc-list@realvnc.com
> Subject: windows 2003 connection loss
>
> I have Version RealVNC 4.1.1 Free Edition running in my environment.
> Every PC with it runs fine.
>
> I just added a Windows 2003 Small Business Server to the
> environment and added RealVNC to it. RealVNC Server runs in
> Service Mode.
>
>
>
>
>
> I am experiencing disconnects from the server. I notice the
> session quits responding and eventually, I get the dialog box
> asking if I want to reconnect. I select yes and I am
> immediately re-connected. During the no response period, I
> am able to communicate with the server using other tools
> (file shares, Ping, nbtstat, etc).
>
>
>
> Does anyone have any ideas why the software occasionally
> quits responding? As I said in the beginning, all other PCs
> work fine.
>
>
>
> Thanks,
>
> Mike Cavanagh
> _______________________________________________
> 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
