I am having trouble getting the same results from a tracert. I have attached the tracert information and then the NetPath information. The tracert is what I was looking for from NetPath. What am I doing wrong in NetPath?
I'm having the exact same problem - when using an external probe rather than the NPM Host itself.
After consulting with my SW supplier, which - in turn escalated this to SW Support, we've collected a few diag logs and I've been advised to reinstall NetPath services.
I hope I'll get to this today - I'll keep updating here. . .
Update: reinstalling NetPath did not resolve this issue for me.
I've ran "Orion Diagnostics" and sent it over to the wise people at SW, for them to further analyse this bug.
Did you catch my response earlier in the thread? #2 highlights the most common reasons we have seen the topology shown in the screenshot of this thread.
this was the issue. When I removed the proxy in the firewall from http and https it worked. now I only need to figure out how to make it work with the proxy. thanks
Thanks cobrien, I did catch your response.
Reason #2 is invalid in this case - there's no proxy, nor any device spoofing the destination. (www.google.com for example...)