Mweb News Server - It ain't workin' no more!

I'm gatvol of the news server issues...

Cancelled my account yesterday. Moving on to another account to see how they perform.

Haven't been able to connect to the news server for almost a month now, but before seacom went down, it was fine!

All the 'mweb guys' tell me is that their testing area works fine.

There has been something wrong with my mweb account! If I connect using a saix username and password, I can download from news.mweb.co.za:119. Put my mweb account back in, and nothing. So you tell me what the problem is!? :p

Anyway, I'm out from Jan 12

The mweb gyus told me the same thing. all is fine on their side. Is it possible that it could have anything to do with the telkom exchange? Maybe we use the same one? Im in the Somerset West area.
 
Last edited:
The mweb gyus told me the same thing. all is fine on their side. Is it possible that it could have anything to do with the telkom exchange? Maybe we use the same one? Im in the Somerset West area.

Well in that case we are on the same one!!! Somerset west exchange, not the breaview one in heldervue, but the one near the court...

I can still connect to it when doing a pppoe dial up connection on SAIX, so it doesn't make sense... But stranger things have happened...
 
Well in that case we are on the same one!!! Somerset west exchange, not the breaview one in heldervue, but the one near the court...

I can still connect to it when doing a pppoe dial up connection on SAIX, so it doesn't make sense... But stranger things have happened...

I wonder on which exchange Empie is. He's got the same issue with the mweb news server. If the problem has anything to do with the exchange, who has to fix it? mweb or telkom?
 
I'm also in Somerset West! In the central area of town. So maybe it can be telkom? But why does WA and IS still work when I try them?
 
Well in that case we are on the same one!!! Somerset west exchange, not the breaview one in heldervue, but the one near the court...

I can still connect to it when doing a pppoe dial up connection on SAIX, so it doesn't make sense... But stranger things have happened...

I wonder on which exchange Empie is. He's got the same issue with the mweb news server. If the problem has anything to do with the exchange, who has to fix it? mweb or telkom?

I'm also in Somerset West! In the central area of town. So maybe it can be telkom? But why does WA and IS still work when I try them?

Good afternoon Guys

Please provide me tracers and pings to our news server, I would like to establish if you receive a response when pinging or doing a tracer to the server.
 
I'm also in Somerset West! In the central area of town. So maybe it can be telkom? But why does WA and IS still work when I try them?

We should be on the same exchange then. You can check which exchange you are on by using the "Phone Search" option on http://www.broadbandstats.co.za/maps/

I am on the SOMERSET WEST (WSSW) exchange. I have no idea why only Mweb is affected. I have asked mweb to investigate. It seems more apparent now that the issue is not with my account or home setup (router, settings, news reader).

Bottom line is whether it's a telkom or mweb issue, Im paying mweb for a service I'm not getting. I am counting on mweb to find the source of the issue and sort it.
 
Good afternoon Guys

Please provide me tracers and pings to our news server, I would like to establish if you receive a response when pinging or doing a tracer to the server.

I did a tracert to the mweb news server last night and the trace completed successfully. wil do one again tonight and post the results.
 
I did a tracert to the mweb news server last night and the trace completed successfully. wil do one again tonight and post the results.

Please Guiver, we need the pings and tracers to establish if it is congestion. However we have logged the maverick with Telkom already. We normally provide pings and tracers as proof when logging mavericks.
 
We should be on the same exchange then. You can check which exchange you are on by using the "Phone Search" option on http://www.broadbandstats.co.za/maps/

I am on the SOMERSET WEST (WSSW) exchange. I have no idea why only Mweb is affected. I have asked mweb to investigate. It seems more apparent now that the issue is not with my account or home setup (router, settings, news reader).

Bottom line is whether it's a telkom or mweb issue, Im paying mweb for a service I'm not getting. I am counting on mweb to find the source of the issue and sort it.

I seem to be on the GUSTROUW (WGUS) Exchange. Which seems to be interconnected to the WSSW exchange.
Yeah, even if it is telkom...it will be better for mweb to sort it out with them. Telkom will only direct us back to Mweb anyways if we tell them we have an issue with the news server. That's just how they roll...

Mweb Guy, I'll do a ping as soon as I get home. Will let you know...
 
Well my line is with mweb, so either way mweb has to fix it... I just wonder if they have disconnected the ip because of congestion on the exchange? I know when I was on 4mbps I had bad latency in the evenings, most nights... So maybe this is exchange specific... Mweb guy... Please kick some telkom somerset west butt!!!
 
Mweb Guy:

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

1 40 ms 101 ms 102 ms speedtouch.lan [192.168.1.254]
2 * * * Request timed out.
3 23 ms 23 ms 24 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 25 ms 24 ms 23 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 26 ms 27 ms 27 ms tengige0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
6 48 ms 46 ms 50 ms 197-84-4-35.cpt.mweb.co.za [197.84.4.35]
7 52 ms 47 ms 45 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
8 45 ms 46 ms 44 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
9 46 ms 45 ms 45 ms news.mweb.co.za [196.28.78.229]

Trace complete.

Something odd at no.2 very much...
 
Mweb Guy:

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

1 40 ms 101 ms 102 ms speedtouch.lan [192.168.1.254]
2 * * * Request timed out.
3 23 ms 23 ms 24 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 25 ms 24 ms 23 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 26 ms 27 ms 27 ms tengige0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
6 48 ms 46 ms 50 ms 197-84-4-35.cpt.mweb.co.za [197.84.4.35]
7 52 ms 47 ms 45 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
8 45 ms 46 ms 44 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
9 46 ms 45 ms 45 ms news.mweb.co.za [196.28.78.229]

Trace complete.

Something odd at no.2 very much...

Thanks Empie, this is very helpful.
 
@MWEB Guy

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\guiver>ping news.mweb.co.za

Pinging news.mweb.co.za [196.28.78.229] with 32 bytes of data:
Reply from 196.28.78.229: bytes=32 time=54ms TTL=119
Reply from 196.28.78.229: bytes=32 time=49ms TTL=119
Reply from 196.28.78.229: bytes=32 time=31ms TTL=119
Reply from 196.28.78.229: bytes=32 time=85ms TTL=119

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

C:\Users\guiver>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 31 ms 22 ms 13 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178
]
4 20 ms 16 ms 12 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 28 ms 27 ms 34 ms tengige0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
6 84 ms 35 ms 32 ms 197-84-4-35.cpt.mweb.co.za [197.84.4.35]
7 61 ms 40 ms 61 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
8 78 ms 41 ms 37 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
9 49 ms 41 ms 52 ms news.mweb.co.za [196.28.78.229]

Trace complete.

C:\Users\guiver>
 
@MWEB Guy

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\guiver>ping news.mweb.co.za

Pinging news.mweb.co.za [196.28.78.229] with 32 bytes of data:
Reply from 196.28.78.229: bytes=32 time=54ms TTL=119
Reply from 196.28.78.229: bytes=32 time=49ms TTL=119
Reply from 196.28.78.229: bytes=32 time=31ms TTL=119
Reply from 196.28.78.229: bytes=32 time=85ms TTL=119

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

C:\Users\guiver>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 31 ms 22 ms 13 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178
]
4 20 ms 16 ms 12 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 28 ms 27 ms 34 ms tengige0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
6 84 ms 35 ms 32 ms 197-84-4-35.cpt.mweb.co.za [197.84.4.35]
7 61 ms 40 ms 61 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
8 78 ms 41 ms 37 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
9 49 ms 41 ms 52 ms news.mweb.co.za [196.28.78.229]

Trace complete.

C:\Users\guiver>

Thanks Guyver, much appreciated.
 
Any news on this front MwebGuy?

Hi Spyk3r,

We have not received any feedback as yet from Telkom regarding the congestion check on the Somerset exchange.

As soon as Telkom updates us, we will let you know.

Regards,

MWEB Guy
 
Hi Spyk3r,

We have not received any feedback as yet from Telkom regarding the congestion check on the Somerset exchange.

As soon as Telkom updates us, we will let you know.

Regards,

MWEB Guy


How long does telkom usually take to to provide feedback? How about putting some pressure on them? It should be obvious by now that nothing gets done based on request alone, especially when dealing with telkom. I'm tired of this "passing-the_bucket" attitude. Don't tell me telkom hasnt updated you! Phone them and find out what is going on so that you can at least provide some sort of constructive feedback to the frustrated clients that are requesting answers from tech support!
 
How long does telkom usually take to to provide feedback? How about putting some pressure on them? It should be obvious by now that nothing gets done based on request alone, especially when dealing with telkom. I'm tired of this "passing-the_bucket" attitude. Don't tell me telkom hasnt updated you! Phone them and find out what is going on so that you can at least provide some sort of constructive feedback to the frustrated clients that are requesting answers from tech support!

Hi guiver

We'll make sure this gets treated as urgent and get you guys an answer as soon as possible.

If it does turn out to be a congestion related problem we will definitely try and push for this to be addressed, but ultimately we are dependent on Telkom timelines in terms of any exchange upgrades that might be required.

Kind Regards
Will
 
Hi guiver

We'll make sure this gets treated as urgent and get you guys an answer as soon as possible.

If it does turn out to be a congestion related problem we will definitely try and push for this to be addressed, but ultimately we are dependent on Telkom timelines in terms of any exchange upgrades that might be required.

Kind Regards
Will

Thanks for the update, Will :) It is important for me to know that the matter is indeed being addressed and not lying at the bottom of a pile on someones desk. Your efforts in the matter do not go unappreciated.
 
Top
Sign up to the MyBroadband newsletter
X