[Symantec] NNTP = TCP now?

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?

Reply to
Jim Heckman
Loading thread data ...

NNTP (119/tcp news service) uses TCP. NTP (123/udp Network Time Protocol) uses UDP. So I think everything is alright. Just open the 119/tcp port.

Regards.

Reply to
Jose Maria Lopez Hernandez

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

Regards, Ian Kenefick

formatting link

Reply to
Ian Kenefick

Ah yes, I see that now. Thanks. Interesting though that I used to be able to block TCP on all ports without affecting NNTP. :-/

Reply to
Jim Heckman

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.