We had an incident a while back where a server was installed in the
tree,
and it also created a LPO in the security container. We already had
BorderManager (Radius) installed in the tree, and all Radius
authentication
stopped until we deleted the LPO.
I've come across a TID that addresses the -603 error we were getting,
which
states to run admattrs.nlm to add the correct properties to the LPO.
Then
configure the LPO with an access rule for Radius.
I've also found another TID that is an update to adm.nlm on the
server,
which apparently allows Radius to continue to function while the LPO
object
is in the tree, and no access rules are setup.

Which route should I take? We are planning on using the LPO down the
road
for VPN use, so we will need a rule for that when the time comes, but
if I
can update adm.nlm and have the LPO exist without a specific rule forRadius, should I try that instead?

thanks,
Dan