Checking the logs of the target server can confirm that the telnet did indeed connect to the target server is required. If the DNS is incorrect, or if there are firewalls between the originating server and the target server, it can seem to connect but it might not be the correct server. Just running Telnet or Powershell and connecting to a server is only part of the test.
How to use telnet server how to#
How to verify that Telnet or Powershell connected to the target server See the 'How to verify that Telnet or Powershell connected to the target server' section below. If the TcpTestSucceeded in the Powershell results shows True, then check the esmd.log (Unix\Linux) or the esmagent.log (Windows) on the agent to see if the agent registers the connection.
If the TcpTestSucceeded in the Powershell results shows False, then it was not able to connect to that port on that agent, and you need to determine what is blocking it.
Test-NetConnection -Port -ComputerName -InformationLevel DetailedĮxample: PS C:\Users\ebsvc> Test-NetConnection -Port 5601 -ComputerName 10.32.111.237 -InformationLevel Detailed In this example you are running this on the CCS manager to test communication to a CCS agent, but it could also be used to test communication from an agent to a manager, etc. Start Powershell and run the following command. How to use Powershell to test connectivity Press another key to break the connection and return to a command prompt. If a blank screen appears with no errors a telnet session has been established. Telnet mgrccstest 5600 (this example shows an attempt to telnet to the target server MGRCCSTEST using port 5600) (NOTE: You can use the hostname, FQDN, or IP of the CCS component you would like to connect to can be used to test) You might have to open the cmd 'As administrator') Telnet syntax: Start -> Run -> cmd (to open a command prompt. Example: from ManagerA to ManagerB, and then from ManagerB to ManagerA. It is best to test communication from each server that is running a CCS components. How use Telnet or Powershell to test connectivity
0 kommentar(er)
