MWEB Connection problems

B

Bratt

New member
Hi,

I have been playing GW2 (at least trying to) since it came out and have been experiencing constabt disconnects for the last month (September). I have a 4MB line and uncapped account with MWEB. I have phone almost everyday to try and resolve this. On all occasions the MWEB person makes me change login details on router which ends up with me not being able to access the internet... When I do a speed test (local mweb test and speedtest.net) I get around 0.3-0.5MB downloads.

I have opened tickets with Telkom (MWEB blame them) and they have come out and tested my line, and found it to be okay.

Here is a tracert I just did to GW2 server:
C:\>tracert 206.127.158.49

Tracing route to 206-127-158-49.plaync.com [206.127.158.49]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 597 ms 494 ms 434 ms 41-135-94-1.dsl.mweb.co.za [41.135.94.1]
3 589 ms 614 ms 610 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 510 ms 517 ms 512 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 680 ms 679 ms 762 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178.97]
6 709 ms 698 ms 628 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 592 ms 668 ms 745 ms 176.67.177.131
8 683 ms 746 ms 762 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 762 ms 766 ms 719 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
10 769 ms 694 ms 639 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 732 ms 752 ms 791 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
12 712 ms 729 ms 749 ms ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26]
13 701 ms 665 ms 642 ms ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
14 723 ms 693 ms 700 ms 195.16.161.58
15 754 ms 718 ms 747 ms 206-127-157-86.plaync.com [206.127.157.86]
16 759 ms 800 ms 747 ms 206-127-157-102.plaync.com [206.127.157.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\>tracert 206.127.158.49

Tracing route to 206-127-158-49.plaync.com [206.127.158.49]
over a maximum of 30 hops:

1 1 ms 1 ms 4 ms home.gateway [192.168.1.254]
2 556 ms 578 ms 558 ms 41-135-94-1.dsl.mweb.co.za [41.135.94.1]
3 650 ms 622 ms 568 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 536 ms 522 ms 496 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 666 ms 701 ms 708 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178.97]
6 706 ms 729 ms 762 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 682 ms 682 ms 677 ms 176.67.177.131
8 857 ms 791 ms 807 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 829 ms 773 ms 716 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
10 687 ms 646 ms 662 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 754 ms 820 ms 837 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
12 864 ms 816 ms 804 ms ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26]
13 790 ms 736 ms 775 ms ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
14 731 ms 722 ms 738 ms 195.16.161.58
15 786 ms 818 ms 738 ms 206-127-157-86.plaync.com [206.127.157.86]
16 728 ms 792 ms 735 ms 206-127-157-102.plaync.com [206.127.157.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

And some random pings:
C:\>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=555ms TTL=122
Reply from 196.2.63.110: bytes=32 time=555ms TTL=122
Reply from 196.2.63.110: bytes=32 time=932ms TTL=122
Reply from 196.2.63.110: bytes=32 time=592ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 555ms, Maximum = 932ms, Average = 658ms

C:\>ping www.telkom.co.za

Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 196.43.22.222: bytes=32 time=619ms TTL=241
Request timed out.

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 619ms, Maximum = 619ms, Average = 619ms

Not really sure what to do anymore. Would I be able to play GW2 on a 1MB account? I dont see why I should pay so much money if I dont get even 10% of the speed on a good day...:mad:
 
Bratt said:
Hi,

I have been playing GW2 (at least trying to) since it came out and have been experiencing constabt disconnects for the last month (September). I have a 4MB line and uncapped account with MWEB. I have phone almost everyday to try and resolve this. On all occasions the MWEB person makes me change login details on router which ends up with me not being able to access the internet... When I do a speed test (local mweb test and speedtest.net) I get around 0.3-0.5MB downloads.

I have opened tickets with Telkom (MWEB blame them) and they have come out and tested my line, and found it to be okay.

Here is a tracert I just did to GW2 server:
C:\>tracert 206.127.158.49

Tracing route to 206-127-158-49.plaync.com [206.127.158.49]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 597 ms 494 ms 434 ms 41-135-94-1.dsl.mweb.co.za [41.135.94.1]
3 589 ms 614 ms 610 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 510 ms 517 ms 512 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 680 ms 679 ms 762 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178.97]
6 709 ms 698 ms 628 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 592 ms 668 ms 745 ms 176.67.177.131
8 683 ms 746 ms 762 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 762 ms 766 ms 719 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
10 769 ms 694 ms 639 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 732 ms 752 ms 791 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
12 712 ms 729 ms 749 ms ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26]
13 701 ms 665 ms 642 ms ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
14 723 ms 693 ms 700 ms 195.16.161.58
15 754 ms 718 ms 747 ms 206-127-157-86.plaync.com [206.127.157.86]
16 759 ms 800 ms 747 ms 206-127-157-102.plaync.com [206.127.157.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\>tracert 206.127.158.49

Tracing route to 206-127-158-49.plaync.com [206.127.158.49]
over a maximum of 30 hops:

1 1 ms 1 ms 4 ms home.gateway [192.168.1.254]
2 556 ms 578 ms 558 ms 41-135-94-1.dsl.mweb.co.za [41.135.94.1]
3 650 ms 622 ms 568 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 536 ms 522 ms 496 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 666 ms 701 ms 708 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178.97]
6 706 ms 729 ms 762 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 682 ms 682 ms 677 ms 176.67.177.131
8 857 ms 791 ms 807 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 829 ms 773 ms 716 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
10 687 ms 646 ms 662 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
11 754 ms 820 ms 837 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
12 864 ms 816 ms 804 ms ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26]
13 790 ms 736 ms 775 ms ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.138]
14 731 ms 722 ms 738 ms 195.16.161.58
15 786 ms 818 ms 738 ms 206-127-157-86.plaync.com [206.127.157.86]
16 728 ms 792 ms 735 ms 206-127-157-102.plaync.com [206.127.157.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

And some random pings:
C:\>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=555ms TTL=122
Reply from 196.2.63.110: bytes=32 time=555ms TTL=122
Reply from 196.2.63.110: bytes=32 time=932ms TTL=122
Reply from 196.2.63.110: bytes=32 time=592ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 555ms, Maximum = 932ms, Average = 658ms

C:\>ping www.telkom.co.za

Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 196.43.22.222: bytes=32 time=619ms TTL=241
Request timed out.

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 619ms, Maximum = 619ms, Average = 619ms

Not really sure what to do anymore. Would I be able to play GW2 on a 1MB account? I dont see why I should pay so much money if I dont get even 10% of the speed on a good day...:mad:
Click to expand...

You can ping Mweb but not Telkom, yet you want to blame Mweb? Definately a Telkom problem, Looks like your line is just dropping completely, maybe it cant sync at 4Mb's. You can play GW2 on a 1Mb account, you can even play it on 384k. Having a faster line wont give you a better ping when connecting outside of S.A.
 
I live in Kuilsriver, Cape Town. Well the reason I am currently blaming MWEB is that I have had Telkom come and test the line and they said it was fine. But I am not excluding them necessarily. Just that I have a problem and whenever I call MWEB support I end up with more problems than before I phoned them (like no internet access at all), whereas Telkom have attempted to resolve the issue.

They have even dropped my sync rate to test for stability and that didn't improve anything. I will probably drop the line to 1 MB and hopefully that will resolve this.
 
Umm how long has this been going on? Have you tried calling telkom and ask them to reset your port/refresh your current profile speed? Another thing you can do, sign up for a free afrihost account (they give away free accounts every once in a while ) here http://www.afrihost.com/site/page/free_1gb_adsl_account_signup, login with that account, and then do a speedtest again to see if the problem lies with mweb. In fact you can do that with any other account from a different ISP. Also that speedtest result looks like international haha.
 
Telkom have reset ports / and tried different speeds on my profile. The one thing they did mention to me was that I was about 3.9km from the exchange (basically on the limit). With this in mind I doubt I will get a reliable service as things stand currently, so I will downgrade (or upgrade in my case) to a 'more reliable' 1MB and see how things go.

I would have tried the alternate ISP option, but sadly I have one of those MWEB locked Billion routers. So for the moment I will just reduce the speed save some money and buy me a router that can then switch between data suppliers.

Thanks for the advice guys. Really appreciate it.
 
You are getting 700ms ping response times directly after your router... This could be the Telkom line.

Log into your router and check the sync speed, attenuation and SNR levels, you may have a very bad ADSL circuit(Telkom test is a yes/no test... ie if adsl light goes on, it works.).
 
I decided to downgrade to 1MB and last night could play without what had become the usual disconnections every 5 min. I think I played for about 2 hrs before I had to relog. Which was great for me. So I think I will stick with 1MB for now until Telkom implements their new system (The tech that came to my house mentioned something about this.).
 
You should be able to get rid of the MWEB lock on your router if you flash the firmware. I did that with an IS locked one. This will also have the advantage of updating the router to the latest version of the firmware.

The risk is that if you stuff it up, or maybe the power cuts out in the middle of the process or something, you might brick it.
 
You must log in or register to reply here.
Back
Top