FIX for telkom sites not opening on LTE uncapped.

B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
Change your APN from "internet" to.. "TelkomInternet"...everything seems to work from there on.
 
B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
muPvVjo.png
 
T

Tartarusx

Member
Joined
Nov 6, 2012
Messages
24
IT WORKS! thanks! I can connect to origin and battlefield 1 servers again!

Thank you for sharing!
 
B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
Well bugger.. seems some sites still do not work!
 
T

Tartarusx

Member
Joined
Nov 6, 2012
Messages
24
Same.. worked for about 2 hours for me now its back to the same. Refreshed the site and now it's timing out again.
 
R

RJJohnson

New Member
Joined
Nov 5, 2014
Messages
4
Guys what worked for me on my PC is to change the DNS server to Googles.
Primary - 8.8.8.8
Secondary 8.8.4.4
 
R

ranger

Expert Member
Joined
May 2, 2007
Messages
2,062
Please also try the Telkom Internet anycast DNS:
105.225.0.1
105.225.0.2

We suspect it may be related to using DNS servers in Durban resulting in users hitting a CDN cluster in Durban that may result in compatibility issues.

Using Google DNS would change that because Google's closest is Johanmesburg.

Our Anycast DNS isn't yet in Durban, so should also work, but may be better for you because of other CDNs we host.

If this resolves the issue for now, we may consider making this the default DNS.
 
B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
Nope, that doesn't fix it, didn't think it would but i tried it anyway.
 
B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
Using 105.225.0.1
105.225.0.2

My ip is 41.164.205.x

Tracing to voxtelecom.co.za

C:\Users\User1>tracert -w 100 voxtelecom.co.za

Tracing route to voxtelecom.co.za [196.41.6.140]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.2.15
2 * * * Request timed out.
3 35 ms 20 ms 21 ms 105-187-252-217.ti-sen.telkomsa.net [105.187.252.217]
4 43 ms 23 ms 19 ms 105.229.0.13
5 48 ms 42 ms 50 ms 105.187.252.46
6 50 ms 42 ms 41 ms 105.187.252.46
7 58 ms * 43 ms vox.ixp.capetown [196.10.140.69]
8 65 ms 41 ms 40 ms 41.193.120.41
9 65 ms 54 ms 55 ms 41.193.106.105
10 53 ms * 57 ms 41.193.106.97
11 61 ms 45 ms 46 ms 41.193.106.101
12 55 ms 45 ms 50 ms 41.193.32.134
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
B

bboy

Expert Member
Joined
Jan 21, 2005
Messages
3,230
Using ADSL

My ip is 105.226.9.x

C:\Users\User1>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Users\User1>tracert -w 100 voxtelecom.co.za

Tracing route to voxtelecom.co.za [196.41.6.140]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms 192.168.2.12
2 * * * Request timed out.
3 41 ms 37 ms 40 ms 105.187.252.77
4 43 ms 61 ms 50 ms 105-187-252-78.ti-sen.telkomsa.net [105.187.252.78]
5 46 ms 51 ms 59 ms 105.229.0.29
6 74 ms * 91 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
7 50 ms 58 ms 67 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
8 57 ms 55 ms 54 ms vox.ixp.capetown [196.10.140.69]
9 92 ms * 87 ms 41.193.120.41
10 78 ms 93 ms 94 ms 41.193.106.105
11 60 ms 62 ms * 41.193.106.97
12 85 ms 94 ms 70 ms 41.193.106.101
13 59 ms 59 ms * 41.193.32.134
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Website DOES load on ADSL
 
R

ranger

Expert Member
Joined
May 2, 2007
Messages
2,062
The point of the DNS change was to see if you get sent (for akamai sites) an Akamai cluster besides the one Vox hosts in Durban, because there may be a problem at Vox in Durban.

Testing Vox with the DNS change doesn't help for that aspect ...

You may want to compare e.g. https://www.emirates.com . That is one we used today troubleshooting with a customer. With SAIX Durban DNS they get 104.94.82.217 which works for HTTP (well, small HTTP such as the redirect to HTTPS) but not HTTPS (or not with larger packets)


If I query that on 105.225.0.1 I get 2.21.234.224 which is on our network, but I can't see if it works for HTTPS over LTE.
 
Last edited:
D

dotcat

Expert Member
Joined
Nov 18, 2005
Messages
1,076
to emirates:


(2.21.234.224), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 4.521 ms 7.561 ms 11.457 ms
2 192.168.2.1 (192.168.2.1) 3.305 ms 1.379 ms 1.297 ms
3 * * *
4 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 24.796 ms 22.335 ms 19.767 ms
5 cust-aggr-2.east.telkomsa.net (105.229.0.13) 20.848 ms 30.671 ms 36.668 ms
6 105.187.249.217 (105.187.249.217) 37.073 ms 36.123 ms 36.739 ms
7 cen-pr-02-te0-7-0-21-vl11.net.telkomsa.net (105.187.249.114) 35.021 ms 42.363 ms 27.875 ms
8 2.21.234.224 (2.21.234.224) 33.727 ms 32.213 ms 30.279 ms

also loads in browser.
 
You must log in or register to reply here.
Top