The easy way (at least for me) to see what is happening is to use
filter debug and check for filtered tcp and possibly udp packets.
However, this can be risky on production servers with a lot of traffic.
(Don't run it any longer than absolutely needed, especially if a lot of
filtered packets show up). A safer option is to use pktscan.nlm on the
server to capture packets and see what requests are being made from the
source address of interest.
You also need NAT working for your filtering to work here. And routing
enabled on the BM server.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***