Can't connect to the URL, only the IP

I am having issues accessing the site from Vancouver Canada now. My issue is a little different however. When I type in the url, I am redirected to navil.com a pay per click search engine. When I ping the url from cmd I can get to it. I can get to cyberstreet.com and I can get to Enworld via the IP (thus I am able to post). Is anyone else experiencing this?
 

log in or register to remove this ad



xmanii said:
Email sent.

Thanks xmanii. I was able to access the site from home using some of the proxy servers from the site that you e-mailed me. However it wouldn't let me log in to post which was frustrating. It felt a little strange. Like I was here but no-one could see or hear me! :D

I'm back at work now where I can get on without a problem. Still no luck at home though.

Does anyone know some proxy servers where I can post from?

Olaf the Stout
 


xmanii said:
No problem, glad it helped some :)


Have you tried making a new account, while using the proxy? I would try that

I don't think that would make a difference. The proxy seemed to limit what you could do on webpages. I couldn't log into my Hotmail account either using the proxy server for example. I'm not 100% computer savvy but it seemed like it wouldn't let me do things that might use or create a cookie. I can't remember the error number that it gave when I tried.

Olaf the Stout
 

Another week and still no access to EN World from my Optus account at home. I rang tech support to see if they could do anything about it and this is the reply that I received:

Dear Adam,

Thank you for your email.

Following is the result from our engineering team:

---------------------------
The problem is that both our Sydney and Melbourne name servers are blocked from the nameservers that handle enworld.org. See below details:

;; AUTHORITY SECTION:
enworld.org. 10467 IN NS ns2.cyberstreet.com.
enworld.org. 10467 IN NS ns.cyberstreet.com.

;; ADDITIONAL SECTION:
ns2.cyberstreet.com. 60253 IN A 204.145.237.14
ns.cyberstreet.com. 148697 IN A 65.127.163.6


A successful traceroute from my desktop to ns2.cyberstreet.com:

[***@*** ~]$ traceroute 204.145.237.14
traceroute to 204.145.237.14 (204.145.237.14), 30 hops max, 38 byte packets
1 zen1-fe0.gw.optusnet.com.au (203.10.68.225) 1.379 ms 0.534 ms 0.650 ms
2 hlp1-pos1.gw.optusnet.com.au (198.142.7.34) 0.855 ms 0.761 ms 0.683 ms
3 mas2-pos5-5.gw.optusnet.com.au (198.142.163.213) 1.459 ms 1.413 ms 1.399 ms
4 mas3-ge10-1.gw.optusnet.com.au (211.29.141.5) 2.043 ms 1.521 ms 1.461 ms
5 203.208.191.5 (203.208.191.5) 148.251 ms 148.561 ms 148.578 ms
6 203.208.171.13 (203.208.171.13) 148.915 ms 148.579 ms 203.208.171.1 (203.208.171.1) 148.598 ms MPLS Label=100240 CoS=5 TTL=1 S=0
7 203.208.171.122 (203.208.171.122) 148.791 ms 203.208.173.133 (203.208.173.133) 148.782 ms 160.025 ms MPLS Label=159616 CoS=5 TTL=1 S=0
8 203.208.168.222 (203.208.168.222) 148.659 ms 148.691 ms 148.465 ms
9 203.208.168.186 (203.208.168.186) 148.686 ms 148.408 ms 148.457 ms 10 bur-core-01.inet.qwest.net (205.171.213.105) 149.068 ms 148.830 ms 164.154 ms
11 tpa-core-02.inet.qwest.net (67.14.3.10) 212.637 ms 213.195 ms 212.637 ms
12 nap-edge-01.inet.qwest.net (205.171.27.46) 217.712 ms 217.992 ms 217.546 ms
13 65.124.198.234 (65.124.198.234) 222.138 ms 221.745 ms 221.321 ms
14 63-144-217-198.cust.neotechus.com (63.144.217.198) 222.301 ms 223.685 ms 222.631 ms
15 204.145.237.14 (204.145.237.14) 222.625 ms 222.660 ms 222.312 ms


Unsuccessful traceroutes from one of our Sydney DNS servers:

[***@dns01.syd ~]$ traceroute 204.145.237.14 traceroute to 204.145.237.14 (204.145.237.14), 30 hops max, 38 byte packets
1 mas4-vl300.gw.optusnet.com.au (211.29.132.2) 0.667 ms 1.022 ms 0.322 ms
2 mas3-ge1-2.gw.optusnet.com.au (211.29.129.241) 0.218 ms mas3-ge9-3.gw.optusnet.com.au (211.29.129.249) 0.406 ms mas3-ge1-2.gw.optusnet.com.au (211.29.129.241) 0.380 ms
3 203.208.148.97 (203.208.148.97) 155.227 ms 147.512 ms 147.468 ms
4 203.208.171.65 (203.208.171.65) 147.500 ms 203.208.149.33 (203.208.149.33) 147.794 ms 203.208.171.65 (203.208.171.65) 147.570 ms
5 203.208.171.1 (203.208.171.1) 148.094 ms 203.208.171.9 (203.208.171.9) 147.806 ms 203.208.171.13 (203.208.171.13) 148.051 ms MPLS Label=100240 CoS=5 TTL=1 S=0
6 203.208.173.133 (203.208.173.133) 147.775 ms 203.208.171.122 (203.208.171.122) 147.929 ms 203.208.173.133 (203.208.173.133) 147.843 ms MPLS Label=159616 CoS=5 TTL=1 S=0
7 203.208.168.222 (203.208.168.222) 147.817 ms 147.620 ms 196.845 ms
8 203.208.168.186 (203.208.168.186) 147.822 ms 147.757 ms 147.995 ms
9 bur-core-01.inet.qwest.net (205.171.213.105) 148.122 ms 148.081 ms 148.025 ms 10 tpa-core-02.inet.qwest.net (67.14.3.10) 211.917 ms 211.695 ms 212.849 ms
11 nap-edge-01.inet.qwest.net (205.171.27.46) 217.170 ms 217.772 ms 217.073 ms
12 65.124.198.234 (65.124.198.234) 221.564 ms 221.185 ms 221.187 ms
13 * * *
..
30 * * *

.and a Melbourne DNS server:

[***@dns01.mel ~]$ traceroute 204.145.237.14 traceroute to 204.145.237.14 (204.145.237.14), 30 hops max, 38 byte packets
1 sun4-vl300.gw.optusnet.com.au (211.31.132.2) 0.366 ms 0.400 ms 1.102 ms
2 sun1-ge0.gw.optusnet.com.au (211.31.129.42) 0.533 ms sun1-ge2-1.gw.optusnet.com.au (211.31.129.66) 0.220 ms sun1-ge0.gw.optusnet.com.au (211.31.129.42) 0.502 ms
3 ros1-pos13.gw.optusnet.com.au (211.31.129.86) 15.797 ms 15.534 ms 15.752 ms
4 203.208.148.225 (203.208.148.225) 170.185 ms 170.059 ms 170.115 ms
5 pax-brdr-02.inet.qwest.net (205.171.1.1) 171.367 ms 171.418 ms 171.251 ms
6 svl-core-02.inet.qwest.net (205.171.205.29) 170.601 ms 170.807 ms 171.228 ms
7 tpa-core-02.inet.qwest.net (67.14.3.10) 233.918 ms 233.788 ms 233.475 ms
8 nap-edge-01.inet.qwest.net (205.171.27.46) 238.940 ms 239.147 ms 238.718 ms
9 65.124.198.234 (65.124.198.234) 242.574 ms 242.589 ms 242.185 ms 10 * * * ..
30 * * *

As you can see, the router with IP address 65.124.198.234 is not allowing traffic from our DNS servers to pass it. The same results were seen when trying to reach the other name server ns.cyberstreet.com (65.127.163.6).
------------------------------

You may wish to check with your webhost provider to enquire if they have placed any blocks on OptusNet.

Regards,
Robyn,

OptusNet Support Specialist

Does this shed any light on the situation for anyone? Are us Optus users forever doomed to not be able to access EN World?

Olaf the Stout
 

That's exactly the same problem I had and reported after checking with Netspace (who came to the same conclusion) nearly 2 months ago when it started happening to me...still no joy here either. :(
 

This is driving me nuts. I'm not a tech guy, and so offer no ideas for resolution - but I wanted to mention that we're looking for one.
 

Good lord, this is one of those things that actually make we realize that internet is a lot more than you and the pages you open...
Sorry to hear you still have trouble guys. Really. :(
 

Remove ads

Top