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 7/2008(R2) ELM Server:

  • Firewall On Windows 7/2008(R2) ELM Server:

1.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow the ELM Enterprise Manager executable located by default c:\Program Files\ELM Enterprise Manager\EEMSVR.exe.
2.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow access to TCP port 135.

  • Firewall On Windows 7/2008(R2) client:

1.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow the program Microsoft Management Console, located by default %systemroot%\System32\mmc.exe

Allow Remote ELM Advisor to the ELM Server:

  • Firewall On Windows 7/2008(R2) ELM Server:

1.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow the ELM Enterprise Manager executable located by default c:\Program Files\ELM Enterprise Manager\EEMSVR.exe.

  • Firewall On Windows 7/2008(R2) client:

1.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow the ELM Advisor executable located by default c:\Program Files\ELM Enterprise Manager\ELM.Advisor.exe.

2.Retest the ELM advisor

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

  • Firewall On Windows 7/2008(R2) client:

1.In the Windows firewall settings, “Inbound Rules”, enable:

-File and Printer Sharing (Echo Request – ICMPv4-In)
-Distributed Transaction Coordinator (RPC)
-File and Printer Sharing (NB-Name-In)
-File and Printer Sharing (NB-Session-In)
2.In the Windows firewall settings, “Inbound Rules”, create a “New Rule” to allow access to the TNTagent default TCP port 1253.

Revision:  1.0

Last Modified:  12/13/2010

Last Reviewed:  12/13/2010

Article Type:  Fix