Re: Norton NPF - I get the same problem.
From: Joseph V. Morris (jvmorris_at_erols.com)
Date: 07/19/03
- Next message: ray: "NAT question"
- Previous message: Eirik Seim: "Re: Linksys router as Firewall"
- In reply to: Jamie: "Re: Norton NPF - I get the same problem."
- Next in thread: Eric: "Re: Norton NPF - I get the same problem."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 19 Jul 2003 11:05:07 -0400
Jamie,
Sorry, been busy.
That sounds like the classic rules corruption problem that has been
occasionally found in all released versions of NIS/NPF. As far as I know,
Symantec has not conclusively established how this occurs. Of course, most
reported instances have gone the other way and are even more dangerous --
they are a PERMIT everything rule present in the system-wide rules settings.
Do you recall the label that was assigned to this rule when you found it?
That could be an important bit of information.
Also, had you run a registry cleaner sometime shortly before this problem
occurred?
Had you installed updates of any of your applications shortly before this
problem occurred?
Just trying to find a bit of information that might be helpful to Symantec
in looking for a resolution.
--
Regards,
Joseph V. Morris
jvmorris@erols.com
"Jamie" <Necroflash@Gothicbtopenworld.com> wrote in message
news:bfbf8b$suk$1@titan.btinternet.com...
. . . .
> Have just checked the systemwide settings under configure systemwide
> settings and discovered a rule that was not there before the last update
> effectively blocking all TCP/UDP from any computer IN/OUT. Have removed
> this rule and everything is back to normal.
- Next message: ray: "NAT question"
- Previous message: Eirik Seim: "Re: Linksys router as Firewall"
- In reply to: Jamie: "Re: Norton NPF - I get the same problem."
- Next in thread: Eric: "Re: Norton NPF - I get the same problem."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
