tag:blogger.com,1999:blog-6013019333081665053.post4390789571770923998..comments2023-07-02T18:46:10.240-07:00Comments on Feroze's musings on Technology: Implementing Traceroute with System.Net - Part IVFeroze Daudhttp://www.blogger.com/profile/02314158942083686821noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6013019333081665053.post-59766465112454436652014-01-05T17:59:34.100-08:002014-01-05T17:59:34.100-08:00hi! Dean
Thanks for your reply. I looked at the d...hi! Dean<br /><br />Thanks for your reply. I looked at the documentation for Ping.Send ( http://msdn.microsoft.com/en-us/library/hb7xxkfx(v=vs.110).aspx ) and did not find any mention for getting a NULL return object for Ping.Send(). So if you are getting a null object back, it is most likely a bug. Do you know how to reproduce that behavior?Feroze Daudhttps://www.blogger.com/profile/02314158942083686821noreply@blogger.comtag:blogger.com,1999:blog-6013019333081665053.post-19155016642218623692013-10-04T16:59:05.137-07:002013-10-04T16:59:05.137-07:00Hi Feroze,
First of all, thank you VERY much for ...Hi Feroze,<br /><br />First of all, thank you VERY much for this posting, an excellent, and very useful piece on using Ping().<br /><br />One note: I have found that, depending on one's network, line 35 can have a null reply.Address, yet the subsequent round passes can still work fine.<br /><br />Protecting against this by surrounding lines 35 - 39 successfully bypasses using these round Dean Ciriellihttps://www.blogger.com/profile/14965156198233846961noreply@blogger.com