How do I monitor a server, when ping is disabled between the applications manager and the server?

How do I monitor a server, when ping is disabled between the applications manager and the server?

Follow the steps below:


1) Edit <AppManager Home\conf\AvailabiltyTests> file

2) Change the entry <am.porttestenabled=false> to <am.porttestenabled=true>

3) Then change : if telnet <am.portstotest=23>, if SSH <am.portstotest=22>, if WMI <am.portstotest=445,135>

4) Restart Applications Manager and then monitor the system

                  New to ADSelfService Plus?

                    • Related Articles

                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...
                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...
                    • Attributes supported in Analytics Plus from Applications Manager

                      The following tables list the configuration attributes supported in Analytics Plus from Applications Manager, categorized by monitor type. Application Server Monitor Type Attributes .Net ● % Time in GC ● % Time in JIT Compiling ● Bytes Received/Min ● ...
                    • Troubleshooting - LDAP Server

                      To troubleshoot LDAP Server Monitor, follow the below steps: 1. Unable to connect to the server: Check if the given Host Name / IP Address is correct. Run the below command in Applications Manger installed server to ensure Host / IP Address is ...
                    • Troubleshooting MS SQL Monitor Addition Problems

                      1. Ensure that the SQL Server is running and accessible. Try connecting to the SQL Server instance via SQL Server Management Studio or DBVisualizer using the same credentials. This step helps diagnose connection issues, ensuring that both the server ...