Hi There,
I’m facing a strange problem since 10 days with a .com website. I can’t access it anymore, when I ping it I get:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Site is not down, doubled checked it with online proxy. I suspect is this Firewall work? If so, how to unblock this site? I’m using Comodo 5.10.228257.2253 version.
Please help, thank you.
are you using securedns?
I don’t know, where to check whether that feature is enabled or disabled?
All other sites are working normally except one. I also did ipconfig /flushdns but no result 
EDIT:
You meant adding these:
Preferred DNS server address for Comodo Secure DNS is: 8.26.56.26
Alternate DNS server address for Comodo Secure DNS is: 8.20.247.20
No, ISP specified only.
if you are not using comodo’s secure dns idk what the cause is. maybe try a different dns from your isp’s
Probably worth posting your ipconfig /all. it’s also worth seeing if you can ping the site, by name and IP address.
I did that…it results in:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Did you try the site name and the site IP address?
Without giving any site input, how could ping command work ???
When I ping the site, ping looks up for the IP address of that site but no ping result:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
I checked it once again, site is opening with online proxy. Also, all sites work for me except this one.
So, I fail to understand if Comodo has something to do with it? If yes, how to unblock this site? Please help
EDIT: same result with FF and IE so even the browser scenario is ruled out.
Using the IP address as opposed to the site name avoids name lookup and removes one potential issue from the equation.
When I ping the site, ping looks up for the IP address of that site but no ping result:Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
I checked it once again, site is opening with online proxy. Also, all sites work for me except this one.
So, I fail to understand if Comodo has something to do with it? If yes, how to unblock this site? Please help
EDIT: same result with FF and IE so even the browser scenario is ruled out.
If you’re able to access other web sites with CIS enabled, then unless you’ve specifically blocked this site, CIS is not your problem. Mybe the site is blocking certain countries have you tried a proxy from your country?
I tried but no result.
[i]Pinging 83.170.92.56 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 83.170.92.56:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
[/i]
To be honest, I don’t doubt CIS either 
But I’m trying to figure this out, you’re right about blocking certain countries but I never use any proxy for private torrent sites as they’ve very rigid rules regarding the same.
But I observed something:
Some six months ago I saved my IP config:
xxx.xx.133.79
DNS Servers . . . . . . . . . . . : xxx.xxx.37.38
xxx.xxx.37.37
xxx.xx.8.8
A few days ago, my ipconfig shows:
xxx.xx.162.34
DNS Servers . . . . . . . . . . . : xxx.xxx.37.37
xxx.xxx.37.35
xxx.xx.8.8
xxx.xx.8.9
Apparently, there is change in the N/W info. Could this change behind this trouble? If yes, why only with one site…couldn’t get it ???
EDIT: Got an idea. I’ll boot into Fedora and check it from there. If it works then trouble coming from Comodo? I don’t think Avira Antivir Personal blocks the sites. Pls correct me, thanks
A long shot, probably wrong, but tried rebooting your router?
I booted into Fedora 14, same problem. I can’t access the site.
So it means, no problem with Comodo. Isn’t it?
Next, what could be the problem with that site?
a) blocked by my ISP (99% NO, writing a mail to them)
b) blocked from the National Gateway? (NO)
c) blocked by the site? Possible, but I’m not sure because I didn’t commit any violation.
d) any other reason?
I never faced such a problem in my life, nice experience
Did you try Co-Mo-Do’s suugestion of rebooting your router? If for some reason the site is blocking your IP address the problem could be fixed by obtaining a new one (assuming it is dynamically assigned).
Try tracert 83.170.92.56 to see how far you get when attempting to access the site. A trace is much more useful than a ping because you can see the point at which you aren’t getting a response.
No router/modem installed. It’s a simple 10 Mbps Fiber broadband line with RJ45 plugged into Ethernet port.
How I forgot this thing :-[ Just tried, getting RTOs after 10 levels or so. Should I paste it here?
EDIT: I did a complete full-system scan using Avira Antivir. ZERO problem.
network problem, if it was an internal error it would not tracert to level 10, if you are getting errors after level 10 there is an issue with something else, not your computer.
That’s what puzzles me. I mean, pls look at this:
4 * * * Request timed out.
8 * * * Request timed out.
13 165 ms 145 ms 146 ms dc5.as13213.net [83.170.70.134]
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.
Should I ignore 4th and 8th hops ???
EDIT: Assuming this problem is from that site’s network then how could I’m able to access it using an online proxy? (I know proxy has its own IP etc).
That depends where the 4th hop is.
EDIT: Assuming this problem is from that site's network then how could I'm able to access it using an online proxy? (I know proxy has its own IP etc).
By using a proxy you’re bypassing any restrictions being imposed by your ISP/Country.
Looking at traceroutes from a few different countries, it does look like you have a network problem, whether it’s an error or deliberate…
TraceRoute to 83.170.92.56 [server51309.uk2net.com]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.42 -
2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net
3 5 2 2 206.223.118.61 equinix.tge9-3.ar1.dfw1.us.nlayer.net
4 0 0 0 69.31.63.125 ae0-50g.cr1.dfw1.us.nlayer.net
5 6 6 7 69.22.142.2 xe-1-1-0.cr1.iah1.us.nlayer.net
6 33 21 28 69.22.142.118 xe-4-2-1.cr1.atl1.us.nlayer.net
7 39 39 50 69.22.142.141 xe-8-3-0.cr1.nyc2.us.nlayer.net
8 38 39 44 69.31.95.121 ae2-30g.cr1.nyc3.us.nlayer.net
9 105 105 105 69.22.142.133 xe-7-3-0.cr1.lhr1.uk.nlayer.net
10 108 106 109 69.22.139.63 ae1-70g.ar1.lhr1.uk.nlayer.net
11 105 105 107 69.22.139.46 as13213.ae4.ar1.lhr1.uk.nlayer.net
12 106 106 108 83.170.70.134 dc5.as13213.net
13 105 105 105 83.170.92.56 server51309.uk2net.com
Trace complete
$ tracert 83.170.92.56
Tracing route to server51309.uk2net.com [83.170.92.56]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Ozzy [192.168.1.1]
2 1 ms 1 ms 1 ms xxxx.112.36]
3 2 ms 1 ms 1 ms xxxx.112.1]
4 2 ms 2 ms 1 ms xxxx.130.169]
5 2 ms 3 ms 2 ms xxxx.59.38]
6 163 ms 163 ms 163 ms linx-224.as13213.net [195.66.224.19]
7 169 ms 163 ms 171 ms dc5.as13213.net [83.170.70.134]
8 169 ms 168 ms 163 ms server51309.uk2net.com [83.170.92.56]
Trace complete.
I’m still confused if this problem is from my ISP or not. I ran tracert once again now, output:
Tracing route to server51309.uk2net.com [83.170.92.56]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ras.beamtele.net [183.82.128.1]
2 1 ms <1 ms <1 ms ras.beamtele.net [183.82.14.53]
3 1 ms 2 ms 2 ms 115.113.207.53.static-hyderabad.vsnl.net.in [115.113.207.53]
4 * * * Request timed out.
5 15 ms 15 ms 15 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
6 151 ms 176 ms 151 ms if-2-2.tcore2.MLV-Mumbai.as6453.net [180.87.38.2]
7 135 ms 134 ms 134 ms if-6-2.tcore1.L78-London.as6453.net [80.231.130.5]
8 * 144 ms * Vlan704.icore1.LDN-London.as6453.net [80.231.130.10]
9 138 ms 138 ms 138 ms te0-1-0-5.mpd21.lon13.atlas.cogentco.com [130.117.14.5]
10 135 ms 135 ms 136 ms te0-3-0-7.ccr22.lon13.atlas.cogentco.com [154.54.56.82]
11 134 ms 134 ms 134 ms te4-1.mpd02.lon01.atlas.cogentco.com [130.117.0.94]
12 142 ms 142 ms 142 ms 149.6.3.158
13 145 ms 147 ms 145 ms dc5.as13213.net [83.170.70.134]
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 if it 's OK at 4th or not. It shouldn’t be but sometimes it can happen. Again, post 13th is a problem from overseas servers connected to that website? ???
Note: I raised an escalation with my ISP in this regard, awaiting their response. To my understanding, they never block websites.
The time out at the 4th hop could be caused by a variety of things, such as congestion, a routing table error, return path problem etc. The problem itself could be on the far side of hop 3, the near side of hop 5 or with the device at hop 4. As far as your unreachable website, try a different IP address from the same block and see if it’s reachable. The address you want to reach is - 83.170.92.56 try: 83.170.92.50/51/52/53 etc.
True. I see a Firewall Event for traceroute program.
83.170.92.50: Success (still there is 4th hop, ignoring it)
11 141 ms 141 ms 141 ms te4-1.mpd02.lon01.atlas.cogentco.com [130.117.0.94]
12 141 ms 143 ms 141 ms 149.6.3.158
13 152 ms 153 ms 153 ms dc5.as13213.net [83.170.70.134]
14 151 ms 151 ms 151 ms server51303.uk2net.com [83.170.92.50]
Trace complete.
83.170.92.51: Failed (same result, 4th hop, post 13th nothing).
83.170.92.52: Failed (same result, 4th hop, post 13th nothing).
83.170.92.53: Success (ignoring 4th hop)
11 145 ms 146 ms 145 ms te1-3.mpd02.lon01.atlas.cogentco.com [154.54.38.150]
12 143 ms 142 ms 142 ms 149.6.3.158
13 153 ms 156 ms 216 ms dc5.as13213.net [83.170.70.134]
14 147 ms 147 ms 147 ms server51306.uk2net.com [83.170.92.53]
Trace complete.
83.170.92.54: Success (ignoring 4th hop)
11 135 ms 135 ms 135 ms te2-2.mpd02.lon01.atlas.cogentco.com [154.54.57.158]
12 136 ms 136 ms 136 ms 149.6.3.158
13 147 ms 147 ms 147 ms dc5.as13213.net [83.170.70.134]
14 135 ms 135 ms 134 ms server51307.uk2net.com [83.170.92.54]
Trace complete.
83.170.92.55: Success (ignoring 4th hop)
11 148 ms 205 ms 207 ms te1-3.mpd02.lon01.atlas.cogentco.com [154.54.38.150]
12 136 ms 136 ms 136 ms 149.6.3.158
13 148 ms 148 ms 147 ms dc5.as13213.net [83.170.70.134]
14 145 ms 145 ms 144 ms server51308.uk2net.com [83.170.92.55]
Trace complete.
83.170.92.56: Failed (4th hop, post 13th nothing) ???