Unable to connect to some sites via Exetel

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
terryc
Posts: 33
Joined: Mon Jan 24, 2005 6:29 pm

Re: Unable to connect to some sites via Exetel

Post by terryc » Wed Feb 04, 2009 12:40 am

I posted my results over in the thread I started under ADSL 1 connection issues

maverick36
Posts: 27
Joined: Thu Jan 29, 2009 9:07 am
Location: Brisbane

Re: Unable to connect to some sites via Exetel

Post by maverick36 » Wed Feb 04, 2009 12:49 am

In both cases the IP works, the domain name does not.
Neither works. I agree this appears to be a different problem to the above two. With tracert, the domain name clearly resolves correctly to an IP address, but we never get to our destination. As I said though, this site does work from my work internet connection, and you can see for yourself that it works if you go through a proxy server (such as http://hidemyass.com) that the network is accessible. So there is still something fishy going on here.

JasonM

Re: Unable to connect to some sites via Exetel

Post by JasonM » Wed Feb 04, 2009 1:18 am

I've asked our sys admin to look into the issues, obviously this isn't going to happen at 1.18am.

Berty
Posts: 41
Joined: Tue Apr 06, 2004 4:22 pm
Location: Armidale

Re: Unable to connect to some sites via Exetel

Post by Berty » Wed Feb 04, 2009 8:57 am

I was having intermittent network time-outs last night and browsing was not snappy as usual. I thought it might be my crappy Netcomm modem/Router. But I guess there was some DNS issue. Will see if it resolves tonight.

Berty
Posts: 41
Joined: Tue Apr 06, 2004 4:22 pm
Location: Armidale

Re: Unable to connect to some sites via Exetel

Post by Berty » Wed Feb 04, 2009 5:50 pm

OK, here is the update. Some sites still don't resolve and the connections times out. Sites are completely random. Even Exetel site times out but after hitting F5 it resolves and loads quickly.
Here is the ping results:

Pinging exetel.com.au [220.233.0.9] with 32 bytes of data:

Ping statistics for 220.233.0.9:
Packets: Sent = 111, Received = 108, Lost = 3 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 355ms, Average = 29ms

As you can see I am getting 2% packet loss but I am not sure if this is the cause.

And here is the trace to Google, which is not promissing:


Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 23 ms 24 ms 10.0.1.25
4 24 ms 23 ms 24 ms AS15169.sydney.pipenetworks.com [218.100.2.97]
5 25 ms * * 66.249.95.232
6 146 ms 147 ms 145 ms 66.249.95.166
7 229 ms * * 216.239.43.212
8 235 ms 233 ms 234 ms 216.239.46.204
9 234 ms * 234 ms 216.239.48.143
10 235 ms * 233 ms 64.233.174.125
11 242 ms 237 ms 234 ms 74.125.30.6
12 * 235 ms 234 ms 74.125.31.134
13 234 ms 235 ms * cg-in-f100.google.com [209.85.171.100]
14 235 ms 234 ms 234 ms cg-in-f100.google.com [209.85.171.100]

Trace complete.

JasonM

Re: Unable to connect to some sites via Exetel

Post by JasonM » Wed Feb 04, 2009 6:00 pm

Berty,

Can you please post 50 pings to 220.233.0.9 and 50 pings to google.com?

Your issue doesn't seem like this issue, and maybe a local issue with your service.

Berty
Posts: 41
Joined: Tue Apr 06, 2004 4:22 pm
Location: Armidale

Re: Unable to connect to some sites via Exetel

Post by Berty » Wed Feb 04, 2009 7:14 pm

Hi Jason,
Thanks for the prompt reply.
Here are the test results:


C:\Users\X>ping exetel.com.au -t

Pinging exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=22ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=22ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.7: Destination host unreachable.
Reply from 192.168.1.7: Destination host unreachable.
Request timed out.
Reply from 220.233.0.9: bytes=32 time=28ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.0.9: bytes=32 time=26ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Reply from 220.233.0.9: bytes=32 time=181ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61
Reply from 220.233.0.9: bytes=32 time=27ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61

Ping statistics for 220.233.0.9:
Packets: Sent = 101, Received = 90, Lost = 11 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 181ms, Average = 25ms


C:\Users\X>ping google.com -t

Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=236ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=233ms TTL=244
Reply from 209.85.171.100: bytes=32 time=233ms TTL=244
Reply from 209.85.171.100: bytes=32 time=233ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=238ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=236ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=236ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Request timed out.
Reply from 209.85.171.100: bytes=32 time=241ms TTL=244
Request timed out.
Reply from 209.85.171.100: bytes=32 time=236ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Request timed out.
Reply from 209.85.171.100: bytes=32 time=234ms TTL=244
Reply from 209.85.171.100: bytes=32 time=235ms TTL=244
Reply from 209.85.171.100: bytes=32 time=242ms TTL=244
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=233ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=233ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=236ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=236ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=236ms TTL=243
Reply from 209.85.171.100: bytes=32 time=236ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=233ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=233ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=234ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243
Reply from 209.85.171.100: bytes=32 time=235ms TTL=243

Ping statistics for 209.85.171.100:
Packets: Sent = 79, Received = 76, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 233ms, Maximum = 242ms, Average = 234ms

JasonM

Re: Unable to connect to some sites via Exetel

Post by JasonM » Wed Feb 04, 2009 7:21 pm

The below passage suggests your connection was interuptted.
Are you using wireless or a cable to connect?

Reply from 220.233.0.9: bytes=32 time=25ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.7: Destination host unreachable.
Reply from 192.168.1.7: Destination host unreachable.
Request timed out.
Reply from 220.233.0.9: bytes=32 time=28ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.0.9: bytes=32 time=26ms TTL=61
Reply from 220.233.0.9: bytes=32 time=23ms TTL=61
Reply from 220.233.0.9: bytes=32 time=24ms TTL=61

Berty
Posts: 41
Joined: Tue Apr 06, 2004 4:22 pm
Location: Armidale

Re: Unable to connect to some sites via Exetel

Post by Berty » Thu Feb 05, 2009 10:21 am

JasonM wrote:The below passage suggests your connection was interuptted.
Are you using wireless or a cable to connect?
I am using wireless, as I mentioned earlier it might be my modem/router playing up. I'll check it out with a cable connection to see if the problem persists.

Thanks again

mwotton
Posts: 1
Joined: Thu Jun 26, 2008 4:15 pm
Location: Central Coast NSW

Re: Unable to connect to some sites via Exetel

Post by mwotton » Thu Feb 05, 2009 2:01 pm

I too am having issues connecting to some sites from my Exetel ADSL2 connection.

Eg. http://www.creflodollarministries.org/ will not resolve on the Exetel connection, but at work it resolves without problem.

From work, here is a trace:

Tracing route to creflodollarministries.org [74.208.47.82]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 36 ms 36 ms 36 ms lo0-insdsl-lns1.gls.integrity.net.au [203.80.170.22]
3 61 ms 36 ms 36 ms eth0-0-217-core0.gls.integrity.net.au [203.80.170.41]
4 34 ms 36 ms 36 ms eth0-0-210-bdr0.gls.integrity.net.au [203.80.170.3]
5 47 ms 40 ms 41 ms c-20496-1023-vaies-200-106.pr1.sydn.nxg.net.au [121.200.227.105]
6 38 ms 38 ms 37 ms s-pr1-sydn-1.br1.sydn.nxg.net.au [121.200.224.67]
7 157 ms 42 ms 183 ms ge-4-1-0.gw4.syd4.alter.net [210.80.189.41]
8 163 ms 37 ms 35 ms 0.so-7-2-1.xt3.syd4.alter.net [210.80.33.241]
9 198 ms 199 ms 201 ms 0.so-1-3-0.ir1.lax12.alter.net [210.80.48.125]
10 198 ms 199 ms 270 ms 0.so-5-0-0.il1.lax9.alter.net [152.63.48.65]
11 260 ms 200 ms 203 ms 0.so-7-0-0.XT1.LAX7.ALTER.NET [152.63.116.249]
12 202 ms 200 ms 202 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41]
13 200 ms 257 ms 201 ms po5-0.core01.lax05.atlas.cogentco.com [154.54.12.245]
14 203 ms 205 ms 205 ms te3-1.mpd01.lax05.atlas.cogentco.com [154.54.6.186]
15 204 ms 333 ms 206 ms te8-2.mpd01.lax01.atlas.cogentco.com [154.54.3.9]
16 203 ms 205 ms 206 ms te8-1.ccr01.lax01.atlas.cogentco.com [154.54.2.117]
17 241 ms 343 ms 240 ms te2-8.ccr01.iah01.atlas.cogentco.com [154.54.0.222]
18 231 ms 232 ms 381 ms te7-3.ccr02.dfw01.atlas.cogentco.com [154.54.2.225]
19 252 ms 348 ms 248 ms te3-2.ccr02.mci01.atlas.cogentco.com [154.54.5.170]
20 245 ms 240 ms 241 ms te-1-3.bb-a.ga.mkc.us.oneandone.net [38.104.86.42]
21 242 ms 255 ms 244 ms te-1-1.bb-a.slr.lxa.us.oneandone.net [74.208.1.65]
22 381 ms 246 ms 246 ms te-1-2.gw-distp-b.slr.lxa.oneandone.net [74.208.1.102]
23 251 ms 252 ms 250 ms ae-1.gw-prtr-r5-b.slr.lxa.oneandone.net [74.208.1.168]
24 245 ms 244 ms 246 ms u15253390.onlinehome-server.com [74.208.47.82]

Trace complete.


From my Exetel connection at home (using the IP I resolved at work):

Tracing route to u15253390.onlinehome-server.com [74.208.47.82]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms http://www.routerlogin.com [192.168.0.1]
2 * * * Request timed out.
3 26 ms 25 ms 26 ms 10.0.1.22
4 26 ms 27 ms 27 ms 38.2.233.220.exetel.com.au [220.233.2.38]
5 26 ms 25 ms 26 ms 316.ge-5-0-0.GW5.SYD2.ALTER.NET [221.133.215.77]
6 26 ms 25 ms 26 ms 0.so-7-2-0.XT3.SYD2.ALTER.NET [210.80.33.189]
7 177 ms 177 ms 177 ms 0.so-1-3-0.IR1.SAC2.Alter.Net [210.80.48.189]
8 178 ms 178 ms 178 ms 0.so-2-0-0.IL1.SAC1.ALTER.NET [152.63.48.33]
9 180 ms 180 ms 180 ms 0.so-3-1-0.XT1.SCL2.ALTER.NET [152.63.48.14]
10 181 ms 180 ms 181 ms po2-1.core01.sjc03.atlas.cogentco.com [154.54.13.113]
11 181 ms 181 ms 181 ms te3-3.mpd01.sjc03.atlas.cogentco.com [154.54.6.118]
12 181 ms 181 ms 181 ms te3-2.ccr02.sjc01.atlas.cogentco.com [154.54.6.101]
13 183 ms 182 ms 182 ms te8-3.ccr02.sfo01.atlas.cogentco.com [154.54.2.137]
14 222 ms 221 ms 222 ms te2-1.ccr02.mci01.atlas.cogentco.com [154.54.6.41]
15 227 ms 227 ms 228 ms te-1-3.bb-a.ga.mkc.us.oneandone.net [38.104.86.42]
16 226 ms 227 ms 226 ms te-1-1.bb-a.slr.lxa.us.oneandone.net [74.208.1.65]
17 228 ms 227 ms 227 ms te-1-2.gw-distp-b.slr.lxa.oneandone.net [74.208.1.102]
18 227 ms 227 ms 227 ms ae-1.gw-prtr-r5-b.slr.lxa.oneandone.net [74.208.1.168]
19 228 ms 226 ms 227 ms u15253390.onlinehome-server.com [74.208.47.82]

Trace complete.

There were a couple of other sites my wife was attempting to load that were exhibiting the same problem. I can repeat this action for those sites too if required.

Micha

JasonM

Re: Unable to connect to some sites via Exetel

Post by JasonM » Thu Feb 05, 2009 2:13 pm

The nameservers for it aren't responding, the server itself is up though:
Name Server:DNS1.MICAHTEK.COM
Name Server:DNS2.MICAHTEK.COM
Name Server:


[root@evilbox ~]# ping DNS1.MICAHTEK.COM
PING DNS1.MICAHTEK.COM (198.160.140.252) 56(84) bytes of data.

--- DNS1.MICAHTEK.COM ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1000ms

[root@evilbox ~]# dig @198.160.140.252 creflodollarministries.org in soa

; <<>> DiG 9.3.4-P1 <<>> @198.160.140.252 creflodollarministries.org in soa
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
[root@evilbox ~]# ping dns2.micahtek.com
PING dns2.micahtek.com (198.160.140.254) 56(84) bytes of data.

--- dns2.micahtek.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[root@evilbox ~]# dig @198.160.140.254 creflodollarministries.org in soa

; <<>> DiG 9.3.4-P1 <<>> @198.160.140.254 creflodollarministries.org in soa
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
[root@evilbox ~]#


---

[root@evilbox ~]# wget --bind-address=220.233.x http://74.208.47.82
--14:08:21-- http://74.208.47.82/
Connecting to 74.208.47.82:80... connected.
HTTP request sent, awaiting response... 400 Bad Request
14:08:21 ERROR 400: Bad Request.

WilliamC
Posts: 369
Joined: Tue May 02, 2006 10:50 pm

Re: Unable to connect to some sites via Exetel

Post by WilliamC » Fri Feb 06, 2009 12:58 am

Dear Users,

For the most part http://wwwkal.ums.edu.my/LJMS/index.htm was found to be blocking the 220.233.0.0/16 range, an appeal has been made for this. The same applies for a few other sites that have been mentioned in this post. Ultimately the decision to block / unblock the sites lies completely with their admins and we (exetel) can only await for them to do this for us.

Regards,

William C

Post Reply