-- What could cause this??

3

3G_

Active Member
Joined
Jul 18, 2005
Messages
95
Reaction score
0
Hi everyone!

I have a serious problem and I have NO clue what could cause this:

Some of my domains is resident on an international server, one of these domains: www.teen.co.za

I can download my pop3 email, ping the domain & access the control panel from iBurst & GPRS connections, but from my Telkom ADSL line I cannot access my email, cannot ping the site and cannot access the control panel.

When I use the dsl-cache proxy from saix, I can however, access the control panel. Weird??

Some other peeps have tested the mail for me on Mweb, Polka, etc etc (Im on Atlantic) and everyone gets the same error.

This means the problem lies with Telkom? As iBurst & GPRS works...

Anyone have any ideas PLEASE?? :confused:

When I ping the domain on telkom adls I get time out errors.... with gprs & iburst it gives 0% loss!

Thanks
Jacques


----
 
By the way:
TIP: If you experience the same problem and you MUST read your email. If your host supply a webmail facility for reading email via a browser, that works. Downloading with POP server do not work but your webmail facility works for some strange reason.
 
yip Ive seen the other posts and now know its Telkom thats the problem... eish.. lol.

mail2web.com works for my emails... and when I use a SAIX proxy server I can access my domain control panels!
 
1 esr (143.160.32.200) 4.268 ms 0.218 ms 0.178 ms
2 fw (143.160.64.1) 0.431 ms 0.496 ms 0.450 ms
3 igs (143.160.4.2) 1.032 ms 0.767 ms 0.695 ms
4 bb-puk-mc-ipnet.uni.net.za (155.232.207.69) 8.653 ms 9.705 ms 9.570 ms
5 tnet-0001-telkombell-ce-3.uni.net.za (155.232.210.6) 28.971 ms 28.292 ms 29.261 ms
6 int-puk-mc-ipnet.uni.net.za (155.232.200.129) 29.925 ms 28.339 ms 45.550 ms
7 wblv-ip-lir-1-wan.telkom-ipnet.co.za (196.25.251.149) 28.046 ms 58.452 ms 28.499 ms
8 ny-ip-dir-globalc-pos-5-0.telkom-ipnet.co.za (196.43.9.137) 297.963 ms 286.010 ms 276.961 ms
9 nyk-i3-geth3-2.telia.net (213.248.82.237) 273.284 ms 266.909 ms 272.927 ms
10 nyk-bb1-link.telia.net (213.248.82.145) 266.326 ms 266.529 ms 269.298 ms
11 nyk-b2-link.telia.net (213.248.82.206) 263.532 ms 267.108 ms 277.328 ms
12 wbs-112980-nyk-b1.c.telia.net (213.248.83.106) 283.906 ms 273.817 ms 303.173 ms
13 65.98.0.213 (65.98.0.213) 295.700 ms 288.073 ms 272.033 ms
14 65.98.58.50 (65.98.58.50) 280.598 ms 284.502 ms 280.688 ms
15 ns1.za-phphosting.com (65.98.75.110) 278.562 ms 274.096 ms 286.348 ms
 
On my side it looks like this

Tracing route to digiprop.co.za [65.98.75.110]
over a maximum of 30 hops:

1 19 ms 21 ms 20 ms dsl-145-128-01.telkomadsl.co.za [165.145.128.1]

2 17 ms 19 ms 21 ms 196.43.24.13
3 18 ms 21 ms 18 ms tbnb-ip-esr-2-gig-6-1-0-615.telkom-ipnet.co.za [
196.43.10.122]
4 343 ms 344 ms 345 ms ny-ip-dir-globalc-pos-7-0.telkom-ipnet.co.za [19
6.43.9.149]
5 343 ms 345 ms 346 ms nyk-i3-geth3-2.telia.net [213.248.82.237]
6 358 ms 342 ms 343 ms nyk-bb1-link.telia.net [213.248.82.145]
7 346 ms 342 ms 344 ms nyk-b2-link.telia.net [213.248.82.206]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.
 
Please assist:

Call your bandwidth ISP and request them to log a fault with Telkom/SAIX/TelkomSA.

The more people who do it, the better.


They will need your ADSL line number and a description of the error with traceroutes etc.

I'm having the same problem, and AXXESS was willing to send the problem as if it is their own.
 
The problem is on Telkom's DSL side it seems as I used PUK's online traceroute utility which found your site successfully through the Telkom backbone above.

But you really need to escalate the issue beyond a clueless helpdesk minion and give them both traces and ask them to explain why it is so.

It sometimes pays to have a local ISP hosting provider as they know who they can contact in Telkom when such issues arise.
 
Last edited:
Yesterday the Telkom chappy could also not find my site when he did a tracert. The ADSL guy then said that he will transfer me back to the Telkom ISP and I must ask them to log a fault. But, after holding the line for 30 frustrating minutes the idiot on the other end was to thick to know what i was talking about. So even if I wanted to report a fault I could not. So how the hell do you report a fault to these people if their staff are to thick to understand what you talk about???
 
Tracert

Here is another one, my Boet is working in JHB and I am in Pretoria. So he did a tracert to his site, also on my server and he could find it. I then did one to the same domain and could not find it. I first post his results from JHB using mweb adsl and then my results from Pretoria using Telkom adsl:
Tracing route to mail.intelli.co.za [65.98.75.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 149 ms 136 ms 134 ms 192.168.1.202
3 147 ms 139 ms 135 ms 192.168.1.3
4 161 ms 143 ms 144 ms dsl-146-0-01.telkomadsl.co.za [165.146.0.1]
5 158 ms 145 ms 145 ms rndf-ip-er-2-fe-12-0-1-610.telkom-ipnet.co.za [196.43.10.181]
6 * * * Request timed out.
7 496 ms 483 ms 483 ms ny-ip-dir-globalc-pos-5-0.telkom-ipnet.co.za [196.43.9.137]
8 495 ms 485 ms 485 ms nyk-i3-geth3-2.telia.net [213.248.82.237]
9 502 ms 484 ms 485 ms nyk-bb1-link.telia.net [213.248.82.145]
10 499 ms 486 ms 486 ms nyk-b2-link.telia.net [213.248.82.206]
11 502 ms 488 ms 487 ms wbs-112980-nyk-b1.c.telia.net [213.248.83.106]
12 497 ms 490 ms 485 ms 65.98.0.213
13 499 ms 491 ms 494 ms 65.98.58.50
14 497 ms 492 ms 490 ms ns1.za-phphosting.com [65.98.75.110]

Trace complete.

Now pretoria results
Tracing route to mail.intelli.co.za [65.98.75.110]
over a maximum of 30 hops:

1 20 ms 21 ms 21 ms dsl-145-128-01.telkomadsl.co.za [165.145.128.1]

2 20 ms 26 ms 21 ms 196.43.24.13
3 20 ms 21 ms 20 ms
tbnb-ip-esr-2-gig-6-1-0-615.telkom-ipnet.co.za [
196.43.10.122]
4 342 ms 373 ms 343 ms
ny-ip-dir-globalc-pos-7-0.telkom-ipnet.co.za [19
6.43.9.149]
5 346 ms 342 ms 515 ms nyk-i3-geth3-2.telia.net [213.248.82.237]
6 342 ms 345 ms 343 ms nyk-bb1-link.telia.net [213.248.82.145]
7 342 ms 344 ms 357 ms nyk-b2-link.telia.net [213.248.82.206]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13
 
Cannot access US mail server ...

Hi,
We have the same problem as Piet. We have not been able to collect mail
from 65.98.60.250 since 2.15am on 19 July.
We have also logged a fault with our ISP - Webafrica and they have passed it onto Saix??? Setting the browser to proxy : cache.saix.co.za Port 8080 has allowed us to log onto webmail and get our messages.
Our tracert also stops at xxx.telia.net
Who takes responsibilty for faults like this? It is day 2 and we are still waiting???
Regards
Bertie
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X