Niagara AX - Niagara 4 LocalHost - When A Platform Connection Rejects Known Good User Names and Passwords, or the host has no password.

Niagara AX - Niagara 4 LocalHost - When A Platform Connection Rejects Known Good User Names and Passwords, or the host has no password.

 

Problem:
Sometimes software problems have prevented users from opening Local Host Platform connections to their Windows machines using Windows user names and passwords. This prevented them from using tools like Station Director and from performing software upgrades. 
 
Solution:
Sometimes authentication will fail because a local account exists on the machine, and another account with the same name and a different password exists in the machine's domain. This sort of ambiguity can be resolved by prefixing the user name, for example using "GREENMACHINE\jimmy" or "ACMEDOMAIN\jimmy" instead of just "jimmy". When the login is rejected because of an actual software problem, though, it may be necessary to work around the problem by configuring the Niagara service to stop using native authentication until it can be upgraded with a fix.
 
Steps:
• Stop the "Niagara" service using the "Services" control panel applet, or using the "net stop niagara" command in a DOS console.
• Use a text editor to open the {niagara install root}/daemon/daemon.properties file and set the following three properties: 
 

authtype=digest
user=myusername
password=mypassword

 
Don't be concerned that the password is entered into the file unencrypted; the Niagara service will re-save the file with the password encrypted the next time it starts. • Start the "Niagara" service again.

Add Feedback