- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm hoping you can help me with something that's beyond my skill level.
I suddenly cannot access www.dokuwiki.org over my Verizon FIOS connection. When I try, it just times out. Running the suggested Windows networking troubleshooter, it says dokuwiki.org is available, but not responding to requests.
Alarmingly, once in a great while when I try to access dokuwiki.org over FIOS, I get a malware site! I'm positive this is not due to a typo, there's something funny going on.
Also, if I first set up a VPN connection, or if I use my work VPN, I can access dokuwiki.org just fine.
Same is true on my cell phone. If I try dokuwiki.org when the phone's connected to my FIOS WiFi, it times out or, occassionaly takes me to a malware site. If I turn off WiFi and use the cell phone's T-Mobile cell network, I can access dokuwiki.org just fine.
Clearly something is wrong, and based on the test with my cell phone, I don't think it's my setup. I think there's something wrong on the FIOS network somehow.
But I don't know enough to pinpoint the problem. Also, I don't really know how to report it to Verizon w/o spending hours talking to tech support people who just want me to unplug and re-plug in my router.
Any thoughts?
Thx!
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay, waited 2-3 days and now it's working w/o any changes on my part.
To reiterate, last weekend I tried to reach www.dokuwiki.org -- a site I've been visiting without issue for months -- using 3 different devices and none of them could reach that site using my home Verizon FIOS connection, but all of them could reach that site if I used another network (i.e., took them to work, use a public WiFi spot, VPN to another network, anything but my home Verizon FIOS network).
Now, 3 days later, I can reach www.dokuwiki.org just fine with all 3 devices over my Verizon FIOS connection -- and no changes to anything.
Not sure what it was, but it's unlikely this problem a) suddenly appeared, and then (b) suddenly disappeared for no reason at all. Since there were no changes to anything on my end, I'm pretty sure Verizon found and fixed a configuration issue.
In any case, over and out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you ping the website?
Or do a traceroute to it?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can and will do both when I get home this evening.
Thx!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As requested...a ping and tracert from my FIOS connection to www.dokuwiki.org
Again, thank you very much for helping me with this.
-- dgg
ping www.dokuwiki.org
Pinging www.dokuwiki.org [138.201.137.132] with 32 bytes of data:
Reply from 138.201.137.132: bytes=32 time=115ms TTL=56
Reply from 138.201.137.132: bytes=32 time=115ms TTL=56
Reply from 138.201.137.132: bytes=32 time=127ms TTL=56
Ping statistics for 138.201.137.132:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 127ms, Average = 119ms
Control-C
C:\WINDOWS\system32>tracert www.dokuwiki.org
Tracing route to www.dokuwiki.org [138.201.137.132]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.1.1
2 23 ms 7 ms 8 ms lo0-100.NRFLVA-VFTTP-306.verizon-gni.net [96.238.95.1]
3 11 ms 7 ms 11 ms B3306.NRFLVA-LCR-21.verizon-gni.net [100.41.219.6]
4 * * * Request timed out.
5 * * * Request timed out.
6 21 ms 16 ms 18 ms 0.ae9.GW11.IAD8.ALTER.NET [140.222.234.13]
7 18 ms 18 ms 18 ms teliasonera-gw.customer.alter.net [204.148.11.138]
8 19 ms 16 ms 18 ms ash-bb4-link.telia.net [213.155.130.58]
9 112 ms 114 ms 113 ms ffm-bb3-link.telia.net [62.115.141.109]
10 114 ms 111 ms 113 ms ffm-b4-link.telia.net [62.115.125.223]
11 122 ms 122 ms 122 ms ae10-0.fra10.core-backbone.com [62.115.9.226]
12 121 ms 119 ms 117 ms ae10-2021.fra20.core-backbone.com [80.255.14.6]
13 112 ms 109 ms 109 ms core-backbone-100g-fra.hetzner.de [80.255.15.122]
14 110 ms 112 ms 113 ms core4.fra.hetzner.com [213.239.245.2]
15 116 ms 113 ms 113 ms core23.fsn1.hetzner.com [213.239.229.74]
16 112 ms 114 ms 113 ms ex9k2.rz17.hetzner.de [213.239.229.18]
17 115 ms 118 ms 118 ms piggy.dokuwiki.org [138.201.137.132]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So it looks as though there is not a network issue accessing the site.
I clicked on the URL on your original post and the screen pops right up.
Not sure why it isn't working for you, but at least in my area (Maryland) I don't have any issues accessing the site.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>> So it looks as though there is not a network issue accessing the site. <<
Not really. If you look at the tracert, there's two spots that time out, and the tracert command took about 2 minutes to run...way, way longer than it should.
Given that, it shouldn't be surprising that my attempts to access the site time out.
And the critical part is none of this happens if I VPN from the same spot in VA to a server located in NYC, and then access the site. It pops right up.
I believe there's something wrong with the Verizion FIOS routing to this site.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Timeouts are not uncommon on trade routes.
a lot of devices in the core of networks are set to not respond.
I'll bet if you trace route to other sites, you will also see timeouts.
the fact that you can ping the website and trace route to it proves no network routing issues.
can't explain why VPN works and not direct. Like I said, it works fine for me.
have you tried clearing browser cache?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay, waited 2-3 days and now it's working w/o any changes on my part.
To reiterate, last weekend I tried to reach www.dokuwiki.org -- a site I've been visiting without issue for months -- using 3 different devices and none of them could reach that site using my home Verizon FIOS connection, but all of them could reach that site if I used another network (i.e., took them to work, use a public WiFi spot, VPN to another network, anything but my home Verizon FIOS network).
Now, 3 days later, I can reach www.dokuwiki.org just fine with all 3 devices over my Verizon FIOS connection -- and no changes to anything.
Not sure what it was, but it's unlikely this problem a) suddenly appeared, and then (b) suddenly disappeared for no reason at all. Since there were no changes to anything on my end, I'm pretty sure Verizon found and fixed a configuration issue.
In any case, over and out.