Home → Problems →

184.73.201.0 unreachable from Eastern Canada

• Edit

Mark Gertsvolf

31 Aug, 2011 06:39 PM

I am located in Eastern Canada and I can't access lighthouseapp.com websites mapped to 184.73.201.0. My colleague in the UK is having no issues and DNS in his area resolves the FQDNs into the same IP address.
As an example: I can access help.lighthouseapp.com site, which in my area is mapped to: 184.73.201.197, but I can not access: selectstart.lighthouseapp.com or my.lighthouseapp.com bothy of which are mapped to 184.73.201.0.

Traceroute from my location does not produce any useful results.

Your timely response will be highly appreciated.

1. 1 Posted by Mark Gertsvolf on 31 Aug, 2011 06:43 PM

   

   My IP address is 173.206.129.44 and it is hosted by Primus Canada.
   I am having no other routing issues with other servers, as far as I can tell.

   • Edit

2. 2 Posted by Nicole on 31 Aug, 2011 06:44 PM

   

   Can you setup up your 'hosts' file with lighthouseapp.com being one of your app instances instead of the Elastic IP?

   e.g. 174.129.46.121, or 204.236.192.54

   This should solve the problem. Let us know.

   Thanks,
   Nicole

   • Edit

3. 3 Posted by Mark Gertsvolf on 31 Aug, 2011 06:50 PM

   

   Nicole,
   Thank you for your response.
   As a quick experiment I used each one of the two addresses directly in the URL with no success. I can still change the /etc/hosts if you think it might produce a different result.

   Thanks,
   Mark.

   • Edit

4. 4 Posted by Nicole on 31 Aug, 2011 06:55 PM

   

   Mark -

   Yes, it looks like your ISP or network isn't allowing our IP address (which ends in a zero, apparently some older configs don't allow that)

   Try adding this to your hosts file:

   184.72.224.21 lighthouseapp.com selectstart.lighthouseapp.com sera.lighthouseapp.com my.lighthouseapp.com
   

   (add any other accounts you use in there)

   You may want to contact your service provider to double check if they can fix the issue further up the chain, but this should at least fix the issue for you.

   Thanks,
   Nicole

   • Edit

5. 5 Posted by Mark Gertsvolf on 31 Aug, 2011 07:06 PM

   

   Hi Nicole,

   I added the mapping to my etc/hosts and verified that it changed the resolution.
   With that I am still having issues accessing the server from the browser.

   $ tracert selectstart.lighthouseapp.com

   Tracing route to lighthouseapp.com [184.72.224.21]
   over a maximum of 30 hops:

   1 20 ms 6 ms 6 ms 192.168.3.1 2 26 ms 25 ms 26 ms dsl-173-206-128-1.tor.primus.ca [173.206.128.1] 3 25 ms 25 ms 25 ms 216.254.131.158 4 39 ms 37 ms 39 ms ra2sh-ge3-4-14.mt.bigpipeinc.com [66.244.223.237] 5 60 ms 37 ms 37 ms ra1sh-ge3-3.mt.shawcable.net [66.163.66.33] 6 65 ms 44 ms 39 ms rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154] 7 * 39 ms 37 ms rc2hu-ge0-0-0.ny.shawcable.net [66.163.74.14] 8 43 ms 43 ms 44 ms rc1as-ge6-0-0.vx.shawcable.net [66.163.76.250] 9 * * * Request timed out. 10 47 ms 44 ms 45 ms 72.21.220.41 11 46 ms 45 ms 45 ms 72.21.222.141 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. ... ...

   • Edit

6. 6 Posted by Mark Gertsvolf on 31 Aug, 2011 07:23 PM

   

   Hi Nicole,

   Thank you for your response.
   I modified my etc/hosts and verified that the changes took effect. However, I am still unable to access the server from my browser.
   Also, if I use the explicit IP address in the URL in the browser, rather then FQDN, I still can not access the site: http://184.72.224.21/projects/81217-avaya-uc/tickets
   Not sure what the issue might be....

   $ tracert selectstart.lighthouseapp.com

   Tracing route to lighthouseapp.com [184.72.224.21]
   over a maximum of 30 hops:

   1 20 ms 6 ms 6 ms 192.168.3.1 2 26 ms 25 ms 26 ms dsl-173-206-128-1.tor.primus.ca [173.206.128.1] 3 25 ms 25 ms 25 ms 216.254.131.158 4 39 ms 37 ms 39 ms ra2sh-ge3-4-14.mt.bigpipeinc.com [66.244.223.237] 5 60 ms 37 ms 37 ms ra1sh-ge3-3.mt.shawcable.net [66.163.66.33] 6 65 ms 44 ms 39 ms rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154] 7 * 39 ms 37 ms rc2hu-ge0-0-0.ny.shawcable.net [66.163.74.14] 8 43 ms 43 ms 44 ms rc1as-ge6-0-0.vx.shawcable.net [66.163.76.250] 9 * * * Request timed out. 10 47 ms 44 ms 45 ms 72.21.220.41 11 46 ms 45 ms 45 ms 72.21.222.141 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.

   • Edit

7. brandi closed this discussion on 06 Sep, 2011 05:38 PM.