Hi Sillicur
We cannot provide you with any additional feedback on the issues you are reporting without sufficient troubleshooting data. The syntax of the pathping command is very straight forward.
cmdprompt> pathping bbc.co.uk for example is all that would be required and then allow the test to complete fully (it takes longer than a normal tracert). As you are claiming that the problem is specific to your MWEB account please provide comparative results between your MWEB account and alternative provider and if there is a clear indication that the packetloss you are experiencing is on the MWEB portion of the route I will have it investigated.
Also please do not make use of tests to Blizzard servers as Blizzard block ICMP traffic on the last portion of the route and you will not get any valid results.
If you cannot provide this information then I'm afraid there is nothing further that we can respond on.
Kind Regards
Will
I provided the data, in this very thread. I did all that. So in response to this post of yours "If you cannot provide this information then I'm afraid there is nothing further that we can respond on." I respond to you with a big **** YOU. After 3 weeks this is what i get, this response. I already provided them with this data on this very thread. Pathping test etc. Now you tell me this.
Mweb guy also quoted me and said in this very thread that "i have recreated your issue on our test bench" Straight up he said that, I have also given the information requested and now after 3 weeks you come up here and say this, if i do not give you the info again and again (even thou i said it happens sporadically and it is hard to catch) there is nothing you can do or respond to me with.
When it happens again I will try to catch it again and again, thou you wont do anything to fix it because you never do.