![]() This command at least gave me an exact time stamp, which is different than a regular ping from my experience (does not have a time-stamp). I could kick off the pings for a live look, or kick off with the output to a text file option and let run for as long as the test period was. We could then compare the time stamps of the ping timeouts to the network load time stamps for the application that was running and see where & when it was maxing out. Thankfully now there are other resources like WUG or Solar Winds in place to get more detailed data like Top Talkers, but I have found it handy to have an exact timestamped ping entry on several occasions nonetheless. timestamp after 10:25:58.81 has jumped back to 10:25:52.73 in the next ping I am seeing disparity in the timestamp when the connection resumes after disconnection.įor e.g. General failure.Īny idea why is this happening? I am redirecting the output to a text file. #Cmd ping transmit failure general failure windows.#Cmd ping transmit failure general failure software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |