[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] Problems with Websense 4.2 for FW1
Thats the way our firewall-1 server itself used to be. It ran for a while, then started failling once a week, and then every day and then multiple times per day. We switched out hardware, same thing. We striped the NT system to bare bones and that helped, but the greatest help was to minimize logging and make sure you have your OEM/Hardware manufactures IDE or SCSI drivers loaded and NOT the generic ones NT provides. For some reason our box would just freeze, but after using the manufactures drivers and litterally disabling everything non essential it hasn't burped since. But i'd bet your drive/disk system on that box is being loaded if you are indeed logging everything with websense. -----Original Message----- From: Clishe, Jason [mailto:[email protected]] Sent: Tuesday, September 19, 2000 1:46 PM To: '[email protected]' Subject: [FW1] Problems with Websense 4.2 for FW1 This isn't so much an FW-1 issue as it is a Websense issue. I've got FW-1 version 4.0 running on NT 4, SP5. I also have a Websense 4.2 box running on Windows 2000 Server, SP1. Everything was going fine for almost 2 months, then we had a situation where none of my users could get to the Internet. After trying numerous things, rebooting the Websense box fixed the problem. I didn't think too much of it at the time. About 3 days later the same thing happened again, and rebooting Websense resolved the problem. From there it started to get more frequent; every other day, every day, twice a day, and now I'm up to about 3 or 4 times a day that we lose access to the Internet, and rebooting Websense fixes the problem. I have talked to 2 colleagues at other companies that use Websense 4.2 for FW-1, and they both report the same problems (they are both running Websense on NT 4, as opposed to my Windows 2000 box, so it doesn't appear to relate to Win2K). Apparently Websense is aware of the issue and working on a fix, but I was wondering if anyone else has had the problem and developed a work-around (besides turning off Websense!) One of my colleagues went so far as to move Websense to a fresh NT install on a different server. It worked flawlessly for several weeks, then the problems came back on the same increasingly frequent schedule. Thank you Jason Clishe ============================================================================ ==== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ============================================================================ ==== ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|