-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: If you were buying a TV today, which brand would you choose?
MWEB Uncapped ADSL Feedback - Part 2
- Thread starter rpm
- Start date
- Status
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Good Morning Viper87, are you still having a problem this morning? If so, to see if the problem is being caused by your exchange. There is a little test you can do, provide tracer results to local and international websites. If the latency is high on the first or second hope, you know the problem is closer to the remote end.
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Good Morning SSung
Please note that your line is syncing at 448 kbps and your attenuation is still extremely high 60.5 dB
I also cannot seem to adjust your line speed at all at the moment. I will have to log another line fault to verify why I cannot adjust your line speeds.
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Could this be because of a congested exchange?
Good Morning kdawg, please provide me your MWEB email address via private messaging and I will let your line and account from my end.
To see if the problem is being caused by your exchange (congestion). There is a little test you can do, provide tracer results to local and international websites. If the latency is high on the first or second hope, you know the problem is closer to the remote end.
kimbo
Expert Member
Tracing route to www.bbc.net.uk [212.58.244.68]
over a maximum of 30 hops:
1 216 ms 209 ms 213 ms bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
Trace complete.
Tracing route to www.google.com [74.125.233.16]
over a maximum of 30 hops:
1 49 ms 49 ms 49 ms cpt01s01-in-f16.1e100.net [74.125.233.16]
Trace complete.
Pinging www.google.com [74.125.233.16] with 32 bytes of data:
Reply from 74.125.233.16: bytes=32 time=48ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Ping statistics for 74.125.233.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 49ms, Average = 48ms
Morning Mweb Guy
This is what i get. I still have the same. The lone is fine for a wile (out 5min) then it dies. HTTP data seems to be lost but NNTP still runs.
Like i said yesterday i tried IE, FF and my phone via wifi and all of them does the same
over a maximum of 30 hops:
1 216 ms 209 ms 213 ms bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
Trace complete.
Tracing route to www.google.com [74.125.233.16]
over a maximum of 30 hops:
1 49 ms 49 ms 49 ms cpt01s01-in-f16.1e100.net [74.125.233.16]
Trace complete.
Pinging www.google.com [74.125.233.16] with 32 bytes of data:
Reply from 74.125.233.16: bytes=32 time=48ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Reply from 74.125.233.16: bytes=32 time=49ms TTL=52
Ping statistics for 74.125.233.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 49ms, Average = 48ms
Morning Mweb Guy
This is what i get. I still have the same. The lone is fine for a wile (out 5min) then it dies. HTTP data seems to be lost but NNTP still runs.
Like i said yesterday i tried IE, FF and my phone via wifi and all of them does the same
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Morning, your ping test results are not that bad.
Please provide me the complete tracers...
kimbo
Expert Member
Hi
That is what i get, i did another one
Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:
1 593 ms 544 ms 441 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]
Trace complete.
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Are you doing the tracers via command prompt?
kimbo
Expert Member
Yes
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\kimbo>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.93]
over a maximum of 30 hops:
1 217 ms 207 ms 208 ms bbc-vip014.cwwtf.bbc.co.uk [212.58.246.93]
Trace complete.
C:\Users\kimbo>
That is the full screen
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Please do the tracer to bbc.uk.net
kimbo
Expert Member
Tracing route to fwd3.hosts.co.uk [85.233.160.22]
over a maximum of 30 hops:
1 213 ms 206 ms 207 ms fwd0.hosts.co.uk [85.233.160.22]
Trace complete.
Last edited:
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Please run a netstat -a -b -n
@MWEB Guy,
Sorry if this is the incorrect place to ask. Possibly it's been ask already.
Now that MWEB is also part of the 40Mbps trial, how do one apply for this? I'm on one the MSAN exchanges. It's actually less then 100 meters from me.
Could you please advise?
Many thnx in advance.
Sorry if this is the incorrect place to ask. Possibly it's been ask already.
Now that MWEB is also part of the 40Mbps trial, how do one apply for this? I'm on one the MSAN exchanges. It's actually less then 100 meters from me.
Could you please advise?
Many thnx in advance.
kimbo
Expert Member
C:\Users\kimbo>netstat -a -b -n
The requested operation requires elevation.
This is what i get
kimbo
Expert Member
C:\Windows\system32>netstat -a -b -n
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
[Skype.exe]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
[Skype.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:2968 0.0.0.0:0 LISTENING
[EEventManager.exe]
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:5938 0.0.0.0:0 LISTENING
[TeamViewer_Service.exe]
TCP 0.0.0.0:39667 0.0.0.0:0 LISTENING
[Skype.exe]
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
[wininit.exe]
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
eventlog
[svchost.exe]
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
Schedule
[svchost.exe]
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49311 0.0.0.0:0 LISTENING
[services.exe]
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
[mDNSResponder.exe]
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING
[TeamViewer_Service.exe]
TCP 127.0.0.1:5939 127.0.0.1:49310 ESTABLISHED
[TeamViewer_Service.exe]
TCP 127.0.0.1:8080 0.0.0.0:0 LISTENING
[SABnzbd.exe]
TCP 127.0.0.1:49273 127.0.0.1:49274 ESTABLISHED
[TeamViewer.exe]
TCP 127.0.0.1:49274 127.0.0.1:49273 ESTABLISHED
[TeamViewer.exe]
TCP 127.0.0.1:49310 127.0.0.1:5939 ESTABLISHED
[TeamViewer.exe]
TCP 127.0.0.1:53630 127.0.0.1:53631 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:53631 127.0.0.1:53630 ESTABLISHED
[firefox.exe]
TCP 192.168.0.102:139 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 192.168.0.102:49211 74.125.233.4:80 CLOSE_WAIT
[googletalk.exe]
TCP 192.168.0.102:49815 199.47.216.173:443 CLOSE_WAIT
[Dropbox.exe]
TCP 192.168.0.102:50858 2.19.119.117:80 CLOSE_WAIT
[ToolbarUpdater.exe]
TCP 192.168.0.102:52503 173.194.66.108:993 TIME_WAIT
TCP 192.168.0.102:52628 175.41.14.4:80 CLOSE_WAIT
[KiesTrayAgent.exe]
TCP 192.168.0.102:54150 2.19.119.117:80 CLOSE_WAIT
[vprot.exe]
TCP 192.168.0.102:54151 197.80.130.11:80 CLOSE_WAIT
[vprot.exe]
TCP 192.168.0.102:54377 74.125.233.2:80 TIME_WAIT
TCP 192.168.0.102:54453 74.125.233.8:80 TIME_WAIT
TCP 192.168.0.102:54457 173.194.66.108:993 ESTABLISHED
[Gmail Notifier.exe]
TCP 192.168.0.102:54458 74.125.233.31:443 TIME_WAIT
TCP 192.168.0.102:54459 74.125.233.31:443 ESTABLISHED
[firefox.exe]
TCP 192.168.0.102:54489 173.252.101.16:443 ESTABLISHED
[firefox.exe]
TCP 192.168.0.102:54490 184.75.168.149:80 TIME_WAIT
TCP 192.168.0.102:54498 197.80.130.25:80 TIME_WAIT
TCP 192.168.0.102:54565 197.80.128.37:443 TIME_WAIT
TCP 192.168.0.102:54566 197.80.128.37:443 ESTABLISHED
[firefox.exe]
TCP 192.168.0.102:59373 65.55.223.23:40006 ESTABLISHED
[Skype.exe]
TCP 192.168.0.102:59378 64.4.61.209:443 ESTABLISHED
[Skype.exe]
TCP 192.168.0.102:59379 173.194.78.125:5222 ESTABLISHED
[googletalk.exe]
TCP 192.168.0.102:59387 199.47.216.149:80 ESTABLISHED
[Dropbox.exe]
TCP 192.168.0.102:59393 78.141.179.18:12350 ESTABLISHED
[Skype.exe]
TCP 192.168.0.102:59508 199.47.216.178:443 CLOSE_WAIT
[Dropbox.exe]
TCP 192.168.0.102:63298 194.54.81.54:5938 ESTABLISHED
[TeamViewer_Service.exe]
TCP [::]:135 [::]:0 LISTENING
RpcSs
[svchost.exe]
TCP [::]:445 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:2869 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:5357 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:49152 [::]:0 LISTENING
[wininit.exe]
TCP [::]:49153 [::]:0 LISTENING
eventlog
[svchost.exe]
TCP [::]:49154 [::]:0 LISTENING
Schedule
[svchost.exe]
TCP [::]:49155 [::]:0 LISTENING
[lsass.exe]
TCP [::]:49311 [::]:0 LISTENING
[services.exe]
TCP [::1]:8080 [::]:0 LISTENING
[SABnzbd.exe]
UDP 0.0.0.0:443 *:*
[Skype.exe]
UDP 0.0.0.0:2968 *:*
[EEventManager.exe]
UDP 0.0.0.0:3702 *:*
EventSystem
[svchost.exe]
UDP 0.0.0.0:3702 *:*
EventSystem
[svchost.exe]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:9000 *:*
[Vid.exe]
UDP 0.0.0.0:9001 *:*
[Vid.exe]
UDP 0.0.0.0:39667 *:*
[Skype.exe]
UDP 0.0.0.0:61607 *:*
[mDNSResponder.exe]
UDP 0.0.0.0:61792 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:63753 *:*
EventSystem
[svchost.exe]
UDP 127.0.0.1:1900 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:49826 *:*
[NLClientApp.exe]
UDP 127.0.0.1:54662 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:54837 *:*
[Skype.exe]
UDP 127.0.0.1:61609 *:*
[Gmail Notifier.exe]
UDP 127.0.0.1:61610 *:*
[sidebar.exe]
UDP 127.0.0.1:61803 *:*
[Skype.exe]
UDP 192.168.0.102:137 *:*
Can not obtain ownership information
UDP 192.168.0.102:138 *:*
Can not obtain ownership information
UDP 192.168.0.102:1900 *:*
SSDPSRV
[svchost.exe]
UDP 192.168.0.102:5353 *:*
[mDNSResponder.exe]
UDP 192.168.0.102:54661 *:*
SSDPSRV
[svchost.exe]
UDP [::]:3702 *:*
EventSystem
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:3702 *:*
EventSystem
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:61608 *:*
[mDNSResponder.exe]
UDP [::]:61793 *:*
FDResPub
[svchost.exe]
UDP [::]:63754 *:*
EventSystem
[svchost.exe]
UDP [::1]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [::1]:5353 *:*
[mDNSResponder.exe]
UDP [::1]:54660 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::29c1:7255:c180:228d%10]:546 *:*
Dhcp
[svchost.exe]
UDP [fe80::29c1:7255:c180:228d%10]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::29c1:7255:c180:228d%10]:54659 *:*
SSDPSRV
[svchost.exe]
C:\Windows\system32>
This is if i run as admin
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Good Morning, please note that this is still in the trial stages. Once the testing has been completed we will be able to provide you more feedback with regards to it.
- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
Looking at these results, you have allot of data intensive programmes running at the same time. This will impact on your experience. YOu only have a 1mb account and it seems like you have multiple devices active.
you could try closing some of these programmes, like drop box, skype, your nntp downloads or team-viewer and test the traffic individually.
Thank you for your prompt response.
Just to clarify. Are you saying that MWEB is testing this internally before asking their current subscribers to test? Or do you mean it's being tested by users already and will rolled out as service when that is done?
- Status