[prev in list] [next in list] [prev in thread] [next in thread]
List: patchmanagement
Subject: RE: Event ID: 4226
From: "Chad Fisette" <Chad_Fisette () SWN ! COM>
Date: 2009-09-10 19:02:55
Message-ID: D0926FF6D4BC394EB0CEFA57C1C706AA02321026 () HOU-MAILCLUSTER ! SWN ! COM
[Download RAW message or body]
I found I was having the issue before the updates. Thanks for all the tips.
-----Original Message-----
From: Julian Harper [mailto:Julian.Harper@Laytons.co.uk]
Sent: Thursday, September 10, 2009 10:58 AM
To: Patch Management Mailing List
Subject: RE: Event ID: 4226
It's a semi common error with Windows XP clients if you're running any network \
services on it, such as P2P programs, I wouldn't be too concerned.
Julian Harper
IT Manager
The Jeroboams Group
-----Original Message-----
From: Susan Bradley [mailto:sbradcpa@pacbell.net]
Sent: 09 September 2009 19:01
To: Patch Management Mailing List
Subject: Re: Event ID: 4226
What does the update do?
The update addresses this vulnerability by dropping existing TCP connections \
adaptively and limiting the number of new TCP connections until system resources are \
restored.
I would expect that actually.
Chad Fisette wrote:
> Did anyone get this error after applying the latest round of patches?
>
> Event Type: Warning
> Event Source: Tcpip
> Event Category: None
> Event ID: 4226
> Date: 9/9/2009
> Time: 9:07:34 AM
> User: N/A
> Computer:
> Description:
> TCP/IP has reached the security limit imposed on the number of concurrent TCP \
> connect attempts.
> For more information, see Help and Support Center at \
> http://go.microsoft.com/fwlink/events.asp. Data:
> 0000: 00 00 00 00 01 00 54 00 ......T.
> 0008: 00 00 00 00 82 10 00 80 ....
> 0010: 01 00 00 00 00 00 00 00 ........
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........
>
>
>
>
> -----Original Message-----
> From: Doug Neal [mailto:dugn@microsoft.com]
> Sent: Tuesday, September 08, 2009 4:00 PM
> To: Patch Management Mailing List
> Subject: RE: Microsoft Says No Again To Windows XP Update CDs - Security Watch:
>
> http://catalog.update.microsoft.com/ does a lot of this already. Just build \
> criteria (platform, KB number, etc.) and all related patches can be dumped into an \
> auto-built directory structure on your local machine.
> doug neal
> Microsoft Update (MU)
> Microsoft Baseline Security Analyzer (MBSA)
>
> From: Bob Schatz [mailto:bschatz@us.ibm.com]
> Sent: Tuesday, September 08, 2009 12:00 PM
> To: Patch Management Mailing List
> Subject: Re: Microsoft Says No Again To Windows XP Update CDs - Security Watch:
>
>
>
>
> You're talking about Microsoft and patches. By the time they'd put out a CD, it \
> would be outdated. FTP or web site makes the most sense.
> From:
> Eric <ews@tellurian.net>
> To:
> "Patch Management Mailing List"
> <patchmanagement@listserv.patchmanagement.org>
> Date:
> 09/08/2009 12:33 PM
> Subject:
> Re: Microsoft Says No Again To Windows XP Update CDs - Security Watch:
>
> ________________________________________
>
>
>
> "Microsoft should just put all the critical updates on an FTP server
> in a directory somewhere."
> This is how it was done circa 1997 - One folder per OS, then folders
> for each SP, and within each SP folder, subfolders for each patch.
> Worked very well.
>
> I believe the major objection to the patch CD is the method of
> obtaining the patches. Microsoft doesn't like to have any of their
> patches rehosted at a third-party site. Whether that's for legal
> reasons or simply to help ensure that those updates don't go out of
> date (replaced by newer patches on MS site that don't get updated on
> third party site), i don't know.
>
> As long as the actual patch binaries are downloaded from the Microsoft
> website and put to your own disk for your own use, that should be fine.
> Perhaps someone could build a tool that contains all the patches and
> their download URLs for each OS. Then, the end-user could run the
> tool on an Internet-connected machine, select the OSes and apps (and
> languages) that they're interested in, and the tool would download all
> the appropriate patches and burn them to disk. I don't believe MS
> would have a problem with that because the patches themselves are
> coming directly from MS. (this assumes that you're using the disk for
> your own corporate use, not rehosting it again for others).
>
> --eric schultze
>
>
> Ben Scott wrote:
>
> > On Fri, Sep 4, 2009 at 7:11 AM, Steve
> > Shockley<steve.shockley@shockley.net> wrote:
> >
> >
> > > > Microsoft Says No Again To Windows XP Update CDs - Security Watch:
> > > >
> > > >
> > > Huh? What about http://support.microsoft.com/kb/913086?
> > >
> > >
> > The problem with that distribution is that it's oriented the wrong
> > way. Each image is all updates for all products for all languages
> > *in a given month*. So to (for example) get all updates needed to
> > bring a new Win XP English SP3 install to current, you have to
> > download *TENS OF GIGABYTES* of stuff you don't want, and carry around tens of \
> > discs.
> > Microsoft should just put all the critical updates on an FTP server
> > in a directory somewhere.
> >
> > -- Ben
> >
> > ---
> > When posting or replying to messages on this list, please send all
> > emails in plain text format. HTML formatted messages will not be accepted.
> >
> > PatchManagement.org is hosted by Shavlik Technologies
> >
> > To unsubscribe send a blank email to
> > leave-patchmanagement@patchmanagement.org
> > If you are unable to unsubscribe via this email address, please email
> > owner-patchmanagement@patchmanagement.org
> >
> >
> >
> >
>
>
>
> ---
> When posting or replying to messages on this list, please send all
> emails in plain text format. HTML formatted messages will not be accepted.
>
> PatchManagement.org is hosted by Shavlik Technologies
>
> To unsubscribe send a blank email to
> leave-patchmanagement@patchmanagement.org
> If you are unable to unsubscribe via this email address, please email
> owner-patchmanagement@patchmanagement.org
>
>
>
> ---
> When posting or replying to messages on this list, please send all
> emails in plain text format. HTML formatted messages will not be accepted.
>
> PatchManagement.org is hosted by Shavlik Technologies
>
> To unsubscribe send a blank email to
> leave-patchmanagement@patchmanagement.org
> If you are unable to unsubscribe via this email address, please email
> owner-patchmanagement@patchmanagement.org
>
>
>
> Notice: This e-mail may contain privileged and/or confidential
> information and is intended only for the addressee. If you are not the
> addressee or the person responsible for delivering it to the
> addressee, you may not copy or distribute this communication to anyone
> else. If you received this communication in error, please notify us
> immediately by telephone or return e-mail and promptly delete the
> original message from your system.
>
> ---
> When posting or replying to messages on this list, please send all
> emails in plain text format. HTML formatted messages will not be accepted.
>
> PatchManagement.org is hosted by Shavlik Technologies
>
> To unsubscribe send a blank email to
> leave-patchmanagement@patchmanagement.org
> If you are unable to unsubscribe via this email address, please email
> owner-patchmanagement@patchmanagement.org
>
>
>
---
When posting or replying to messages on this list, please send all emails in plain \
text format. HTML formatted messages will not be accepted.
PatchManagement.org is hosted by Shavlik Technologies
To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email \
owner-patchmanagement@patchmanagement.org
---
When posting or replying to messages on this list, please send all
emails in plain text format. HTML formatted messages will not be accepted.
PatchManagement.org is hosted by Shavlik Technologies
To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org
Notice: This e-mail may contain privileged and/or confidential
information and is intended only for the addressee. If you are not the
addressee or the person responsible for delivering it to the addressee,
you may not copy or distribute this communication to anyone else. If you
received this communication in error, please notify us immediately by
telephone or return e-mail and promptly delete the original message from
your system.
---
When posting or replying to messages on this list, please send all
emails in plain text format. HTML formatted messages will not be accepted.
PatchManagement.org is hosted by Shavlik Technologies
To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic