Re: email/http/ftp server access blocked over Fios

Author	All Replies
jedawson join:2005-06-15	reply to idea-in NJ Re: email/http/ftp server access blocked over Fios See my previous comments in response to your first question - yes, I have tried direct IP address instead of URL, and have also done a traceroute. However, I haven't tried the nslookup. How would I go about doing that? Thanks
jedawson join:2005-06-15	to forum · permalink · · 2005-06-15 13:50:00 ·
PONman join:2005-06-09 Fairfax, VA	If you have tried the IP (the one that worked at your office) than an nslookup wont really help. This will only tell you what IP Verizon is resolving the URL to. And if using the IP doesn't work, than you have a routing problem, not a DNS issue. The next step is to identify where the route breaks down. Post a tracert (and one from work if you got it) and maybe we can help. Also, try using a proxy to see if you can access the http portion. www.guardster.com is a free webproxy that you could use to check if you can get access to the http.
PONman join:2005-06-09 Fairfax, VA	to forum · permalink · · 2005-06-15 14:07:26 ·
jedawson join:2005-06-15	Guardster.com worked - so what does that tell me? Tracert from home: traceroute to [mydomain], 30 hops max, 40 byte packets 1 10.9.22.1 (10.9.22.1) 2.87 ms 2.603 ms 2.483 ms 2 130.81.32.80 (130.81.32.80) 2.389 ms 2.236 ms 2.256 ms 3 130.81.10.90 (130.81.10.90) 49.432 ms 19.84 ms 19.614 ms 4 130.81.15.42 (130.81.15.42) 20.027 ms 19.818 ms 19.754 ms 5 so-4-0-0.mpr2.iad2.us.above.net (64.125.30.122) 32.199 ms 20.597 ms 20.971 ms 6 so-4-0-0.mpr1.iad1.us.above.net (64.125.28.213) 21.048 ms 20.868 ms 20.702 ms 7 so-1-0-0.cr1.dca2.us.above.net (64.125.28.125) 20.846 ms 21.225 ms 20.994 ms 8 so-4-0-0.mpr2.atl6.us.above.net (64.125.28.230) 66.507 ms 117.034 ms 32.425 ms 9 so-0-0-0.mpr1.atl6.us.above.net (64.125.27.49) 32.662 ms 32.337 ms 32.197 ms 10 so-4-3-0.mpr2.iah1.us.above.net (64.125.31.25) 55.524 ms 55.615 ms 55.767 ms 11 t289.216-200-251-162.iah1.us.above.net (216.200.251.162) 56.182 ms 56.186 ms 56.32 ms 12 66.98.241.27 (66.98.241.27) 56.231 ms 56.316 ms 56.367 ms 13 gphou-66-98-241-126.ev1.net (66.98.241.126) 56.373 ms 56.876 ms 56.904 ms 14 * * * Tracert from work seems to get stuck at the same point, although at work I'm actually able to access the site.
jedawson join:2005-06-15	to forum · permalink · · 2005-06-15 14:25:15 ·
DaSneaky1D one wall to block them all Premium,MVM join:2001-03-29 The Lou ·Charter Pipeline	reply to jedawson As Chris123NT suggested, the problem is either a routing problem on EV's network, or the netblock you are currently part of isn't being routed correctly. I work at an ISP, not Verizon. If you want you can PM me your IP address and I can see if it's being broadcast to our network. If not, you can do a whois lookup and see what netblock it is part of. It could be a part of a previously denied IP range that needs to be updated manually by every ISP blocking it. Verizon could not be broadcasting it correctly. No way to troubleshoot this with so little information being given. -- ] :: my trivial ramblings :: [
	to forum · permalink · · 2005-06-15 14:27:10 ·
TheOtherPete join:2001-06-28 Boyds, MD 1 edit	reply to jedawson said by jedawson : Guardster.com worked - so what does that tell me? Tracert from home: traceroute to [mydomain], 30 hops max, 40 byte packets 1 10.9.22.1 (10.9.22.1) 2.87 ms 2.603 ms 2.483 ms 2 130.81.32.80 (130.81.32.80) 2.389 ms 2.236 ms 2.256 ms 3 130.81.10.90 (130.81.10.90) 49.432 ms 19.84 ms 19.614 ms 4 130.81.15.42 (130.81.15.42) 20.027 ms 19.818 ms 19.754 ms 5 so-4-0-0.mpr2.iad2.us.above.net (64.125.30.122) 32.199 ms 20.597 ms 20.971 ms 6 so-4-0-0.mpr1.iad1.us.above.net (64.125.28.213) 21.048 ms 20.868 ms 20.702 ms 7 so-1-0-0.cr1.dca2.us.above.net (64.125.28.125) 20.846 ms 21.225 ms 20.994 ms 8 so-4-0-0.mpr2.atl6.us.above.net (64.125.28.230) 66.507 ms 117.034 ms 32.425 ms 9 so-0-0-0.mpr1.atl6.us.above.net (64.125.27.49) 32.662 ms 32.337 ms 32.197 ms 10 so-4-3-0.mpr2.iah1.us.above.net (64.125.31.25) 55.524 ms 55.615 ms 55.767 ms 11 t289.216-200-251-162.iah1.us.above.net (216.200.251.162) 56.182 ms 56.186 ms 56.32 ms 12 66.98.241.27 (66.98.241.27) 56.231 ms 56.316 ms 56.367 ms 13 gphou-66-98-241-126.ev1.net (66.98.241.126) 56.373 ms 56.876 ms 56.904 ms 14 * * * Tracert from work seems to get stuck at the same point, although at work I'm actually able to access the site. What no one here seems to have noticed is that traceroute != http. Just because ICMP (traceroute) packets are blocked at a certain point does not mean that is the problem you are having with http/ftp/smtp. ICMP packets are routinely blocked at border devices (firewalls) for security reasons. The fact that your traceroute dies at the same point at work as from home is the big clue that you are diagnosing a non-problem e.g. the traceroute is not telling you anything about your problem other than the fact that your routing appears to be fine. Now I agree if you can surf everywhere else but your site it seems unlikely that Verizon would be blocking your particular site but the fact that you can traceroute 15 hops out does not mean that your HTTP packets are not being dropped at Verizon (although I agree that it doesnt make sense) Can you surf to other web sites in the same net space as your domain? E.g. if you change the last octet and just try random addresses can you browse to any sites?
TheOtherPete join:2001-06-28 Boyds, MD 1 edit	to forum · permalink · · 2005-07-01 07:44:47 ·


Thursday, 03-Dec 14:04:51	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com.republican-creole page compression OFF