Craig,
Maybe you could shed some light on this for me. My filter exceptionsare configured as follows:

Exception1: allows source port 1024-65535 to dest 51080, with any
source address to only the NetStorage server as dest host (private
address specified)

Exception2: allows response on port 51080 from Netstorage server as
source host (private address) to any dest host at dest port 1024-65535


Exception3: allows source port 1024-65535 to dest 51443, with any
source address to only the NetStorage server as dest host (private
address specified)

Exception4: allows response on port 51443 from Netstorage server as
source host (private address) to any dest host at dest port 1024-65535


Normally this configuration has worked for any service on my private
network that I am making available to the public side. My symptom
with
this configuration is that I get prompted for my authentication
information when I direct my browser to the appropriate address,
however, when I provide the authentication information the process
never
completes. After a period of time the authentication box pops back up

in the browser, almost as if the process has timed out. If I unload
IPFLT, IPXFLT, and FILTSRV the authentication process completes fine
and
I am presented with the NetStorage page as I would expect.

Am I misunderstanding the filter exception configuration for this
service?

Thank you in advance,
Aaron DiBari


Craig Johnson wrote:

> I think it uses LDAP only from within the server, and then usually
> to itself. LDAP doesn't go from client to server, for sure.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and books on
> BorderManager, go to http://nscsysop.hypermart.net ***