Re: [Symantec] NNTP = TCP now?
From: Jim Heckman (wnzrfeurpxzna_at_lnubb.pbz.invalid)
Date: 04/29/05
- Next message: Wolfgang Zweimueller: "Re: Proper Way to Pass ICMP Through Firewall-1?"
- Previous message: Will: "Re: Proper Way to Pass ICMP Through Firewall-1?"
- In reply to: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Next in thread: Ian Kenefick: "Re: [Symantec] NNTP = TCP now?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 29 Apr 2005 15:55:30 GMT
On 28-Apr-2005, Jose Maria Lopez Hernandez <jkerouac@bgsec.com>
wrote in message <4270963e_1@x-privat.org>:
> Jim Heckman 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?
>
> 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.
Ah yes, I see that now. Thanks. Interesting though that I used to be
able to block TCP on all ports without affecting NNTP. :-/
-- Jim Heckman
- Next message: Wolfgang Zweimueller: "Re: Proper Way to Pass ICMP Through Firewall-1?"
- Previous message: Will: "Re: Proper Way to Pass ICMP Through Firewall-1?"
- In reply to: Jose Maria Lopez Hernandez: "Re: [Symantec] NNTP = TCP now?"
- Next in thread: Ian Kenefick: "Re: [Symantec] NNTP = TCP now?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|