Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


5 posts

Wannabe Geek


Topic # 95301 30-Dec-2011 00:27
Send private message

Hi,

I am having some issues with the Telecom network. I'm often unable to access websites via browser, even though I can ping and tracert them without issues. DNS resolution is working fine, but it seems the remote server is unable to make a connection and times out with a "Connection closed by remote server". Using a remote proxy everything works fine, which leads me to think this is a Telecom issue. This has been happening more often recently and I'm starting to worry as internet access is very important to me.

What could be the issue? Here is an example with one website, www.minecraftforum.net (which redirects to  varnish.cursetech.com) :

Pinging varnish.cursetech.com [68.64.47.124] with 32 bytes of data:
Reply from 68.64.47.124: bytes=32 time=245ms TTL=47
Reply from 68.64.47.124: bytes=32 time=212ms TTL=47
Reply from 68.64.47.124: bytes=32 time=213ms TTL=47
Reply from 68.64.47.124: bytes=32 time=212ms TTL=47

Ping statistics for 68.64.47.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
 Minimum = 212ms, Maximum = 245ms, Average = 220ms


Tracing route to varnish.cursetech.com [68.64.47.124]
over a maximum of 30 hops:

1 48 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 24 ms 134 ms 23 ms 115-188-232-1.jetstream.xtra.co.nz [115.188.232.1]
3 * 35 ms 73 ms mdr-fid-int.akbr5.global-gateway.net.nz [202.37.244.222]
4 48 ms 48 ms * ae4-10.akbr5.global-gateway.net.nz [202.37.244.221]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * 160 ms 160 ms 205.158.79.141.ptr.us.xo.net [205.158.79.141]
10 159 ms 160 ms 160 ms te1-0-0d0.cir1.la3-ca.us.xo.net [207.88.15.29]
11 164 ms 163 ms 195 ms 207.88.14.217.ptr.us.xo.net [207.88.14.217]
12 216 ms 219 ms 215 ms vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
13 246 ms 215 ms 215 ms te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
14 214 ms 214 ms 213 ms ae0d0.mcr1.smyrna-ga.us.xo.net [216.156.0.66]
15 245 ms 215 ms 215 ms 209.118.220.30
16 216 ms 215 ms 221 ms 68.64.33.45
17 214 ms 213 ms 244 ms 68.64.47.124

Trace complete.


Seems everything is in order but attempts to GET the website fail, as the connection is closed after a while as the server times out. So it seems the connection request is making it through but the data is unable to be routed back to me, leading to the server giving up.

What could be the issue? Does anybody else have the same issues? Is there a way to fix it or do we just have to wait it out?

Also, on a related note, google.co.nz has become so unreliable (randomly timing out generally unresponsive) I've been forced to redirect to google.com which always works fine. I suppose this is part of the general problem as well.

Create new topic
BDFL - Memuneh
61192 posts

Uber Geek
+1 received by user: 11974

Administrator
Trusted
Geekzone
Lifetime subscriber

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.