I'm unable to access my homepage website from my verizon fios at home. The url is www.vimarsh.com. The website works fine from other ISPs. DNS is resolving fine. Not only this website but a few other websites on the same server are inaccessible.
Is there some verizon firewall which is blocking the server? The server address is star.lunarpages.com or 184.108.40.206
Your URL opens fine here in NY. I can't imagine there's a Verizon firewall blocking your access but maybe some routing issue from your part of the country to your server?
If you're using a Verizon issued router you might try resetting it to the default settings. There have been a case or two reported here where a user had been issued a recycled router and it had a setting buried in it that caused access issues.
Well I can access it just fine from a Verizon connection, so I dont think Verizon is purposely blocking it.
Try running a tracert. That way we can tell if it is navigating the Verizon network or not. It is possible to be blocked on the other end. There was a rash of posts earlier this summer from people unable to access some websites that turned out to be that the websites were blocking some Verizon IP addresses. Lets see if that is what is happening to you.
Go to your command prompt (if you dont know how to do this, post back with the version of windows that you have)
post back the results
Error exists between keyboard and chair.
the site is hosted on lunarpages.
that can be the case, lunarpages blocking my ip - donno why. i'll contact them. thanks.
here is the tracert
Re: Cannot access website from fios at home[ Edited ]
11-06-2010 09:03 AM - edited 11-06-2010 09:09 AM
Is it working now? No issues tracert from the East coast. It could be software on your PC that is preventing the redirect. The domain name vimarsh.com does not match the end result, which is star.lunarpages.com. Or an issue with Level3's routers. Got me.
NeoTrace Trace Version 3.25 - TRIAL Results
Date: 11/6/2010 (Saturday), 12:00:36 PM
Node Net Reg IP Address Location Node Name
1 - - 192.168.3.201 WASHINGTON D.C. xxxxxxx
2 1 - 192.168.3.1 Unknown
3 1 - 192.168.1.1 Unknown ipcop.localdomain
4 2 - x.x.x.x Unknown
5 3 1 220.127.116.11 WASHINGTON D.C. g15-0-6-292.washdc-lcr-02.verizon-gni.net
6 3 1 18.104.22.168 38.961N, 77.339W so-3-0-0-0.res-bb-rtr2.verizon-gni.net
7 4 2 22.214.171.124 WASHINGTON D.C. 0.ae2.br1.iad8.alter.net
8 5 3 126.96.36.199 WASHINGTON D.C. ae7.edge1.washingtondc4.level3.net
9 5 3 188.8.131.52 WASHINGTON D.C. vlan69.csw1.washington1.level3.net
10 5 3 184.108.40.206 WASHINGTON D.C. ae-71-71.ebr1.washington1.level3.net
11 5 3 220.127.116.11 Atlanta ae-2-2.ebr3.atlanta2.level3.net
12 5 3 18.104.22.168 Dallas ae-7-7.ebr3.dallas1.level3.net
13 5 3 22.214.171.124 Dallas ae-82-88.ebr2.dallas1.level3.net
14 5 3 126.96.36.199 San Diego ae-4-4.car2.sandiego1.level3.net
15 5 3 188.8.131.52 San Diego add2net-inc.car2.sandiego1.level3.net
16 6 4 184.108.40.206 Anaheim star.lunarpages.com