I just wanted to add my name to the list as someone having the exact
same
problems listed in this complaint. This has been a big burden for me
as
I've been trying to roll this out to over 2000 users, but can't
because of
this major problem. Please work on this one Novell!!!

Ryan


>
> We continue to have trouble with the newest (3.70x and 3.70y)

aclcheck.nlm
> that were in the beta and full release of bm37sp1. After working

properly
> with the n2h2 box for a few hours or so, the aclcheck.nlm stops
> communicating with the n2h2 system (linux). We have patched to the


newest
> patches as suggested on both systems, plenty of RAM, P IV HP TC 2110


> server, NW6, and so on. We have also tried diff network cards etc.

to
> verify that connectivity is not the issue (also, a ping between the


> bordermanager and n2h2 system shows no loss)
>
> Appears that a query to the n2h2 box gets stuck and the only fix is

to
> unload proxy, proxycfg, and aclcheck (which abends the server 20

times
or
> so). Loading proxy then gets things working again.
>
> We have back-rev'd to the Sept. version of aclcheck.nlm and so far

its
> working OK. But, we don't want to keep using that version since it

will
> allow users to access sites that should be filtered if the n2h2

system
is
> not available.
>
> Any new beta or full releases of aclcheck.nlm coming out soon? Or

other
> suggestions?
>
> When its working, it sure is a nice product and sooooo easy to

control
> access per account etc....
>
>
>