Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?

• Subject: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
• From: "Lawrence Frewin of Accommodation.com" <Lawrence@xxxxxxxxxxxxxxxxx>
• Date: Tue, 1 May 2001 17:10:56 +0100
• List-id: Mailing list for users to address network security on Cobalt products. <cobalt-security.list.cobalt.com>

• Follow-Ups:
  • Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
    • From: Dan

• References:
  • [cobalt-security] RaQ3-All-Kernel-4.0.1-2.216C24III.pkg
    • From: Fred
  • [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
    • From: Dan

• Prev by Date: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
• Next by Date: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
• Previous by thread: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
• Next by thread: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
• Sun Cobalt Security Message Index
• Sun Cobalt Security Thread Index