jedawson
@transedge.c
| email/http/ftp server access blocked over Fios
For the last several days I have suddenly been unable to access the server where my personal website and email is hosted. This occurred suddenly over the weekend, and access to each of these servers from other locations is uninterrupted. My Internet access generally over Fios is still fine.
I have now spent over 2.5 hours on the phone with the people at the Verizon Fiber Solutions Center to no avail.
I am using 2 separate computers - one PC plugged into the router directly via Ethernet cable, and a laptop connecting wirelessly, three different web browsers and email programs, all without success. I have unplugged both my home n/w and my Vonage routers from the configuration to see if those were causing the problem, but again to no avail. I am therefore 100% sure the problem is not at my end. My website hosting service also assures me there's been no change at their end either.
Any suggestions? I'm seriously considering jumping ship to Comcast... |
|
PetePuma
How many lumps do you want
Premium,MVM
join:2002-06-13
Arlington, VA | Can you post a traceroute to the server? |
|
jedawson
@verizon.net | I am away from home at the moment but I have tried traceroute and it tends to break down after about 15 hops. |
|
degauss1
join:2001-07-02
Hillsboro, OR
 ·ViaTalk
 ·Verizon FIOS
 ·Comcast
·Axvoice
| reply to jedawson
Hmm let me see if I have this straight.
1. You say people from various networks can get to your servers hosted by some company somewhere.
2. You can reach ftp/http/pop/smtp service on networks other than your hosting provider without issue.
3. Verizon say they are not blocking stuff.
4. The hosting provider says it's not a problem on their end.
Hmmm yeah, sure sounds like port blocking to me. Right. Perhaps if you posted more troubleshooting information we could assist. My initial guess is that what you really have are DNS issues. Have you tried accessing these hosted service via direct IP address?
I've seen problems just like this with my Comcast connection. They've had more than their share of DNS server issues lately. |
|
jedawson
join:2005-06-15
| That summary is correct. In other words,
1. I am able to access the ftp/http/pop/smtp servers associated with my domain from other PCs (e.g. at work)
2. I am able to access other ftp/http/pop/smtp over my Fios connection
3. I am unable to access the ftp/http/pop/smtp servers associated with my domain over my Fios connection
I asked about port blocking but Verizon said they only block 25 and 80, which shouldn't really affect me as long as I'm not hosting the server on my Fios-connected PC.
I have tried accessing the server via the IP address directly - that doesn't work. They also walked me through re-setting my DNS settings etc. over the phone yesterday, to no avail.
What other information would help you help me? |
|
cdru
Go Colts
Premium,MVM
join:2003-05-14
Fort Wayne, IN
| reply to jedawson
said by jedawson  :I am away from home at the moment but I have tried traceroute and it tends to break down after about 15 hops. If it indeed is after 15 hops, you are most likely outside the Verizon controlled network unless you are stuck in some type of a routing loop.
--
"What gives them the right to come in and do this?" she said. - Lady complaining that she was getting FIOS in her backyard. |
|
jedawson
join:2005-06-15
| I've just run the traceroute test again three times, and every time it appears to get stuck in the same place:
13 gphou-66-98-241-126.ev1.net (66.98.241.126) 56.373 ms 56.876 ms 56.904 ms
It makes the first 13 hops the same way every time, and this is the last hop. It then times out at this stage.
Any suggestions? |
|
Chris123NT
join:2001-11-24
Nesconset, NY
·Verizon FIOS
| reply to jedawson
Looks like a problem with EV1's routing OR it doesn't like your IP address. Try rebooting the ONT/Router and getting a new IP, see if that helps the problem.
--
Its not about what you do, Its about HOW you do it  |
|
idea-in NJ
@comcast.n |  reply to jedawson
Did you check connecting by ip address and/or do a tracert to see where there's a problem?
You could do an nslookup to see what VZ is resolving your hosts to...maybe they have a DNS problem they're unaware of (it's happened before). |
|
jedawson
join:2005-06-15 | 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 |
|
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. |
|
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. |
|
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 :: [ |
|
NOCMan
Verizon Fios User
Premium
join:2004-09-30
Flower Mound, TX
| reply to jedawson
Let me get this straight?
Servers at EV1? If so then you need to contact EV1 about the problem as it's out on the internet and verizon is pretty much powerless to fix it. Just looking at a traceroute it's clear that it's dieing on EV1's network (Firewall, bad bgp routing or something else) contact your hosting provider and they should be able to fix it. |
|
jedawson
join:2005-06-15 | DaSneaky1D -
I have sent you an email via the site with my IP address details etc. Let me know if there's some other better way to contact you. |
|
GernBlanston
join:2005-01-08
51464 | reply to jedawson
How on earth is this a Verizon problem?
You're way out on the internet when this issue takes hold, and apparently you're able to browse anywhere else pretty much flawlessly, no? |
|
alphaxp
join:2005-07-01
Rowlett, TX
| reply to jedawson
I am having the same problem with my FIOS. Can't get to a site that I know works from Earthlink DSL and SBC. I also did tracert and found it timing out at ivhou-207-218-223-106.ev1.net
Apparently the same place as your problem.
IP I was going to was 64.246.62.117
I plan to call Verizon tomorrow. |
|
alphaxp
join:2005-07-01
Rowlett, TX | Just tried rebooting the D-Link router to get another IP address for WAN. Can now get to the URL. Apparently there is a problem with the IP address block I had for my WAN. |
|
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? |
|
lgkahn
Premium
join:2005-02-15
Londonderry, NH
·Comcast
 ·Verizon Online DSL
| reply to jedawson
I am on verizon and it works for me.. the way you can test is telnet to port 80 on the ip and type some crap and hit return you should get something like this
501 Method
Not Implemented
Method Not Implemented
c to /index.h
tml not supported.
Invalid method in request c
Connection to host lost. |
|
