Managing NerveCenter
-
Managing NerveCenter Security - Troubleshooting: Managing NerveCenter Security -
The following list contains some common security problems NerveCenter users face.
Problem: Users are not members of the appropriate NerveCenter user group on the server machine (ncadmins or ncusers on UNIX or NerveCenter Admins or NerveCenter Users on Windows).
Solution: Check group membership. If users are not members of the appropriate groups, add them. Remember that on Windows, users must log out for changes to take place.
See Managing Security on UNIX or Managing Security on Windows.
Problem: Users do not have a valid Windows account.
Solution: Check the user account. See your Windows documentation for more details.
Problem: The server is not running.
See Chapter 3, Running the NerveCenter Server
Problem: ncadmins and ncusers have been created on a NerveCenter host that is also an NIS client.
Solution: When running NerveCenter on an NIS client, the groups ncadmins and ncusers must reside on the NIS Master. Local NerveCenter groups are ignored when the local system is an NIS client. Authentication is done on the NIS Master server. When running in an NIS environment, make sure the NerveCenter groups are defined on the NIS master. The user community members must be members of those groups as well.
Problem: NerveCenter was installed on Windows without security.
Solution: Reinstall the NerveCenter server with security.
Problem: Users who are members of ncusers (UNIX) or NerveCenter Users (Windows) can only monitor and reset alarms. To be able to modify NerveCenter objects, users must be members of ncadmins (UNIX) or NerveCenter Admins (Windows).
Solution: Add users to the appropriate groups.
See Managing Security on UNIX or Managing Security on Windows.
Problem: User does not have the appropriate permissions on the Web server.
Solution: Give the user access to the Web server. See your Web server documentation for details.
Adding Users to a NerveCenter Installed on a Windows Workstation or Server | Managing NerveCenter Alarm Actions |
29 July 2003 |