Security Basics mailing list archives
Re: Blocking port 4444 for W32.Blaster.Worm
From: chort <chort () amaunetsgothique com>
Date: 20 Aug 2003 09:13:08 -0700
On Wed, 2003-08-20 at 06:23, Brett Munhall wrote:
In-Reply-To: <OF4867F7BA.C7CC7A58-ON48256D81.000036BA-48256D81.00003EE1 () cityofperth wa gov au> I have a quick question. If I block 4444 on the firewall or router and a workstation uses 4444 for web traffic and it is blocked. Will the workstation lock up or does it just retransmit the traffic on another port? Thanks, Brett
In my experience the connection will time-out. If the client was a web browser, they would need to hit refresh or click the link again. If it's e-mail, hit send & receive again, etc. In recent history (last few years) I haven't seen a client crash because a connection timed-out (disclaimer, I don't pretend to have witnessed the effects of a time-out on every possible client on every possible OS. Some clients might be lame and not handle the condition gracefully). -- Brian Keefer --------------------------------------------------------------------------- ----------------------------------------------------------------------------
Current thread:
- Blocking port 4444 for W32.Blaster.Worm Steven_Paice (Aug 12)
- RE: Blocking port 4444 for W32.Blaster.Worm Michael LaSalvia (Aug 12)
- RE: Blocking port 4444 for W32.Blaster.Worm Steven_Paice (Aug 13)
- <Possible follow-ups>
- RE: Blocking port 4444 for W32.Blaster.Worm CHRIS GRABENSTEIN (Aug 12)
- Re: Blocking port 4444 for W32.Blaster.Worm Brett Munhall (Aug 20)
- Re: Blocking port 4444 for W32.Blaster.Worm chort (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm David Gillett (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm Dave Killion (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm Michael LaSalvia (Aug 12)