Subject: From: Date:

Re: [ECS] Winsock error? Mark Gilmore Tue, 11 Jul 2000 09:53:49 -0400

---

Then I would kill RADMIN, as this is the only
thing you are doing different.
btw, do we need to run both RADMIN AND the ECS server ?
Is this a remote (away from PC) or local connection ?
-- 
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
423-745-0026
Hours: Mon-Sat, 9AM-8PM/EST


Mark Sekelsky wrote:
> 
> This error is back.  We left town on Saturday morning.  Before leaving I did
> a reboot and did not load ACE server meaning all that was running was Win
> 98, ECS and Radmin server.  Accessed ECS via ecs_www twice and received
> maybe four voice messages via postie.  The error came Monday I couldn't
> access the system remotely nor was ECS sending voice messages.  I verified
> that the connection was working by calling my second line and getting a busy
> signal.  I had a neighbor go over to my house and reboot my PC.  After
> rebooting I was able to access again and this is when I found a message log
> packed with those errors.
> 
> Mark S
> 
> -----Original Message-----
> From: Mark Sekelsky <Mark@sekelsky.com>
> To: ecs-list@netbloc.com <ecs-list@netbloc.com>
> Date: Monday, July 10, 2000 4:33 PM
> Subject: Re: [ECS] Winsock error?
> 
> >Actually this is Mark S.  I was at a friends for the weekend and for
> >whatever reason I could receive my accounts but anything sent (even
> replies)
> >went from him.  In any event The PC runs ECS, ACE server and Radmin.  Other
> >than those, nothing else runs.  I am not sure what you mean by a local or
> >remote connection.  I run ecs_www to initiate a dialup connection and after
> >connecting is when the error has occurred.
> >
> >Now since my initial post I have not had this problem.  I should also note
> >that I have been sending my messages via email for about a year or so
> (maybe
> >4 or 5 times) and never had the problem.
> >
> >Mark S
> >
> >-----Original Message-----
> >From: Mark Gilmore <omnip@usit.net>
> >To: ecs-list@netbloc.com <ecs-list@netbloc.com>
> >Date: Monday, July 10, 2000 1:50 PM
> >Subject: Re: [ECS] Winsock error?
> >
> >
> >>Hi Dave,
> >>OK, so much for my theory.
> >>Is there any OTHER Internet-related software that is running ?
> >>Is there anything "unique" about your PC that I should know about ?
> >>Is this a local or remote connection ?
> >>--
> >>Mark Gilmore
> >>Omnipotence (ECS home automation software)
> >>http://www.usit.com/omnip
> >>423-745-0026
> >>Hours: Mon-Sat, 9AM-8PM/EST
> >>
> >>
> >>"Everson, Dave J" wrote:
> >>>
> >>> I don't think so.  The screen I display 99% of the time only has 7 items
> >on
> >>> it and only two of those are likely to change during the course of a
> day.
> >>>
> >>> -----Original Message-----
> >>> From: Mark Gilmore [mailto:omnip@usit.net]
> >>> Sent: Sunday, July 09, 2000 14:35
> >>> To: ecs-list@netbloc.com
> >>> Subject: Re: [ECS] Winsock error?
> >>>
> >>> Mark,
> >>> The WASENOBUFS error means that no buffers are available
> >>> for TCP/IP (Internet) communications.
> >>> The only thing I can think of that could cause this would
> >>> be if you had a LOT of displayed Group-Items which changed
> >>> frequently (which could eventually cause a traffic overload).
> >>> Is this the case ?
> >>> --
> >>> Mark Gilmore
> >>> Omnipotence (ECS home automation software)
> >>> http://www.usit.com/omnip
> >>> 423-745-0026
> >>> Hours: Mon-Sat, 9AM-8PM/EST
> >>>
> >>> Mark Sekelsky wrote:
> >>> >
> >>> > While playing with this web stuff for ECS I occasionally get the
> >following
> >>> > error messages:
> >>> >
> >>> > 0024 O 07/02  8:27 PM:SCK_HOST_ADDR_SD:listen (err#x2747:WSAENOBUFS)
> >>> > (TCP_HOST_CHK)
> >>> > 0025 O 07/02  8:27 PM:SCK_HOST_ADDR_SD:bind (err#x2740:WSAEADDRINUSE)
> >>> > (TCP_HOST_CHK)
> >>> >
> >>> > The first one usually occurs one time.  The second one will occur
> every
> >>> few
> >>> > seconds until I disconnect.  The connection, while appearing active,
> >>> doesn't
> >>> > work when I get these errors.  A reboot fixes the problem.  Anybody
> >have
> >>> any
> >>> > idea what this is, or more importantly how to fix it?
> >>> >
> >>> > Mark S
> >>
> >
> >

---