The file/database/options UnifiedLogonAllowed works fine sometimes. But occasionally, it will stop authenticating with NT and will ask for the Navision User ID and password (which is not synchronized automatically with NT). This behavior will continue until the Navision “Financials Server” database service is stopped, then started. Why and what can be done to prevent this problem?
I encountered the same problem with a 2.00c and tracked it down as follows: using a client on the server computer and connecting to a local database with no unified login breaks it for the former working database too. This can be reproduced. As you said, only restarting the service helps. It seems as if the unified login is changed globally for the computer (registry?, .zup?) and not on an individual database basis. I haven’t verified these possibilities in depth. Solution: don’t use a client directly on the server. Since then, everything is OK. Bye, Torsten