Problem: Sometimes one or more clients may get failure messages when they try to log into a Broker or Agent.
If the client was able to connect before then usually something has changed within their network
that now prohibits remote machine connection. This cause can be related to new machine installations
where their DNS servers do not resolve the new host names, or a firewall between the client and server
or agent blocks port usage.
CA Support usually first asks the customers can you use ping and use telnet to test network connectivity
to the remote machine. If either of these fails connection then the customer should engage their network
administrator or firewall admin to resolve the connection issue.
In many cases, the client does not have access to ping or telnet or they may not be installed on
their client machines.
Attached to this Tip is a simple field developed utility (FDU) called HNetScan. The self extracting
executable can be installed to the clients computer and will create a desktop icon and normally install
to c:\HNetScan default directory. When you execute HNetScan, enter the host name or IP address of the
remote machine that you wish to test connectivity and click the start button. HNetScan will then perform
a telnet and ping check to the target machine via the IP address and the Port number. A log file is
generated in the c:\HNetScan directory and if left running in the background will rollover and create
a new log at midnight.
You may uninstall this windows utility via the normal uninstall applet in the control panel.
This tool is provided as is to support customer self analysis.
ADDENDUM 24 OCT 2016 - Modified installer to work with windows 10 (32 or 64bit).