|
KirkG@PacInfoSys.com wrote: > > Scott is right, IBM doesn't provide a traceroute function. Go to the > archive and search on traceroute. I found one there and DL'd and it works. > I don't know if it was Scott's or someone else's, but I know at least one > does exist. > Thanks - found one. Didn't resolve the problem though. Maybe someone out there has run into a similar situation. In an attempt to monitor the status of our networks and internet connection we would like the 400 to ping our internet router. The router is on the other side of our firewall (Firebox) When we ping any outside IP address ex: ping www.midrange.com Pings 1,3 and 5 are successful. Pings 1 & 2 fail with no response after one second. If we ping to local addresses or to the DMZ of the firewall all 5 pings are successful. I can't figure out what is happening to the pings (2 & 4) that are getting lost. Secondly if there is an improper route on the 400 this may be affecting performance. John Hall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.