Folks:<br><br>I'd like to see if anyone has heard of circumstances like this before.<br><br>I have a server on the Amazon EC2 cloud running a website service. This is largely working well.<br><br>However I have one customer that cannot get to it from a specific address. The IP address of my server is 75.101.149.255. When you do a "whois" on this it comes up as: <br>
<br>OrgName: Amazon.com, Inc.<br>OrgID: AMAZO-4<br>Address: Amazon Web Services, Elastic Compute Cloud, EC2<br>Address: 1200 12th Avenue South<br>City: Seattle<br>StateProv: WA<br>PostalCode: 98144<br>
Country: US<br><br>which makes perfect sense.<br><br>We originally thought that Amazon might be blocking access to the service to specific IP or IP ranges, but based on traceroutes that didn't seem to make sense.<br>
<br>When my customer tries to do a traceroute from his place to my server he doesn't even get out of his router:<br><br>tracert 75.101.149.255<br>Tracing route to [75.101.149.255] over a maximum of 30 hops:<br> 1 1 ms <1 ms <1 ms <a href="http://www.routerlogin.com">www.routerlogin.com</a> [10.1.1.1]<br>
2 * * * Request timed out.<br><br>I've never seen anything like that before. I can understand things timing out when you get to the Amazon area, but timing out before you even get into the Net proper? That doesn't make sense to me. Everything else seems to work properly from his location from what he's telling me.<br>
<br>There is a part of me that thinks there may be something wrong somehow with my customer's address. When I do a "whois" on the customer's address it comes back as being owned by IANA, which doesn't seem right at all. Also when I try a traceroute to his address *I* don't get past my router in two totally separate locations (work, that has one ISP, and home, which has a very different ISP).<br>
<br>I've never quite seen anything act like this before and I'm not quite sure how to puzzle it out. <br><br>Does anyone have any thoughts?<br>-- <br>Doc Kinne, [KQR]<br>(From the Gmail Web Interface)<br>