Mweb and Gmail. Trace provided.

S

SYNERGY

Executive Member
Joined
Jul 13, 2007
Messages
6,050
Reaction score
331
Location
Durban
Hey

My gmail keeps on timing out...

Trace:

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

C:\Users\User>tracert mail.google.com

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

  1     4 ms     4 ms     4 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    47 ms    27 ms    21 ms  41-86-107-6.mweb.co.za [41.86.107.6]
  4    21 ms    20 ms    19 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    23 ms    23 ms    24 ms  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    52 ms    92 ms    36 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
  7   319 ms   269 ms   398 ms  pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]
  8   314 ms   274 ms   263 ms  195.66.224.125
  9   318 ms   263 ms   293 ms  64.233.175.25
 10   327 ms   316 ms   355 ms  209.85.252.45
 11   344 ms   294 ms   331 ms  209.85.248.214
 12   222 ms   222 ms   222 ms  64.233.174.105
 13   252 ms   329 ms   258 ms  74.125.233.23

Trace complete.

C:\Users\User>
Everything else works fine thou... Line 2 is the problem.
Thanks :)
 
SYNERGY said:
Hey

My gmail keeps on timing out...

Trace:

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

C:\Users\User>tracert mail.google.com

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

  1     4 ms     4 ms     4 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    47 ms    27 ms    21 ms  41-86-107-6.mweb.co.za [41.86.107.6]
  4    21 ms    20 ms    19 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    23 ms    23 ms    24 ms  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    52 ms    92 ms    36 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
  7   319 ms   269 ms   398 ms  pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]
  8   314 ms   274 ms   263 ms  195.66.224.125
  9   318 ms   263 ms   293 ms  64.233.175.25
 10   327 ms   316 ms   355 ms  209.85.252.45
 11   344 ms   294 ms   331 ms  209.85.248.214
 12   222 ms   222 ms   222 ms  64.233.174.105
 13   252 ms   329 ms   258 ms  74.125.233.23

Trace complete.

C:\Users\User>
Everything else works fine thou... Line 2 is the problem.
Thanks :)
Click to expand...

Hi SYNERGY

Please note that the 2nd hop reflects that the problem is closer to the remote end; probably your firewall or it could also be your line/exchange (however you report no other problems). The tracer does complete though, it would have been a problem if it continued to time out. Please also DM me your MWEB email address and what your DNS settings are.

Kind regards,
MWEB Guy
 
I don't see any problems there, the fact that line 2 doesn't have any data and times out simply means whatever device that is, isn't responding to ICMP packets. As MWEB Guy points out the trace completes successfully so the packets are getting all the way to the last hop.
 
His traceroute shows 2 things,

1. His line's latency spike a lot.

2. He is getting directed to the wrong google data centre if you ask me.

Code: 
root@heaven-htpc:~# traceroute 74.125.233.23
traceroute to 74.125.233.23 (74.125.233.23), 30 hops max, 60 byte packets
 1  router.heaven.za.net (10.0.0.1)  0.203 ms  0.288 ms  0.358 ms
 2  wblv-ip-esr-3.ipnet.wa.co.za (41.185.83.1)  7.210 ms  9.605 ms  12.272 ms
 3  vl108.cr.gw.cpt.za.wa.co.za (196.220.59.238)  16.203 ms  18.486 ms  21.111 ms
 4  41.185.0.254 (41.185.0.254)  23.314 ms  25.790 ms  28.699 ms
 5  vl140.er.cinx.cpt.za.wa.co.za (41.185.1.5)  34.371 ms  35.286 ms  37.767 ms
 6  198.32.214.41 (198.32.214.41)  38.953 ms  39.041 ms  41.473 ms
 7  * * *
 8  74.125.233.23 (74.125.233.23)  46.791 ms  47.957 ms  49.689 ms
 
another concern is the jump from 39ms to 390ms between hops 6 and 7. Its possible that pos-1-2-0.lon-up-1.mweb.co.za is under a bit of strain and dropping packets. Repeat this trace a few times and see if it is so.
 
All other websites load fine thou :/

Its a nightmare trying to Telkom that something is wrong with their exchange... I'll try and get them to change my port:

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

C:\Users\User>tracert mail.google.com

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

  1     4 ms     5 ms     5 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    68 ms    66 ms    65 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4    36 ms    33 ms    51 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    44 ms    38 ms    55 ms  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   119 ms    99 ms   104 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.2
10]
  7   304 ms   263 ms   260 ms  pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]

  8   269 ms   334 ms   266 ms  195.66.224.125
  9   301 ms   292 ms   291 ms  64.233.175.25
 10   339 ms   388 ms   336 ms  209.85.252.45
 11   281 ms   326 ms   287 ms  209.85.248.214
 12   245 ms   236 ms   264 ms  64.233.174.105
 13   235 ms   237 ms   234 ms  74.125.233.21

Trace complete.

C:\Users\User>
 
My Google Chat kept on timing out on Neotel due to our DNS being queried from 8.8.8.8 and not from the local Neotel DNS servers.

At my parent's home I'm using the 196.28.182.20 Mweb DNS server with their Mweb uncapped 384kbps connection, which gives me an international GMail IP address.
Code: 
Name:    googlemail.l.google.com
Addresses:  74.125.230.120
          74.125.230.117
          74.125.230.118
          74.125.230.119
Aliases:  mail.google.com
Code: 
 # ADDRESS                                 RT1   RT2   RT3   STATUS                        
 1 d-link-adsl-router.tuis                 1ms   1ms   1ms                                 
 2 41-132-44-1.dsl.mweb.co.za              23ms  24ms  22ms                                
 3 te1-1-0.502.cpt-ipc-1.mweb.co.za        24ms  23ms  23ms                                
 4 gi0-2-cpt-cinx.mweb.co.za               23ms  23ms  23ms                                
 5 198.32.214.41                           26ms  24ms  24ms                                
 6 209.85.248.215                          180ms 178ms 179ms <MPLS:L=709878,E=4>           
 7 209.85.252.44                           221ms 223ms 221ms                               
 8 209.85.251.56                           222ms 222ms 221ms                               
 9 74.125.230.120                          176ms 175ms 176ms
 
That is strange. It looks like M-Web peers with Google at CINX, but they are not routing their JHB customers to that peering session, and now it looks like their JHB clients are routed via International back to Cape Town for Google Cape Town.

Pada, try tracing 74.125.233.21 via the Cape Town based M-Web connection, it should look very local then. That whole /24 is in Cape Town, as well as 64.233.174.0/24
 
stricken said:
another concern is the jump from 39ms to 390ms between hops 6 and 7. Its possible that pos-1-2-0.lon-up-1.mweb.co.za is under a bit of strain and dropping packets. Repeat this trace a few times and see if it is so.
Click to expand...

Nah, 6 is the traffic leaving SA and then 7 is it arriving in London, pos-1-2-0.LON-up-1.mweb.co.za (LON = London) tengige0-3-1-0.MID-up-1.mweb.co.za (MID = Probably Midrand)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X