This could happen when the reply comes back from a different IP then the one that is pinged. Typicaly with a system with several network cards OR several IP addresses. In 1610 build (latest is on http://beta.woodstone.nu) we log this correctly into the logfile.
Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carter, Phillip Sent: Wednesday, November 03, 2004 4:01 AM To: [EMAIL PROTECTED] Subject: [SA-list] Problem with server PING Running Salive 4.1.1609 on W2k Pro SP4. I've got a check setup to ping one of our servers and it routinely fails even though a command-line ping to the same server is successful. The check is setup to do 4 pings with a timeout of 4 seconds. The Salive log shows, 3/11/2004 1:12:52 PM xxxxxx Ping 3/11/2004 1:12:53 PM ERR PING status: 11010 3/11/2004 1:12:54 PM ERR PING status: 11010 3/11/2004 1:12:55 PM ERR PING status: 11010 3/11/2004 1:12:56 PM ERR PING status: 11010 3/11/2004 1:12:56 PM xxxxxx Ping failed due to a successrate of only 0% 3/11/2004 1:13:05 PM xxxxxx Ping 3/11/2004 1:13:07 PM ERR PING status: 11010 3/11/2004 1:13:08 PM ERR PING status: 11010 3/11/2004 1:13:09 PM ERR PING status: 11010 3/11/2004 1:13:10 PM ERR PING status: 11010 3/11/2004 1:13:10 PM xxxxxx Ping failed due to a successrate of only 0% While the command-line ping, running on the same machine returns, Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=128 Etc... Why is Salive failing the ping check?? Thanks Phillip Carter Database Administrator Bell Potter Securities Limited email: [EMAIL PROTECTED] Ph: +61 3 9235 1691 Fax: +61 3 9235 1665 IMPORTANT DISCLAIMER - THIS MAY AFFECT YOUR LEGAL RIGHTS: Because this document has been prepared without consideration of any specific clients investment objectives, financial situation or needs, a Bell Potter Securities Limited investment adviser should be consulted before any investment decision is made. While this document is based on the information from sources which are considered reliable, Bell Potter Securities Limited, its directors, employees and consultants do not represent, warrant or guarantee, expressly or impliedly, that the information contained in this document is complete or accurate. Nor does Bell Potter Securities Limited accept any responsibility to inform you of any matter that subsequently comes to its notice, which may affect any of the information contained in this document. This document is a private communication to clients and is not intended for public circulation or for the use of any third party, without the prior approval of Bell Potter Securities. Disclosure of Interest: Bell Potter Securities Limited receives commission from dealing in securities and its authorised representatives, or introducers of business, may directly share in this commission. Bell Potter Securities and its associates may hold shares in the companies recommended. Bell Potter Securities Limited ABN 25 006 390 772 AFS Licence No. 243480 ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
