Re: [Symantec] NNTP = TCP now?

From: Ian Kenefick (ian_kenefick_at_eircom.net)
Date: 04/29/05


Date: Fri, 29 Apr 2005 01:30:17 +0100

On Thu, 28 Apr 2005 06:46:17 GMT, "Jim Heckman"
<wnzrfeurpxzna@lnubb.pbz.invalid> wrote:

>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?

No, but I think you mis understand NNTP and TCP.

Regards,
Ian Kenefick
http://antivirus.ik-cs.com



Relevant Pages

  • Re: [Symantec] NNTP = TCP now?
    ... > Norton Internet Security 2002) has been treating incoming NNTP ... > as if it were TCP. ... The only people for me are the mad ones -- the ones who are mad to live, ...
    (comp.security.firewalls)
  • Re: Charmed life ...
    ... And before you say 'oh, well, I meant the Internet', ... Usenet is older than that, ... first transfered over NNTP, a TCP protocol, 1985. ...
    (uk.rec.cycling)
  • Re: NNTP problem
    ... nntp uses tcp 119 ... firewall hardware you use. ... > I tried to add msnews group to my outlook express. ... > want to open NNTP port if it is close. ...
    (microsoft.public.windowsxp.security_admin)
  • [Symantec] NNTP = TCP now?
    ... Norton Internet Security 2002) has been treating incoming NNTP ... TCP, but now I've had to remove it to let NNTP in, so now I get ...
    (comp.security.firewalls)