Hi All,

I've got a really weird situation happening here. I've installed a
BM3.7
system on top of NW6SP2. It seems that the filters.cfg file never
gets set
up properly. I have gone through the manual configuration attempt
using
BRDCFG to reinitialize the filters, but it didn't seem to help. I'veattached the FILTERS.CFG file.

I wonder if there might be a problem with the way that the server
itself was
installed. The client installed the server into to tree as a NW6
server,
but set the IP address wrong. Rather than change the IP address, we
decided
to just remove it from the tree. I cleaned up the tree, getting rid
of the
left over NDS objects, like the NLSLSP,security, and backup queue
objects.
When I reinstalled the server into the tree (using the same server
name), I
did get an error. "Warning: eMFrame failed to associate initial roles
with
..admin.XXXX. Associations can be made after installation is
complete". I
didn't think too much about this at the time, but I'm now wondering if
this
might be causing the problem. I did not make any new associations,
since
they will probably not be using iManager. I don't know if this was
caused
by installing a server with the same name as one that was removed from
the
tree.

Anyway, I installed BM3.7 on the server and everything seemed to be
going
just fine, however, when I went in to FILCFG to set up some
exceptions, I
noticed the the filter list was nearly empty (see below). None of the

expected proxy or VPN exceptions were there. I followed the
instructions in
TID 10080403 to try to reset the default filters, but it didn't help.Another thing that I noticed was the ConsoleOne showed the
NBMRuleContainer
as a generic object, and it was empty. NWAdmin32 shows it as an
unknown
object. The BM server is responding to quite a few port requests, so
this
is definately a problem.

Does anyone have any ideas here? In a worst case scenario, I'm
thinking
that maybe I need to remove the server from the tree, then do another,
fresh
install, this time using a different server name. But I don't really
know
if this is really going to fix the problem.

Thanks in advance,

Mark


# FILE: FILTERS.CFG
#
# Filter Database. This file is maintained by the Filter Services NLM.

# *** IMPORTANT ***
# TAMPERING WITH THIS FILE MAY CAUSE SEVERE MALFUNCTIONING OF THE
SYSTEM.
#-------------------------------------------------------------------------


VERSION 1.3

GLOBAL-IP-LOG DISABLED
GLOBAL-IPX-LOG DISABLED

IP-NOT-MATCHING-FLT-EXCEPTION-LIST-LOG DISABLED
IPX-NOT-MATCHING-FLT-EXCEPTION-LIST-LOG DISABLED


PACKET-FILTER-LIST IP, ENABLED, DENY

PACKET-FILTER-LIST IPX, ENABLED, DENY FILTER ENABLED NOLOG,
INTRFACE:<Any>,
IPX:pkt_type=FF socket=FFFF
srcsocket=FFFF, INTRFACE:N100_2_EII, Added by BRDCFG to block all IPXpackets.
FILTER ENABLED NOLOG, INTRFACE:N100_2_EII, IPX:pkt_type=FF
socket=FFFF
srcsocket=FFFF, INTRFACE:<Any>, Added by BRDCFG to block all IPX
packets.

SERVICE-FILTER-LIST ADVERTISE, APPLETLK, DISABLED, DENY

SERVICE-FILTER-LIST ADVERTISE, IPX, ENABLED, DENY FILTER ENABLED
NOLOG,
IPXSAP:FFFF, *, GROUP:<ANY>, INTRFACE:N100_2_EII,
Added by BRDCFG to block all IPX SAP traffic.

SERVICE-FILTER-LIST ACCEPT, IPX, ENABLED, DENY FILTER ENABLED NOLOG,
IPXSAP:FFFF, *, GROUP:<ANY>, INTRFACE:N100_2_EII,
Added by BRDCFG to block all IPX SAP traffic.

ROUTE-FILTER-LIST ADVERTISE, APPLETLK, DISABLED, DENY

ROUTE-FILTER-LIST ACCEPT, APPLETLK, DISABLED, DENY

ROUTE-FILTER-LIST ADVERTISE, OSPF, DISABLED, DENY

ROUTE-FILTER-LIST ADVERTISE, EGP, DISABLED, DENY

ROUTE-FILTER-LIST ACCEPT, EGP, DISABLED, DENY

ROUTE-FILTER-LIST ADVERTISE, IP, DISABLED, DENY

ROUTE-FILTER-LIST ACCEPT, IP, DISABLED, DENY

ROUTE-FILTER-LIST ADVERTISE, IPX, ENABLED, DENY FILTER ENABLED
NOLOG,
IPX:00000000/00000000, INTRFACE:N100_2_EII,
<none>, Added by BRDCFG to block all IPX RIP traffic.

ROUTE-FILTER-LIST ACCEPT, IPX, ENABLED, DENY FILTER ENABLED NOLOG,

IPX:00000000/00000000, INTRFACE:N100_2_EII,
<none>, Added by BRDCFG to block all IPX RIP traffic.