dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
2
share rss forum feed

Toollio

join:2003-11-17
Brazil/Cda
reply to exseven

Re: [Eastern Ontario] Inaccessible sites

said by exseven:

I'm just going to point out that the last hop when you can't reach it is the second last hop when you can. There is probably sole firewall issues or something else in Brazil out of cogeco control.

Try contacting dh-c.net.br

There is no issue at the Brazil end. I just asked my wife, who is in Brazil, to access the site from there--no problems. I can still access the site fine in Canada with my Virgin mobile account on my ipad. I just had a friend on Rogers in Toronto try it again, and he can access it as usual. I can access it on my cellular.

The reality is that this problem seems to affect only Cogeco subscribers--and strangely only a portion of them. One would assume a problem at the Brazil end would affect everyone--or at least all Cogeco subscribers.

Here is my tracert from this morning, similar to the poster above. (I have Xd out some addresses for security.) It would be interesting if someone who can access the site could post theirs.

Tracing route to www.reclameaqui.com.br [200.98.215.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms xxx]
2 5 ms 6 ms 5 ms x.x.x.x
3 21 ms 19 ms 18 ms d226-5-109.home.cgocable.net [xx.x x.xx]
4 16 ms 17 ms 18 ms xe-2-2-0.tor10.ip4.tinet.net [77.67.69.237]
5 29 ms 29 ms 28 ms xe-1-1-0.nyc23.ip4.tinet.net [89.149.185.81]
6 41 ms 41 ms 81 ms as12956.ip4.tinet.net [77.67.78.2]
7 117 ms 74 ms 72 ms Xe11-1-8-0-grtmiabr4.red.telefonica-wholesale.ne
t [94.142.126.118]
8 172 ms 232 ms 172 ms Xe2-0-0-0-grtsaosi3.red.telefonica-wholesale.net
[94.142.123.106]
9 185 ms 182 ms 186 ms Xe1-0-4-0-grtsaosi3.red.telefonica-wholesale.net
[94.142.118.89]
10 173 ms 174 ms 174 ms 176.52.253.238
11 * * * Request timed out.
12 176 ms 186 ms 189 ms 200-147-29-3.static.uol.com.br [200.147.29.3]
13 * 177 ms * 200-147-29-3.static.uol.com.br [200.147.29.3]
14 186 ms * 177 ms host91-33.dh-c.net.br [200.225.91.33]
15 * * 179 ms host91-33.dh-c.net.br [200.225.91.33]
16 * * * Request timed out.
17 * * * Request timed out.

exseven
Premium,VIP
join:2003-05-23
L8E0G6
kudos:1
As the trace gets to host91-33.dh-c.net.br in all cases i would say the issue is between them and reclameaqui.com.br or a firewall at reclameaqui that is blocking a/multiple subnets. Contact them and ask for a reverse trace back to your home IP, and to verify their firewalls and with their hoster (dh-c.net). The packet leaves the cogeco network and makes it almost all the way to the end system then stops...

17  host91-33.dh-c.net.br (200.225.91.33)  205.412 ms  206.180 ms  204.102 ms
18  * * *
19  reclameaqui.com.br (200.98.215.88) [open]  203.962 ms  205.996 ms *

Toollio

join:2003-11-17
Brazil/Cda

2 edits
said by exseven:

As the trace gets to host91-33.dh-c.net.br in all cases i would say the issue is between them and reclameaqui.com.br or a firewall at reclameaqui that is blocking a/multiple subnets. Contact them and ask for a reverse trace back to your home IP, and to verify their firewalls and with their hoster (dh-c.net). The packet leaves the cogeco network and makes it almost all the way to the end system then stops...

17  host91-33.dh-c.net.br (200.225.91.33)  205.412 ms  206.180 ms  204.102 ms
18  * * *
19  reclameaqui.com.br (200.98.215.88) [open]  203.962 ms  205.996 ms *

How, then, would you explain the fact that Cogeco subscribers in Cornwall (see above) and at least one location can access the site? Surely the end points in Brazil would not be different for different Cogeco clients?

There is no point in contacting dh-c.net. Brazilian companies are notoriously bad at responding to consumer issues. I will receive no reply.

Edit to add info:

I just tried an experiment. I am now accessing the site through a VPN server in Montreal. The site can be reached. However, the tracert seems to be the same as with cogeco--final hop unreachable and the same second-last hop. I also did a trace on my ipad through virgin mobile--I get the site, but trace shows final destination unceachable and the same second last hop. This suggests to me that the final destination cannot be pinged or tracerted, and that does not necessarily mean it is broken. Many routers and providers block pings and tracerts ( ICMP packets).


thingfish

@bell.ca
As I mentioned above, I can view the webpage with my DSL connection. However, trying to tracert is not successful. It also times out after the host91-33.dh-c.net.br hop.

Doesn't really help your situation, but just thought I'd provide a bit more info.

Toollio

join:2003-11-17
Brazil/Cda
said by thingfish :

As I mentioned above, I can view the webpage with my DSL connection. However, trying to tracert is not successful. It also times out after the host91-33.dh-c.net.br hop.

Doesn't really help your situation, but just thought I'd provide a bit more info.

Thanks. That to me is further confirmation that the last hop is blocking ping/tracert packets, not an indication that it is actually uncreachable in real-world browsing. So, it seems we're back to Cogeco.