Then why is it so hard to paste a tracert here so we can compare the routes ?
Obviously not as I was clearly replying to nelis which you replied to and I followed up on
Wow, not sure why you throwing a complete hissy fit here when people are trying to help you. If you don't want to be helped why not do the smart thing and move to another provider, thus voting with your wallet.
Tracing route to bruce.ferrago.net [84.234.17.86]
over a maximum of 30 hops:
1 22 ms 22 ms 21 ms 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
2 32 ms 33 ms 31 ms Te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
3 32 ms 34 ms 31 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
4 34 ms 48 ms 36 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
5 186 ms 184 ms 185 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
6 343 ms 212 ms 201 ms linx-extreme1.netrino.co.uk [195.66.227.18]
7 373 ms 203 ms 211 ms thn-edge.netrino.co.uk [84.234.19.142]
8 186 ms 185 ms 185 ms hex-edge.netrino.co.uk [84.234.19.146]
9 187 ms 188 ms 187 ms bs1-core.netrino.co.uk [84.234.19.5]
10 189 ms 188 ms 189 ms bruce.ferrago.net [84.234.17.86]
Trace complete.
Tracing route to bruce.ferrago.net [84.234.17.86]
over a maximum of 30 hops:
0 Sillicur-PC [41.133.132.100]
1 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
2 Te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
3 Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
4 TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
5 pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
6 linx-extreme1.netrino.co.uk [195.66.227.18]
7 thn-edge.netrino.co.uk [84.234.19.142]
8 hex-edge.netrino.co.uk [84.234.19.146]
9 bs1-core.netrino.co.uk [84.234.19.5]
10 bruce.ferrago.net [84.234.17.86]
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sillicur-PC [41.133.132.100]
0/ 100 = 0% |
1 54ms 2/ 100 = 2% 2/ 100 = 2% 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
0/ 100 = 0% |
2 55ms 1/ 100 = 1% 1/ 100 = 1% Te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
0/ 100 = 0% |
3 52ms 1/ 100 = 1% 1/ 100 = 1% Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
0/ 100 = 0% |
4 55ms 1/ 100 = 1% 1/ 100 = 1% TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
0/ 100 = 0% |
5 205ms 1/ 100 = 1% 1/ 100 = 1% pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
0/ 100 = 0% |
6 214ms 1/ 100 = 1% 1/ 100 = 1% linx-extreme1.netrino.co.uk [195.66.227.18]
0/ 100 = 0% |
7 210ms 0/ 100 = 0% 0/ 100 = 0% thn-edge.netrino.co.uk [84.234.19.142]
0/ 100 = 0% |
8 208ms 0/ 100 = 0% 0/ 100 = 0% hex-edge.netrino.co.uk [84.234.19.146]
0/ 100 = 0% |
9 211ms 0/ 100 = 0% 0/ 100 = 0% bs1-core.netrino.co.uk [84.234.19.5]
1/ 100 = 1% |
10 208ms 1/ 100 = 1% 0/ 100 = 0% bruce.ferrago.net [84.234.17.86]
Trace complete.
U say you were replying to nelis but you quoted me when saying "No, but how can one help someone who can't give you as the technician at least something to start on apart from my game is kak?". I am not a tech guy, but I just dont see the point of doing these tracerts again and again. Like now when i do it everything is fine, no timeouts. My problem is when i show this tracert when everything is fine, Mweb will just say everything is fine and close my ticket.....Even thou they know its a problem that occurs sporadically.
Dont talk to me about throwing a complete hissy fit son. When you quoted me and said that i pretty much snapped. I have put so much time and effort into this fault already. I want to be helped, but they wont and you cannot help me. You cannot fix their network so I honestly dont see the point, unless you work for Mweb, there is nothing you can do.
Edit: Oh look, packets lost. What a surprise. Seemed fine a moment ago and now it has gone to **** again pretty much.