Re: VNC connection closed w/ error 10055

2005-10-03 Thread Collier Hill
ZoneAlarm was completely removed (no change in behavior)
Also to confirm, RealVNC was running as a service and no screen saver
enabled.
RealVNC seems to have had no issues interacting with desktop. Client
functioned
perfectly for a short period of time (1-5 minutes). Longer, if I didn't
actually do anything
on the remote machine and just let the connection sit idle.
Also, a number of other things were tried.
 Final resolution:
 I ended up uninstalling RealVNC and installing TightVNC. Was able to
connect
from Win XP systems and remote control Win 2000 system with no issues.
  So, it looke like TightVNC will be my solution. Thanks to everyone for all
the
suggestions and assistance.
 Best Regards
 On 9/29/05, James Weatherall <[EMAIL PROTECTED]> wrote:
>
> Collier,
>
> Try completely removing ZoneAlarm via the Add/Remove Programs dialog.
> We've
> had previous reports of installed third-party firewalls causing problems
> even though they weren't actually active.
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> > Sent: 29 September 2005 18:02
> > To: James Weatherall
> > Cc: vnc-list@realvnc.com
> > Subject: Re: VNC connection closed w/ error 10055
> >
> > James,
> > When i run a netstat -an on the client I get 7 "established"
> > connections.
> > one of which is vnc:
> > TCP :3307 :5900 ESTABLISHED
> > netstat -an on the vnc server machine gives me 3
> > "established" connections
> > with one vnc:
> > TCP :5900 :3307 ESTABLISHED
> > Hard to believe that 7 and 3 established connections
> > respectively, could
> > cause memory allocation or resource management problems.
> >
> > As far as firewalls are concerned, I have the Zone Labs
> > firewall installed,
> > but have it disabled so as not to interfere with VNC. In
> > addition, virus
> > scans show my system to be clean.
> > Once again, Thanks for any input.
> > Regards
> > On 9/28/05, James Weatherall <[EMAIL PROTECTED]> wrote:
> > >
> > > Collier,
> > >
> > > Error 10055 normally means that there are too many
> > connections open on
> > > either the server or viewer machine, meaning that the OS
> > can't allocate
> > > enough memory to manage them all. Try running netstat -an
> > on both the
> > > server and viewer when you see this error & check how many
> > "established"
> > > connections there are to other systems.
> > >
> > > According to a quick Google search, there are some viruses
> > that can cause
> > > this error to appear, a Windows 95 resource leak that can,
> > and it's also
> > > possible that third-party firewalling software might cause
> > similar issues
> > > if
> > > it has memory leaks, or if it exposes bugs in the OS
> > >
> > > Regards,
> > >
> > > Wez @ RealVNC Ltd.
> > >
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> > > > Sent: 27 September 2005 21:07
> > > > To: vnc-list@realvnc.com
> > > > Subject: VNC connection closed w/ error 10055
> > > >
> > > > I have seen a couple of references to this issue in previous
> > > > posts, but see
> > > > no resolution posted. So, here is my problem.
> > > > configuration:
> > > > VNC Server 4.1.1 for Windows on Windows 2000 Pro
> > > > VNC Client 4.1.1 for Windows on Windows XP Pro
> > > > I start the VNC client on XP and successfully authenticate
> > > > and connect to
> > > > the VNC server. The connection seems to function properly for
> > > > 1 - 5 minutes.
> > > > Then the connection is automatically closed with the
> > following error
> > > > message:
> > > > VNC Viewer : Question
> > > > Unable to wait for socket data: An operation on a socket
> > could not be
> > > > performed because the system lacked sufficient buffer space
> > > > or because a
> > > > queue was full. (10055)
> > > > Do you wish to attempt to reconnect to ? Yes/No
> > > > Any attempts to click "Yes" just porduce the same error
> > > > message. If I say
> > > > "No", I can reconnect and get the exact same behavior.
> > > > Thanks in advance for any thoughts.
> > > > ___
> > > > 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
___
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 connection closed w/ error 10055

2005-09-29 Thread James Weatherall
Collier,

Try completely removing ZoneAlarm via the Add/Remove Programs dialog.  We've
had previous reports of installed third-party firewalls causing problems
even though they weren't actually active.

Regards,

Wez @ RealVNC Ltd.
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> Sent: 29 September 2005 18:02
> To: James Weatherall
> Cc: vnc-list@realvnc.com
> Subject: Re: VNC connection closed w/ error 10055
> 
> James,
>  When i run a netstat -an on the client I get 7 "established" 
> connections.
> one of which is vnc:
> TCP :3307 :5900 ESTABLISHED
>   netstat -an on the vnc server machine gives me 3 
> "established" connections
> with one vnc:
> TCP :5900 :3307 ESTABLISHED
>   Hard to believe that 7 and 3 established connections 
> respectively, could
> cause memory allocation or resource management problems.
> 
> As far as firewalls are concerned, I have the Zone Labs 
> firewall installed,
> but have it disabled so as not to interfere with VNC. In 
> addition, virus
> scans show my system to be clean.
>  Once again, Thanks for any input.
>   Regards
> On 9/28/05, James Weatherall <[EMAIL PROTECTED]> wrote:
> >
> > Collier,
> >
> > Error 10055 normally means that there are too many 
> connections open on
> > either the server or viewer machine, meaning that the OS 
> can't allocate
> > enough memory to manage them all. Try running netstat -an 
> on both the
> > server and viewer when you see this error & check how many 
> "established"
> > connections there are to other systems.
> >
> > According to a quick Google search, there are some viruses 
> that can cause
> > this error to appear, a Windows 95 resource leak that can, 
> and it's also
> > possible that third-party firewalling software might cause 
> similar issues
> > if
> > it has memory leaks, or if it exposes bugs in the OS
> >
> > Regards,
> >
> > Wez @ RealVNC Ltd.
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> > > Sent: 27 September 2005 21:07
> > > To: vnc-list@realvnc.com
> > > Subject: VNC connection closed w/ error 10055
> > >
> > > I have seen a couple of references to this issue in previous
> > > posts, but see
> > > no resolution posted. So, here is my problem.
> > > configuration:
> > > VNC Server 4.1.1 for Windows on Windows 2000 Pro
> > > VNC Client 4.1.1 for Windows on Windows XP Pro
> > > I start the VNC client on XP and successfully authenticate
> > > and connect to
> > > the VNC server. The connection seems to function properly for
> > > 1 - 5 minutes.
> > > Then the connection is automatically closed with the 
> following error
> > > message:
> > > VNC Viewer : Question
> > > Unable to wait for socket data: An operation on a socket 
> could not be
> > > performed because the system lacked sufficient buffer space
> > > or because a
> > > queue was full. (10055)
> > > Do you wish to attempt to reconnect to ? Yes/No
> > > Any attempts to click "Yes" just porduce the same error
> > > message. If I say
> > > "No", I can reconnect and get the exact same behavior.
> > > Thanks in advance for any thoughts.
> > > ___
> > > 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
___
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 connection closed w/ error 10055

2005-09-29 Thread Collier Hill
James,
 When i run a netstat -an on the client I get 7 "established" connections.
one of which is vnc:
TCP :3307 :5900 ESTABLISHED
  netstat -an on the vnc server machine gives me 3 "established" connections
with one vnc:
TCP :5900 :3307 ESTABLISHED
  Hard to believe that 7 and 3 established connections respectively, could
cause memory allocation or resource management problems.

As far as firewalls are concerned, I have the Zone Labs firewall installed,
but have it disabled so as not to interfere with VNC. In addition, virus
scans show my system to be clean.
 Once again, Thanks for any input.
  Regards
On 9/28/05, James Weatherall <[EMAIL PROTECTED]> wrote:
>
> Collier,
>
> Error 10055 normally means that there are too many connections open on
> either the server or viewer machine, meaning that the OS can't allocate
> enough memory to manage them all. Try running netstat -an on both the
> server and viewer when you see this error & check how many "established"
> connections there are to other systems.
>
> According to a quick Google search, there are some viruses that can cause
> this error to appear, a Windows 95 resource leak that can, and it's also
> possible that third-party firewalling software might cause similar issues
> if
> it has memory leaks, or if it exposes bugs in the OS
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> > Sent: 27 September 2005 21:07
> > To: vnc-list@realvnc.com
> > Subject: VNC connection closed w/ error 10055
> >
> > I have seen a couple of references to this issue in previous
> > posts, but see
> > no resolution posted. So, here is my problem.
> > configuration:
> > VNC Server 4.1.1 for Windows on Windows 2000 Pro
> > VNC Client 4.1.1 for Windows on Windows XP Pro
> > I start the VNC client on XP and successfully authenticate
> > and connect to
> > the VNC server. The connection seems to function properly for
> > 1 - 5 minutes.
> > Then the connection is automatically closed with the following error
> > message:
> > VNC Viewer : Question
> > Unable to wait for socket data: An operation on a socket could not be
> > performed because the system lacked sufficient buffer space
> > or because a
> > queue was full. (10055)
> > Do you wish to attempt to reconnect to ? Yes/No
> > Any attempts to click "Yes" just porduce the same error
> > message. If I say
> > "No", I can reconnect and get the exact same behavior.
> > Thanks in advance for any thoughts.
> > ___
> > 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 connection closed w/ error 10055

2005-09-29 Thread Collier Hill
Win XP firewall is not enabled. However, at your suggestion, I added the VNC
service to the firewall definition.
 Still getting same behavior.

 On 9/27/05, John Aldrich <[EMAIL PROTECTED]> wrote:
>
> Two things:
> Do you have the XP firewall enabled? If so, try disabling it. Also, have
> you
> tried specifically allowing the VNC executeable in the firewall, even if
> disabled?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Collier Hill
> Sent: Tuesday, September 27, 2005 4:07 PM
> To: vnc-list@realvnc.com
> Subject: VNC connection closed w/ error 10055
>
>
> I have seen a couple of references to this issue in previous posts, but
> see
> no resolution posted. So, here is my problem.
> configuration:
> VNC Server 4.1.1 for Windows on Windows 2000 Pro
> VNC Client 4.1.1 for Windows on Windows XP Pro
> I start the VNC client on XP and successfully authenticate and connect to
> the VNC server. The connection seems to function properly for 1 - 5
> minutes.
> Then the connection is automatically closed with the following error
> message:
> VNC Viewer : Question
> Unable to wait for socket data: An operation on a socket could not be
> performed because the system lacked sufficient buffer space or because a
> queue was full. (10055)
> Do you wish to attempt to reconnect to ? Yes/No
> Any attempts to click "Yes" just porduce the same error message. If I say
> "No", I can reconnect and get the exact same behavior.
> Thanks in advance for any thoughts.
> ___
> 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 connection closed w/ error 10055

2005-09-28 Thread James Weatherall
Collier,

Error 10055 normally means that there are too many connections open on
either the server or viewer machine, meaning that the OS can't allocate
enough memory to manage them all.  Try running netstat -an on both the
server and viewer when you see this error & check how many "established"
connections there are to other systems.

According to a quick Google search, there are some viruses that can cause
this error to appear, a Windows 95 resource leak that can, and it's also
possible that third-party firewalling software might cause similar issues if
it has memory leaks, or if it exposes bugs in the OS

Regards,

Wez @ RealVNC Ltd.


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Collier Hill
> Sent: 27 September 2005 21:07
> To: vnc-list@realvnc.com
> Subject: VNC connection closed w/ error 10055
> 
> I have seen a couple of references to this issue in previous 
> posts, but see
> no resolution posted. So, here is my problem.
>  configuration:
> VNC Server 4.1.1 for Windows on Windows 2000 Pro
> VNC Client 4.1.1 for Windows on Windows XP Pro
>  I start the VNC client on XP and successfully authenticate 
> and connect to
> the VNC server. The connection seems to function properly for 
> 1 - 5 minutes.
> Then the connection is automatically closed with the following error
> message:
>  VNC Viewer : Question
> Unable to wait for socket data: An operation on a socket could not be
> performed because the system lacked sufficient buffer space 
> or because a
> queue was full. (10055)
> Do you wish to attempt to reconnect to ? Yes/No
>  Any attempts to click "Yes" just porduce the same error 
> message. If I say
> "No", I can reconnect and get the exact same behavior.
>  Thanks in advance for any thoughts.
> ___
> 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 connection closed w/ error 10055

2005-09-27 Thread John Aldrich
Two things:
Do you have the XP firewall enabled? If so, try disabling it. Also, have you
tried specifically allowing the VNC executeable in the firewall, even if
disabled?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Collier Hill
Sent: Tuesday, September 27, 2005 4:07 PM
To: vnc-list@realvnc.com
Subject: VNC connection closed w/ error 10055


I have seen a couple of references to this issue in previous posts, but see
no resolution posted. So, here is my problem.
 configuration:
VNC Server 4.1.1 for Windows on Windows 2000 Pro
VNC Client 4.1.1 for Windows on Windows XP Pro
 I start the VNC client on XP and successfully authenticate and connect to
the VNC server. The connection seems to function properly for 1 - 5 minutes.
Then the connection is automatically closed with the following error
message:
 VNC Viewer : Question
Unable to wait for socket data: An operation on a socket could not be
performed because the system lacked sufficient buffer space or because a
queue was full. (10055)
Do you wish to attempt to reconnect to ? Yes/No
 Any attempts to click "Yes" just porduce the same error message. If I say
"No", I can reconnect and get the exact same behavior.
 Thanks in advance for any thoughts.
___
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