Products Affected

All ELM Products 5.x and 6.x

Considerations

  • Service Agent, and/or ELM Advisor, and/or ELM Console installed separately from the ELM Server.
  • Windows Firewall is on both remote computer and ELM server, or just on the ELM Server, or just on the remote computer.
  • The service agent will need to have ports open to communicate with the ELM server, refer to the Troubleshooting Service Agent Installation KBA.

Symptoms

  1. Only during a 5.x manual service agent installation, when attempting to authenticate with the ELM Server, an Unknown Username or Password error is presented.
  2. ELM advisor displays error when tested:
    Test failed on COM Exception unable to connect to the server. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
  3. Only during a 5.x service agent push from the ELM Console, a Connect As dialogue box presents itself to authenticate to the client, when entering valid credentials an error Error connecting to \\\Admin$ box is displayed.

Resolution

Allow Remote ELM Console Access to the ELM Server:

•Firewall On Windows XP/2003(R2) ELM Server:

  1. In the Windows firewall settings, on the “General” tab, ensure that the Don’t allow exceptions isn’t checked.
  2. In the Windows firewall settings, on the “Exceptions” tab, add the following TCP ports to include: 135 and 3584.
  3. In the Windows firewall settings, on the “Exceptions” tab, add the program ELM Server, located default c:\Program Files\ELM Enterprise Manager\EEMSVR.exe

•Firewall On Windows XP/2003(R2) client:

  1. In the Windows firewall settings, on the “General” tab, ensure that the Don’t allow exceptions isn’t checked.
  2. In the Windows firewall settings, on the “Exceptions” tab, add the following TCP port to include: 135.
  3. In the Windows firewall settings, on the “Exceptions” tab, add the program Microsoft Management Console, located by default %systemroot%\mmc.exe

Allow Remote ELM Advisor to the ELM Server:

•Firewall On Windows XP/2003(R2) ELM Server:

  1. In the Windows firewall settings, on the “General” tab, ensure that the Don’t allow exceptions isn’t checked.
  2. In the Windows firewall settings, on the “Exceptions” tab, add the following TCP port to include: 135 and 3584.

•Firewall On Windows XP/2003(R2) client:

  1. In the Windows firewall settings, on the “Exceptions” tab, “Add Program” which will be the ELM Advisor executable located default c:\Program Files\ELM Enterprise Manager\ELM.Advisor.exe.
  2. Add TCP port 135 to the port exceptions list.
  3. Retest the ELM advisor

Deploy Agent(s) From the ELM Console to the Client:

•Firewall On Windows XP/2003(R2) client:

  1. In the Windows firewall settings, on the “Exceptions” tab, Add File and Printer Sharing.Note: Only for service agents, this can be unchecked after the intial install.
  2. Add TCP port 135 to the port exceptions list.
  3. Add TNTAgent default TCP port 1253 to the port exceptions list. Note: Only for service agents

Revision: 1.1

Last Modified:  12/6/2010

Last Reviewed: 12/6/2010

Article Type: Fix