Domino 12.0.2 FP5, Nomad 1.0.15 on MS Server 2022
Normally a common name is all that is required to allow Nomad to look up in the NAB to get the fully qualified user name, home server and connect to the ID Vault.
I have a couple of users who can only log on using their abbreviated name. Common name does not work - it attempts to connect to server “None” and of course fails. Both person records have both fully qualified and common names listed in the FullName field, and the server name correct in the MailServer field.
What might I be missing?
AB
Hello Andrew,
Please check and compare person document for working user and affected user for any mismatch.
When it fails, what error is being reported?
Thanks and Regards
Niraj V Jani
A support case is probably best to let us safely look at the logs from your server.
You can enable some lower level logging in nomad-config.yml (in the data directory):
DEBUG: “nomad=info,nomad::domino=trace,rocket=error”
and restart nomad server. This will spit out a lot of information, including around user lookups.
If you cannot determine the issue yourself, you can always open a support case and we can take a look.
I have checked the person documents, as set out in my OP. I can see no difference between working document (mine) and non-working (theirs). I am looking for something more specific (a field other than the ones I have mentioned as checked) or something outside the person document I might look at.
The error reported is simply that setup failed, but it shows (both in the UI and in the console log) that the server it is attempting to connect to is “None”. The question is why is it trying to do that when the correct server is listed in the Mail Server field.
Thank you. I will try that. The resulting debug information is written where? To the server console or somewhere else?
It should appear on the Domino server console.
Maybe you have more than one person record with the same Common Name? Check all directories if using Directory Assistance.