Hello Scott,

now it works. NMAS 2.3.5.2 has fixed the problem. Now I get a access
accepted message.

Many thanks for your help.

Best regards.
Boert

Interesting... If this error is happening in NMAS.NLM, then it's
happening
very early in the authentication process. I was expecting to see more
detail
in the log.

Which version of NMAS.NLM are you running? This problem might be fixed
in
NMAS 2.3.6. This error has been reported in some environments when
NMAS has
to go to another server to process the authentication because the user
does
not exist in a local writeable replica. I'm not sure if NMAS 2.3.6 has
been
posted for download yet. If you don't see it on the support site, then
you'll have to call support to get it.

It would be helpful to see one more (hopefully final) trace file. I'd
like
to have you run DSTrace with the +NMAS, +AREQ, +RSLV, and +VCLN
switches.
This should tell me what NMAS.NLM or BAUTHPXY.NLM was trying to read
from
eDirectory when it received the error.