MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
Hi, I am unable to connect to news.mweb.co.za. It was working brilliantly ever since I opened my mweb account... I get a connection refused error, anyone else getting this?

Server: news.mweb.co.za

Status: Enabled

# Connections: Failed to connect: (10060, "(10061, 'Connection refused')") [email protected]:119
 
Hi, I am unable to connect to news.mweb.co.za. It was working brilliantly ever since I opened my mweb account... I get a connection refused error, anyone else getting this?

Good evening Chris_H, please ping the news server and use the IP you obtain from there (test).
 
Good evening Chris_H, please ping the news server and use the IP you obtain from there (test).

Thanks for the reply but I get the same error

Server: news.mweb.co.za

Status: Enabled

# Connections: Failed to connect: (10060, "(10061, 'Connection refused')") [email protected]:119


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

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

1 4 ms 2 ms 12 ms 192.168.0.1
2 12 ms 9 ms 12 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 12 ms 12 ms 9 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178
]
4 10 ms 9 ms 10 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 14 ms 15 ms 15 ms tengige0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
6 11 ms 2947 ms 11 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
7 12 ms 10 ms 13 ms is.cinx.net.za [196.223.22.10]
8 15 ms 15 ms 12 ms core2a-ctn-gi0-1.ip.isnet.net [168.209.2.6]
9 31 ms 33 ms 34 ms 168.209.100.213
10 34 ms 34 ms 34 ms core1b-rba-te2-0-1.ip.isnet.net [168.209.1.181]

11 34 ms 34 ms 34 ms 168.209.98.66

Trace complete.

C:\Users\ChrisH>
 
Thanks for the reply but I get the same error

Chris may I delete your current session, I would like to establish if you have the same problem after connecting with a new IP?
 
Yes that will be great :)

I have deleted your session, recreated your Telkom port and reauthenticated your account. Please reboot your router for 5 to 10 min and let me know if you are still not able to connect to the news server.
 
I have deleted your session, recreated your Telkom port and reauthenticated your account. Please reboot your router for 5 to 10 min and let me know if you are still not able to connect to the news server.

Thanks will do so now... ignore the PM, you are way too fast for me lol
 
Hey Mweb guy I need some help. I had problems and thought it was my line but I switched over to my Do broadband bandwidth and was able to play and browse fine but as soon as I switched back to Mweb I have all sorts of dropouts. It works fine for a while and then everything goes dead but I'm still connected according to my router.

Edit: I've also just found out that I'm not receiving certain email messages.
 
Last edited:
Hey Mweb guy I need some help. I had problems and thought it was my line but I switched over to my Do broadband bandwidth and was able to play and browse fine but as soon as I switched back to Mweb I have all sorts of dropouts. It works fine for a while and then everything goes dead but I'm still connected according to my router.

Edit: I've also just found out that I'm not receiving certain email messages.

Hi MJ INC,

I would like to look into this from our side. Please can you PM me your MWEB account details in order for me to do so.

Kind regards,
MWEB Guy
 
Hi MWEB Guy I seem to be having the same issues as others. Initially contacted telkom to check the line. All is well on their side, I hope! :o

I'm getting a connection, but no or intermittent data! :wtf:

C:\>tracert www.mweb.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 12 ms 12 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 18 ms 17 ms 18 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 32 ms 32 ms 32 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 * * * Request timed out.
9 37 ms 33 ms 34 ms www.mweb.co.za [196.2.63.110]

Trace complete.


C:\>tracert www.google.com

Tracing route to www.l.google.com [74.125.233.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 11 ms 12 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 11 ms 15 ms 12 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 33 ms 33 ms 32 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
8 * * * Request timed out.
9 35 ms 35 ms 34 ms 64.233.174.105
10 35 ms 34 ms 34 ms cpt01s01-in-f19.1e100.net [74.125.233.19]

Trace complete.


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

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Request timed out.
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Request timed out.

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms
 
Hi MWEB Guy I seem to be having the same issues as others. Initially contacted telkom to check the line. All is well on their side, I hope! :o

I'm getting a connection, but no or intermittent data! :wtf:

C:\>tracert www.mweb.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 12 ms 12 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 18 ms 17 ms 18 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 32 ms 32 ms 32 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 * * * Request timed out.
9 37 ms 33 ms 34 ms www.mweb.co.za [196.2.63.110]

Trace complete.


C:\>tracert www.google.com

Tracing route to www.l.google.com [74.125.233.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 11 ms 12 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 11 ms 15 ms 12 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 33 ms 33 ms 32 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
8 * * * Request timed out.
9 35 ms 35 ms 34 ms 64.233.174.105
10 35 ms 34 ms 34 ms cpt01s01-in-f19.1e100.net [74.125.233.19]

Trace complete.


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

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Request timed out.
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Request timed out.

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms

Good evenig Blender1, Your Telkom Line readings seem fine. However your tracers time out on the 2nd hop, this normally means that the problem is closer to the remote end. (remote end itself, Telkom Line or DSLAM).

Lets reset and reconfigure your router (password required for this) and I will recreate your Telkom port to verify if that makes a difference.
 
Ok. Thanx. I've reset and reloaded the settings on my router. Will check the connection.
Thanx for the help

Its a pleasure, please keep me informed though.

Kind regards,
MWEB guy
 
OK! Looking much better! At least I can actually open a site or two now :D

C:\>tracert www.mweb.co.za

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

1 2 ms 5 ms 3 ms 192.168.1.1
2 1516 ms 1711 ms 1865 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1]
3 1715 ms 1676 ms 1706 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 * * * Request timed out.
5 40 ms 37 ms 40 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 35 ms 35 ms 35 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]
7 * 36 ms 34 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 * * * Request timed out.
9 36 ms 38 ms 37 ms www.mweb.co.za [196.2.63.110]

Trace complete.


C:\>tracert www.google.com

Tracing route to www.l.google.com [74.125.233.20]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.1
2 14 ms * 13 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1]
3 12 ms 13 ms 13 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 * * * Request timed out.
5 * * * Request timed out.
6 61 ms 86 ms 56 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]
7 85 ms 34 ms 33 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
8 * * * Request timed out.
9 34 ms 34 ms 35 ms 64.233.174.105
10 35 ms 34 ms 36 ms cpt01s01-in-f20.1e100.net [74.125.233.20]

Trace complete.


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=2440ms TTL=119
Reply from 196.2.63.110: bytes=32 time=2353ms TTL=119
Reply from 196.2.63.110: bytes=32 time=2319ms TTL=119
Reply from 196.2.63.110: bytes=32 time=2055ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2055ms, Maximum = 2440ms, Average = 2291ms
 
Internet really slow at the moment... I'm barely getting 512 speeds on a 1meg line. MWEB Guy, what's up? Is it just me??
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X