When you try to log in to the nworks Web UI you receive the following error:
No connection could be made because the target machine actively refused it x.x.x.x:8084
See a screenshot example:
There is a variety of reasons that can cause this issue, but the gist of the error is that you either do not have sufficient permissions, or permissions/access/settings are corrupt.
Make sure that nWorks Enterprise Manager Windows service is started.
Open the Start menu and run services.msc in the command prompt. Locate nWorks Enterprise Manager service in the list. If the service is not started, right-click it and choose Start from the menu.
Verify that the domain account that you use to access the nworks Web UI is a member of the local nWorks Enterprise Manager accounts group and a member of the local Administrators group.
Verify that the local Administrators group has Full Control access for the nworks Enterprise Manager Configuration website in IIS.
To check permissions, open the IIS Manager and in the Connections pane go to ServerName > Sites > nworks Enterprise Manager Configuration. Right-click the nworks Enterprise Manager Configuration node and choose Edit Permissions from the menu. Open the Security tab and check permissions for the local Administrators group. Change permissions if necessary and propagate them to all child nodes. These steps also apply for IIS 7.
As a last resort, you can remove saved nworks data to reset any internal data sources that could contain saved credentials. To do this, rename the maindb.xml file and restart nWorks Enterprise Manager Windows service. After that, you will need to add connections to VMware servers and configure monitoring settings in the nworks Enterprise Manager once again.
The maindb.xml file is located in the following directory:
Windows 2003: C:\Documents and Settings\All Users\Application Data\nworks\Management Center\maindb.xml
Windows 2008: C:\ProgramData\nworks\Management Center\maindb.xml