MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Mweb guy, I have a question. I've currently got an ADSL line and 2gb account through you guys, and then I use an uncapped account from Openweb, but I am no longer satisfied with the experience on their account and feel it is not worth the money I pay for it. I'm strongly considering cancelling my account with them and getting a new account elsewhere. Seeing as I already have a 2gb account, is it possible that you guys can give me a day trial account or something to test out?
 
Graal said:
Mweb guy, I have a question. I've currently got an ADSL line and 2gb account through you guys, and then I use an uncapped account from Openweb, but I am no longer satisfied with the experience on their account and feel it is not worth the money I pay for it. I'm strongly considering cancelling my account with them and getting a new account elsewhere. Seeing as I already have a 2gb account, is it possible that you guys can give me a day trial account or something to test out?
Click to expand...


Hi Graal

Please see PM I sent you.
 
Segg said:
Ok, just strange considering it operated at 115kB/s on average for the first week.
Click to expand...

115KB/s is "too fast" for a 1Mb line, unless you have a >1Mb line and only a 1Mb uncapped account.
1Mbps = 128KB/s but taking overhead into consideration, 128*0.83 ~~ 106KB/s as a maximum download speed.

From there on downloads are speed limited by several factors, including network load, shaping, server speeds, etc.
 
My connection (PPPoE) keeps randomly dropping, quite often at the moment. Spoke to a friend and said he had the same issue yesterday, Mweb said its not on their side, was wondering if anyone else is also having the issue?
 
Lazy.Me said:
My connection (PPPoE) keeps randomly dropping, quite often at the moment. Spoke to a friend and said he had the same issue yesterday, Mweb said its not on their side, was wondering if anyone else is also having the issue?
Click to expand...

Hi Lazy.Me

Please PM me the MWEB account details in order for me to look into this from our side and provide you with feedback.
 
My internet is extremely slow again. My 1Meg line feels slower than 56K. :(
 
Awesum said:
My internet is extremely slow again. My 1Meg line feels slower than 56K. :(
Click to expand...

Hi Awesum

I checked the account and line. The line readings are a bit irregular. Attenuation is very high. I would suggest contacting Telkom, have them re-create the port and investigate what is causing the attenuation to be that high as well.
 
How do I upgrade my line from 384K to 1MB? (MWeb 1MB uncapped shaped all inclusive account)
 
Cool :D Do it please! Thanks! Is there anything I should do in order to make it happen? When Telkom upgrades my line from 1MB to 2MB later, I will want to have it downgraded to 1MB.
 
DarkSpectre said:
Cool :D Do it please! Thanks! Is there anything I should do in order to make it happen? When Telkom upgrades my line from 1MB to 2MB later, I will want to have it downgraded to 1MB.
Click to expand...

I will arrange this for you.
When Telkom does your upgrade from 1Mb to 2Mb all you will have to do is notify us then we will be able to arrange the downgrade to 1Mb.
 
Since the week-end (possible before that) I cannot connect to Battle.net, in my case StarCraft 2 in particular.

Luckily I had a 1Gb free Afrihost account and that allowed me to download and install the latest patches (patch 1.50), but I can't even authenticate on Mweb. I tried in vain to install the patch the entire week-end, and now I can't even log into the game.

Is Mweb now blocking access to Battle.net? Could someone please look into this for me.
 
MyWorld said:
Since the week-end (possible before that) I cannot connect to Battle.net, in my case StarCraft 2 in particular.

Luckily I had a 1Gb free Afrihost account and that allowed me to download and install the latest patches (patch 1.50), but I can't even authenticate on Mweb. I tried in vain to install the patch the entire week-end, and now I can't even log into the game.

Is Mweb now blocking access to Battle.net? Could someone please look into this for me.
Click to expand...

Hi MyWorld

Is this the only thing you are having trouble with ?
How is your browsing and downloads ?
Provide me with trace route results.
 
Browsing and downloading seems fine over http and ftp, tested a NZB as well to be sure.

It is only Battle.net that is not authenticating.

I have no idea what the IP and port is Battle.net is using for SC2 authentication, if someone could provide me with this I will traceroute.

I know the pach server uses ports 6881-6999. Are these blocked on Mweb's side?

EDIT:
Just got the login servers details, here is the traceroutes:

Code: 
traceroute to us.logon.battle.net (12.129.206.130), 30 hops max, 60 byte packets
 1  login.router (192.168.0.1)  1.364 ms  1.709 ms  2.141 ms
 2  41-132-76-1.dsl.mweb.co.za (41.132.76.1)  10.333 ms  12.396 ms  14.870 ms
 3  tengig-0-0-0-104.vic-ipc-1.mweb.co.za (196.22.169.146)  22.924 ms  24.433 ms  26.167 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  28.649 ms  30.572 ms  32.710 ms
 5  tengig0-7-0-2.12.vic-p-1.mweb.co.za (196.22.169.241)  227.402 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za (196.22.169.242)  231.332 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za (196.22.169.225)  231.904 ms
 6  pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7)  235.231 ms pos0-3-0-0.lon-up-1.mweb.co.za (197.80.5.9)  222.243 ms pos0 (197.80.5.7)  209.986 ms
 7  176.67.177.131 (176.67.177.131)  208.617 ms  212.281 ms  212.283 ms
 8  xe-8-1-0.edge3.London1.Level3.net (195.50.124.133)  228.057 ms  212.374 ms  215.493 ms
 9  vl-3602-ve-226.csw2.London1.Level3.net (4.69.166.149)  220.882 ms vl-3604-ve-228.csw2.London1.Level3.net (4.69.166.157)  231.180 ms vl-3603-ve-227.csw2.London1.Level3.net (4.69.166.153)  227.805 ms
10  ae-59-224.ebr2.London1.Level3.net (4.69.153.141)  229.956 ms ae-56-221.ebr2.London1.Level3.net (4.69.153.129)  213.440 ms  220.642 ms
11  ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70)  287.185 ms ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66)  288.863 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74)  293.566 ms
12  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74)  284.582 ms  284.304 ms  284.318 ms
13  ae-2-70.edge3.NewYork1.Level3.net (4.69.155.81)  302.230 ms ae-1-60.edge3.NewYork1.Level3.net (4.69.155.17)  295.178 ms ae-3-80.edge3.NewYork1.Level3.net (4.69.155.145)  345.172 ms
14  att-level3.newyork1.level3.net (4.68.63.142)  300.287 ms  300.291 ms  280.372 ms
15  cr1.n54ny.ip.att.net (12.122.131.102)  359.312 ms  359.319 ms  359.571 ms
16  cr2.cgcil.ip.att.net (12.122.1.2)  377.411 ms  377.412 ms  377.035 ms
17  cr1.cgcil.ip.att.net (12.122.2.53)  374.793 ms  349.738 ms  355.716 ms
18  cr2.dvmco.ip.att.net (12.122.31.85)  364.860 ms  365.734 ms  366.269 ms
19  cr1.slkut.ip.att.net (12.122.30.25)  367.111 ms  369.934 ms  373.582 ms
20  cr2.la2ca.ip.att.net (12.122.30.30)  361.758 ms  363.945 ms  364.182 ms
21  gar29.la2ca.ip.att.net (12.122.129.241)  361.650 ms  364.432 ms  364.430 ms
22  12-122-254-238.attens.net (12.122.254.238)  368.085 ms 12-122-254-234.attens.net (12.122.254.234)  372.019 ms  358.916 ms
23  mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  355.424 ms mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254)  363.991 ms mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  351.402 ms
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


traceroute eu.logon.battle.net
traceroute to eu.logon.battle.net (213.248.127.130), 30 hops max, 60 byte packets
 1  login.router (192.168.0.1)  1.262 ms  1.689 ms  2.121 ms
 2  41 (41.132.76.1)  10.052 ms  11.474 ms  13.939 ms
 3  tengig-0-0-0-101.vic-ipc-1.mweb.co.za (196.22.169.134)  22.091 ms  24.750 ms  26.112 ms
 4  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2)  29.001 ms  30.603 ms  32.578 ms
 5  tengig0-0-0-2.11.vic-p-2.mweb.co.za (196.22.169.226)  227.322 ms  231.490 ms  231.495 ms
 6  pos0 (197.80.5.7)  233.337 ms  225.408 ms pos0 (197.80.5.9)  223.569 ms
 7  176.67.177.131 (176.67.177.131)  223.981 ms  228.557 ms  228.532 ms
 8  xe (195.50.124.133)  237.106 ms  212.736 ms  211.431 ms
 9  vl (4.69.166.149)  228.566 ms vl-3501-ve-115.csw1.London1.Level3.net (4.69.166.129)  218.061 ms vl (4.69.166.157)  223.602 ms
10  ae-1-51.edge5.London1.Level3.net (4.69.139.75)  222.391 ms * *
11  ldn-b5-link.telia.net (213.248.92.81)  220.971 ms Telia (4.68.111.182)  221.734 ms ldn (213.248.92.81)  215.198 ms
12  ldn-bb1-link.telia.net (80.91.247.91)  225.466 ms ldn-bb2-link.telia.net (80.91.249.181)  228.080 ms ldn-bb2-link.telia.net (80.91.247.93)  230.557 ms
13  prs-bb2-link.telia.net (80.91.247.240)  267.577 ms prs-bb1-link.telia.net (213.155.134.34)  243.101 ms prs-bb1-link.telia.net (80.91.247.254)  226.659 ms
14  ffm-bb2-link.telia.net (80.91.246.180)  234.486 ms  234.464 ms ffm-bb1-link.telia.net (80.91.245.100)  237.825 ms
15  ffm-b10-link.telia.net (80.91.251.248)  243.414 ms ffm-b10-link.telia.net (80.91.247.185)  243.710 ms *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Servers cannot be reached.
:(
 
Last edited:
Did some more digging, and according to the Battle.net support site (http://us.battle.net/support/en/article/performing-a-traceroute) I should try a different IP and logon server, but the results stay the same:

traceroute 12.129.202.154
traceroute to 12.129.202.154 (12.129.202.154), 30 hops max, 60 byte packets
1 login.router (192.168.0.1) 1.404 ms 1.739 ms 2.099 ms
2 41-132-76-1.dsl.mweb.co.za (41.132.76.1) 10.559 ms 12.001 ms 14.947 ms
3 197-80-4-82.jhb.mweb.co.za (197.80.4.82) 22.272 ms 24.274 ms 26.017 ms
4 vl-92.vic-hscore-1.mweb.co.za (196.22.189.2) 29.058 ms 30.434 ms vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 32.132 ms
5 tengig0-7-0-2.12.vic-p-1.mweb.co.za (196.22.169.241) 228.842 ms 228.856 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za (196.22.169.242) 233.817 ms
6 pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7) 232.908 ms 223.522 ms 209.790 ms
7 176.67.177.131 (176.67.177.131) 209.756 ms 213.426 ms 213.739 ms
8 xe-8-1-0.edge3.London1.Level3.net (195.50.124.133) 213.665 ms 213.667 ms 215.718 ms
9 vl-3603-ve-227.csw2.London1.Level3.net (4.69.166.153) 222.826 ms vl-3604-ve-228.csw2.London1.Level3.net (4.69.166.157) 224.555 ms vl (4.69.166.153) 222.827 ms
10 ae-56-221.ebr2.London1.Level3.net (4.69.153.129) 230.135 ms ae-57-222.ebr2.London1.Level3.net (4.69.153.133) 210.030 ms ae-59-224.ebr2.London1.Level3.net (4.69.153.141) 217.993 ms
11 ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66) 287.637 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 284.998 ms 290.726 ms
12 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 292.856 ms ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 294.590 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 304.739 ms
13 ae-3-80.edge3.NewYork1.Level3.net (4.69.155.145) 298.242 ms ae-2-70.edge3.NewYork1.Level3.net (4.69.155.81) 287.778 ms ae (4.69.155.145) 282.581 ms
14 att-level3.newyork1.level3.net (4.68.63.142) 291.227 ms 291.234 ms 291.223 ms
15 cr1.n54ny.ip.att.net (12.122.131.102) 368.653 ms 368.414 ms 368.388 ms
16 cr2.cgcil.ip.att.net (12.122.1.2) 383.152 ms 364.263 ms 361.447 ms
17 cr1.cgcil.ip.att.net (12.122.2.53) 355.889 ms 355.894 ms 356.216 ms
18 cr2.dvmco.ip.att.net (12.122.31.85) 369.784 ms 369.795 ms 362.784 ms
19 cr1.slkut.ip.att.net (12.122.30.25) 364.711 ms 364.970 ms 364.677 ms
20 cr2.la2ca.ip.att.net (12.122.30.30) 372.296 ms 366.050 ms 365.632 ms
21 gar29.la2ca.ip.att.net (12.122.129.241) 397.958 ms 369.494 ms 357.289 ms
22 12-122-254-238.attens.net (12.122.254.238) 364.401 ms 12-122-254-234.attens.net (12.122.254.234) 365.587 ms 12 (12.122.254.238) 361.093 ms
23 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 362.926 ms mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 358.744 ms 358.752 ms
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


traceroute europe.battle.net
traceroute to europe.battle.net (213.248.106.68), 30 hops max, 60 byte packets
1 login.router (192.168.0.1) 1.305 ms 1.669 ms 2.128 ms
2 41 (41.132.76.1) 9.581 ms 12.005 ms 14.215 ms
3 tengig-0-0-0-104.vic-ipc-2.mweb.co.za (196.22.163.218) 22.269 ms 23.812 ms 26.180 ms
4 vl (196.22.189.2) 28.958 ms vl (196.22.189.3) 30.894 ms 32.611 ms
5 tengig0-0-0-2.11.vic-p-1.mweb.co.za (196.22.169.225) 226.449 ms tengig0 (196.22.169.242) 229.513 ms 232.982 ms
6 pos0 (197.80.5.7) 233.852 ms pos0-3-0-0.lon-up-1.mweb.co.za (197.80.5.9) 226.503 ms 222.063 ms
7 176.67.177.131 (176.67.177.131) 226.550 ms 226.987 ms 226.960 ms
8 xe (195.50.124.133) 239.800 ms 212.424 ms 210.938 ms
9 vl (4.69.166.157) 228.071 ms 228.055 ms vl-3503-ve-117.csw1.London1.Level3.net (4.69.166.137) 227.209 ms
10 ae-1-51.edge5.London1.Level3.net (4.69.139.75) 224.686 ms * *
11 ldn-b5-link.telia.net (213.248.96.37) 220.802 ms 220.777 ms ldn-b5-link.telia.net (213.248.92.81) 225.890 ms
12 ldn-bb1-link.telia.net (80.91.248.217) 226.426 ms ldn-bb1-link.telia.net (80.91.247.91) 228.091 ms 228.071 ms
13 hbg-bb2-link.telia.net (80.91.245.6) 241.939 ms hbg-bb1-link.telia.net (80.91.247.42) 235.052 ms 235.056 ms
14 s-bb1-link.telia.net (80.91.247.144) 253.398 ms s-bb1-link.telia.net (213.155.135.237) 294.014 ms s-bb1-link.telia.net (213.155.130.117) 255.340 ms
15 s-b3-link.telia.net (213.155.133.101) 260.453 ms s-b3-link.telia.net (213.155.131.121) 264.117 ms s-b3-link.telia.net (213.155.133.97) 260.787 ms
16 s-hdn-i3-link.telia.net (80.91.249.69) 259.653 ms 260.729 ms 264.374 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Click to expand...
 
MyWorld said:
Browsing and downloading seems fine over http and ftp, tested a NZB as well to be sure.

It is only Battle.net that is not authenticating.

I have no idea what the IP and port is Battle.net is using for SC2 authentication, if someone could provide me with this I will traceroute.

I know the pach server uses ports 6881-6999. Are these blocked on Mweb's side?

EDIT:
Just got the login servers details, here is the traceroutes:

Code: 
traceroute to us.logon.battle.net (12.129.206.130), 30 hops max, 60 byte packets
 1  login.router (192.168.0.1)  1.364 ms  1.709 ms  2.141 ms
 2  41-132-76-1.dsl.mweb.co.za (41.132.76.1)  10.333 ms  12.396 ms  14.870 ms
 3  tengig-0-0-0-104.vic-ipc-1.mweb.co.za (196.22.169.146)  22.924 ms  24.433 ms  26.167 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  28.649 ms  30.572 ms  32.710 ms
 5  tengig0-7-0-2.12.vic-p-1.mweb.co.za (196.22.169.241)  227.402 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za (196.22.169.242)  231.332 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za (196.22.169.225)  231.904 ms
 6  pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7)  235.231 ms pos0-3-0-0.lon-up-1.mweb.co.za (197.80.5.9)  222.243 ms pos0 (197.80.5.7)  209.986 ms
 7  176.67.177.131 (176.67.177.131)  208.617 ms  212.281 ms  212.283 ms
 8  xe-8-1-0.edge3.London1.Level3.net (195.50.124.133)  228.057 ms  212.374 ms  215.493 ms
 9  vl-3602-ve-226.csw2.London1.Level3.net (4.69.166.149)  220.882 ms vl-3604-ve-228.csw2.London1.Level3.net (4.69.166.157)  231.180 ms vl-3603-ve-227.csw2.London1.Level3.net (4.69.166.153)  227.805 ms
10  ae-59-224.ebr2.London1.Level3.net (4.69.153.141)  229.956 ms ae-56-221.ebr2.London1.Level3.net (4.69.153.129)  213.440 ms  220.642 ms
11  ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70)  287.185 ms ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66)  288.863 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74)  293.566 ms
12  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74)  284.582 ms  284.304 ms  284.318 ms
13  ae-2-70.edge3.NewYork1.Level3.net (4.69.155.81)  302.230 ms ae-1-60.edge3.NewYork1.Level3.net (4.69.155.17)  295.178 ms ae-3-80.edge3.NewYork1.Level3.net (4.69.155.145)  345.172 ms
14  att-level3.newyork1.level3.net (4.68.63.142)  300.287 ms  300.291 ms  280.372 ms
15  cr1.n54ny.ip.att.net (12.122.131.102)  359.312 ms  359.319 ms  359.571 ms
16  cr2.cgcil.ip.att.net (12.122.1.2)  377.411 ms  377.412 ms  377.035 ms
17  cr1.cgcil.ip.att.net (12.122.2.53)  374.793 ms  349.738 ms  355.716 ms
18  cr2.dvmco.ip.att.net (12.122.31.85)  364.860 ms  365.734 ms  366.269 ms
19  cr1.slkut.ip.att.net (12.122.30.25)  367.111 ms  369.934 ms  373.582 ms
20  cr2.la2ca.ip.att.net (12.122.30.30)  361.758 ms  363.945 ms  364.182 ms
21  gar29.la2ca.ip.att.net (12.122.129.241)  361.650 ms  364.432 ms  364.430 ms
22  12-122-254-238.attens.net (12.122.254.238)  368.085 ms 12-122-254-234.attens.net (12.122.254.234)  372.019 ms  358.916 ms
23  mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  355.424 ms mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254)  363.991 ms mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  351.402 ms
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


traceroute eu.logon.battle.net
traceroute to eu.logon.battle.net (213.248.127.130), 30 hops max, 60 byte packets
 1  login.router (192.168.0.1)  1.262 ms  1.689 ms  2.121 ms
 2  41 (41.132.76.1)  10.052 ms  11.474 ms  13.939 ms
 3  tengig-0-0-0-101.vic-ipc-1.mweb.co.za (196.22.169.134)  22.091 ms  24.750 ms  26.112 ms
 4  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2)  29.001 ms  30.603 ms  32.578 ms
 5  tengig0-0-0-2.11.vic-p-2.mweb.co.za (196.22.169.226)  227.322 ms  231.490 ms  231.495 ms
 6  pos0 (197.80.5.7)  233.337 ms  225.408 ms pos0 (197.80.5.9)  223.569 ms
 7  176.67.177.131 (176.67.177.131)  223.981 ms  228.557 ms  228.532 ms
 8  xe (195.50.124.133)  237.106 ms  212.736 ms  211.431 ms
 9  vl (4.69.166.149)  228.566 ms vl-3501-ve-115.csw1.London1.Level3.net (4.69.166.129)  218.061 ms vl (4.69.166.157)  223.602 ms
10  ae-1-51.edge5.London1.Level3.net (4.69.139.75)  222.391 ms * *
11  ldn-b5-link.telia.net (213.248.92.81)  220.971 ms Telia (4.68.111.182)  221.734 ms ldn (213.248.92.81)  215.198 ms
12  ldn-bb1-link.telia.net (80.91.247.91)  225.466 ms ldn-bb2-link.telia.net (80.91.249.181)  228.080 ms ldn-bb2-link.telia.net (80.91.247.93)  230.557 ms
13  prs-bb2-link.telia.net (80.91.247.240)  267.577 ms prs-bb1-link.telia.net (213.155.134.34)  243.101 ms prs-bb1-link.telia.net (80.91.247.254)  226.659 ms
14  ffm-bb2-link.telia.net (80.91.246.180)  234.486 ms  234.464 ms ffm-bb1-link.telia.net (80.91.245.100)  237.825 ms
15  ffm-b10-link.telia.net (80.91.251.248)  243.414 ms ffm-b10-link.telia.net (80.91.247.185)  243.710 ms *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Servers cannot be reached.
:(
Click to expand...

Thank you for this information, I will have a look into this for you.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X