Troubleshooting connection errors

If you are receiving an HPSUM Connection Error or Discovery Failed messages, follow these main troubleshooting tips.

• Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP address. If it does, it prevents HP Smart Update Manager from connecting to the remote server's share because Windows only allows one connection from a client to a server's share. This can be checked by entering net use at a command prompt. If there is an existing share to the target IP address \admin$ share, delete it and try the installation again.
• Ensure that the target IP address server's admin$ share is accessible. Validate the target server can be accessed by entering net use x: \\<ip_address_or_dns_name>\admin$ for the target server's IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net use x: /d at command prompt.
• Ensure the user ID being used to connect to the target IP address server is part of the administrator's group. If it is not, HP Smart Update Manager blocks installation to the target.
• Ensure WMI is enabled and running on all Windows target servers.
• For Linux, ensure the SSH port is not blocked.
• In some rare cases, external storage enclosures may cause HP Smart Update Manager to report a discovery failure. To resolve this problem, disconnect the external storage until the firmware updates are completed.
• For Linux, ensure that the target server can be contacted through SSH and that the scp command is available to securely send files to the target server.
• Ensure the firewall ports on any routers in the network as documented in the Enabling ports in HP Smart Update Manager section of this document.
• The Symantec End Point Protection product (SEP) blocks HP Smart Update Manager ability to communicate with remote targets if the Network Threat Analysis feature is enabled. Disable this feature while HP Smart Update Manager is in use on the workstation.
• Examine the OpMan.trace, IPScout.trace, OSScout.trace, discagent.trace and discmanager.trace files to determine the cause of the failure. For more information, see Collecting trace directories.