[Symantec] NNTP = TCP now?
From: Jim Heckman (wnzrfeurpxzna_at_lnubb.pbz.invalid)
Date: 04/28/05
- Next message: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Previous message: Will: "Proper Way to Pass ICMP Through Firewall-1?"
- Next in thread: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Reply: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Reply: Ian Kenefick: "Re: [Symantec] NNTP = TCP now?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 28 Apr 2005 06:46:17 GMT
Since I downloaded and installed the new version of Symantec
Redirector today (27 April), Personal Firewall (a component of
Norton Internet Security 2002) has been treating incoming NNTP
as if it were TCP. I used to have a rule blocking all incoming
TCP, but now I've had to remove it to let NNTP in, so now I get
annoying pop-ups every so often asking me if I want to permit or
block an incoming TCP connection. Aargh!
Anyone else having this problem? Any ideas what to do about it?
-- Jim Heckman
- Next message: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Previous message: Will: "Proper Way to Pass ICMP Through Firewall-1?"
- Next in thread: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Reply: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Reply: Ian Kenefick: "Re: [Symantec] NNTP = TCP now?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
