MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Is anyone else having speed issues with the news server? Seems since around 1pm it's puttering between 50-200 max. Not the biggest issue, lol, just curious ;)
 
Mine seems fine, getting between 340kB/s and 354kB/s, my max line speed is 360kB/s.
 
Ok, slow speed was obviously the start of something, getting horrid packet loss ingame again and international sites are sluggish :/
 
Be thankful for your slow speeds, my access cut off almost completely this morning at 9. Nothing except telkom.co.za worked. Some kind of DNS problem the techie i called guessed. Works again now but seems to be rather drunk.
 
Hi Mweb guy.....

Thank yu that problem will be fixed in another 2 weeks or so when i move house, it seems the only way to fix the problem is to move closer to the exchange lol....
 
Mweb Guy, It seems Mweb is blocking traffic on Port 119 on both my Uncapped accounts?

Hi Hummercellc

Are you receiving any error message when using port 119?

We are not blocking that port.
 
If I connect to news.mweb.co.za "connection timed out"
If I connect to reader.xsusenet.com "connection timed out" (paid account)

both on port 119

Error: I could not see your service on news.mweb.co.za on port (119)
Error: I could not see your service on reader.xsusenet.com on port (119)

Success: I could see your service on reader.xsusenet.com on port (563)(SSL)
 
Mweb has been great until now, I have been with them for over 12 years. I have started to receive Mweb abuse emails that I am putting strain on their network and further abuse of their network will result in the loss of my ADSL service. I have 5 computers and use +- 400gb a month. Is this really too much on my supposed uncapped 4mb account? Upgrading my package to a business class package is not a option... (Which Mweb clearly suggests in their abuse email)...
 
If I connect to news.mweb.co.za "connection timed out"
If I connect to reader.xsusenet.com "connection timed out" (paid account)

both on port 119

Error: I could not see your service on news.mweb.co.za on port (119)
Error: I could not see your service on reader.xsusenet.com on port (119)

Success: I could see your service on reader.xsusenet.com on port (563)(SSL)

Can you ping the news server?
 
Mweb has been great until now, I have been with them for over 12 years. I have started to receive Mweb abuse emails that I am putting strain on their network and further abuse of their network will result in the loss of my ADSL service. I have 5 computers and use +- 400gb a month. Is this really too much on my supposed uncapped 4mb account? Upgrading my package to a business class package is not a option... (Which Mweb clearly suggests in their abuse email)...

Hi Defiler

You can query this with our abuse department directly in order to establish why they have flagged the account for abuse. They will provide you with more information as well.
 
Yip

Pinging news.mweb.co.za [196.28.78.229] with 32 bytes of data:
Reply from 196.28.78.229: bytes=32 time=68ms TTL=116
Reply from 196.28.78.229: bytes=32 time=66ms TTL=116
Reply from 196.28.78.229: bytes=32 time=65ms TTL=116
Reply from 196.28.78.229: bytes=32 time=64ms TTL=116

Ping statistics for 196.28.78.229:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 68ms, Average = 65ms



Pinging reader.xsusenet.com [91.235.168.35] with 32 bytes of data:
Reply from 91.235.168.35: bytes=32 time=223ms TTL=50
Reply from 91.235.168.35: bytes=32 time=237ms TTL=50
Reply from 91.235.168.35: bytes=32 time=326ms TTL=50
Reply from 91.235.168.35: bytes=32 time=218ms TTL=50

Ping statistics for 91.235.168.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 218ms, Maximum = 326ms, Average = 251ms
 
Yip

Pinging news.mweb.co.za [196.28.78.229] with 32 bytes of data:
Reply from 196.28.78.229: bytes=32 time=68ms TTL=116
Reply from 196.28.78.229: bytes=32 time=66ms TTL=116
Reply from 196.28.78.229: bytes=32 time=65ms TTL=116
Reply from 196.28.78.229: bytes=32 time=64ms TTL=116

Ping statistics for 196.28.78.229:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 68ms, Average = 65ms



Pinging reader.xsusenet.com [91.235.168.35] with 32 bytes of data:
Reply from 91.235.168.35: bytes=32 time=223ms TTL=50
Reply from 91.235.168.35: bytes=32 time=237ms TTL=50
Reply from 91.235.168.35: bytes=32 time=326ms TTL=50
Reply from 91.235.168.35: bytes=32 time=218ms TTL=50

Ping statistics for 91.235.168.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 218ms, Maximum = 326ms, Average = 251ms

I send you a PM, please have a look and let me know.
 
Hi MWEB Guy

Quick heads-up, thanks for the trial account. It expired today and I converted to an actual 4Mb Uncapped account.

Very happy with the speeds I've been getting, hope it stays like that... :)

Cheers
 
Hi MWEB Guy

Quick heads-up, thanks for the trial account. It expired today and I converted to an actual 4Mb Uncapped account.

Very happy with the speeds I've been getting, hope it stays like that... :)

Cheers

Hi udesign

Thank you for the positive feedback.

We appreciate the time taking to post and we always strive to improve our levels of service and support to our customers therefore we are delighted that your experience was positive.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X