Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

"Connection timed out" --Router problem?


  • Please log in to reply
3 replies to this topic

#1 Merlinnair

Merlinnair

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 29 February 2012 - 07:04 PM

For some reason, just a few days ago, I can't access "sockshare.com" or "putlocker.com" at all. (They use the same server anyway). It had been working fine for me until then, and I can't think of any major changes that have happened.

I've tried it on three browsers and two different computers, I get similar error messages of "connection timed out". The websites work fine on my friends' computers, it's just mine. And those are the only sites that do this. I also ran tracert in command prompt on sockshare and got these results, not sure what they mean:
Tracing route to sockshare.com [89.238.130.247]
over a maximum of 30 hops:

1 5 ms 4 ms 2 ms 192.168.2.1
2 9 ms 11 ms 11 ms ip24-255-168-1.ks.ks.cox.net [24.255.168.1]
3 13 ms 11 ms 23 ms 70.183.64.5
4 23 ms 25 ms 22 ms ip70-183-65-25.ks.ks.cox.net [70.183.65.25]
5 28 ms 20 ms 78 ms 70.183.66.245
6 17 ms 18 ms 23 ms 70.183.71.61
7 109 ms 81 ms 77 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
8 104 ms 105 ms 110 ms xe-4-2-0-0.nyk2nqp2.us.ip.tdc.net [198.32.176.10
1]
9 222 ms 219 ms 222 ms ae-0.ldn4nqp1.uk.ip.tdc.net [83.88.25.27]
10 198 ms 196 ms 197 ms cpe.pos1-0.0xc3d76d2a.albnxg7.customer.tele.dk [
195.215.109.42]
11 195 ms 195 ms 201 ms 77.243.185.169
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.

I don't know much about the subject but I can tell that it is NOT Dns-blocked.
Neither does my router or my provider block the site, it just ...stops. Is this something that I can fix myself? Let me know if you need more info on my router or my computer...

Edited by Merlinnair, 29 February 2012 - 07:56 PM.


BC AdBot (Login to Remove)

 


#2 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:11:50 PM

Posted 01 March 2012 - 01:10 AM

It appears that your IP address has been blocked at their server. I ran a traceroute and the next hop after "74.243.185.169" is the server itself.

I'd recommend you contact sockshare directly and see what they say. Be sure to include the IP address you're accessing the site from in your email to them.

And just for comparison, here is a traceroute from me (Memphis, TN) to them:
Tracing route to sockshare.com [89.238.130.247]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  * [192.168.2.1]
  2     7 ms     7 ms    12 ms  * [65.255.*.*]
  3     5 ms     6 ms     9 ms  * [65.255.*.*]
  4    10 ms    12 ms     7 ms  * [65.255.*.*]
  5    13 ms    11 ms    12 ms  net-216-37-66-33.in-addr.worldspice.net [216.37.
66.33]
  6    16 ms    11 ms    14 ms  67.107.184.9.ptr.us.xo.net [67.107.184.9]
  7    10 ms     9 ms    14 ms  216.156.10.221.ptr.us.xo.net [216.156.10.221]
  8    13 ms    11 ms    14 ms  ae1d0.mcr1.memphis-tn.us.xo.net [216.156.1.45]
  9    23 ms    26 ms    27 ms  vb1330.rar3.dallas-tx.us.xo.net [216.156.0.89]
 10    23 ms    26 ms    22 ms  207.88.14.241.ptr.us.xo.net [207.88.14.241]
 11    31 ms    31 ms    32 ms  206.111.5.218.ptr.us.xo.net [206.111.5.218]
 12   121 ms   121 ms   121 ms  xe-10-3-0.lon10.ip4.tinet.net [213.200.80.26]
 13   145 ms   151 ms   149 ms  m247-gw.ip4.tinet.net [141.136.96.230]
 14   142 ms   144 ms   146 ms  77.243.185.169
 15   144 ms   146 ms   149 ms  no-rdns-yet.ohtele.com [89.238.130.247]

Trace complete.
* = censored

#3 Merlinnair

Merlinnair
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:50 PM

Posted 06 March 2012 - 07:26 PM

Their reply was (After they told me to clear my cache and whatnot):
"This is then something your ISP is filtering on their end, we do not black IP's."

Is there anything else I can do?

#4 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:11:50 PM

Posted 06 March 2012 - 08:19 PM

They are blocking your IP. The fact that we go through the same hop (77.243.185.169) shows that their firewall either on a router or server, is blocking your IP address.

This is not anything from your ISP, and while they may not be blocking you intentionally - they have blocked your IP.

EDIT: When I say "they are" it could also be their provider/host.

Edited by NpaMA, 06 March 2012 - 08:27 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users