Question locked out of http site with chrome , edge or applications.

[robertsimoneau1955]

I first noticed this problem while using N3FJP amatuer radio logging software. If I picked help it would lockup trying to reach http:\\www.n3fjp.com. This problem has existed a long time now. I have troubleshot to find it is not just the N3FJP site, but all http sites. I can fix it temporarily by going into my router and releasing my IP address, then renewing. How long it will work is any man's guess. The whole house of computers, one macbook, two pc, two laptops and one tablet lose the ability to reach http sites, until I release and renew my ip address on the router. If I open and connect my VPN (NordVPN) on my computer, I can then reach the sites. If I take my phone off the FIOS network and use data, and turn on the hotspot, hook my home computer to that hotspot, I can reach the sites. It is definitely FIOS Network related. The router is a G3100 Firmware 3.1.0.13. I believe I have eliminated it being a computer problem, as it happens on every inhouse computer. The fact that behind a VPN it works, leads me to believe it is not the rounter. I am open to any suggestions, this is driving me up a wall. Here is an example for when it is broken:

C:\Users\robertsimoneau>ping n3fjp.com

Pinging n3fjp.com [192.64.150.103] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.64.150.103:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Turn on VPN
C:\Users\robertsimoneau>ping n3fjp.com

Pinging n3fjp.com [192.64.150.103] with 32 bytes of data:
Reply from 192.64.150.103: bytes=32 time=10ms TTL=56
Reply from 192.64.150.103: bytes=32 time=11ms TTL=56
Reply from 192.64.150.103: bytes=32 time=11ms TTL=56
Reply from 192.64.150.103: bytes=32 time=11ms TTL=56

Ping statistics for 192.64.150.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

Fails to reach N2FJP site and times out.

C:\Users\robertsimoneau>tracert n3fjp.com

Tracing route to n3fjp.com [192.64.150.103]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms G3100.myfiosgateway.com [192.168.1.1]
2 4 ms 5 ms 4 ms N3FJP [192.64.150.103]

Trace complete.

Turn on VPN and it reaches the site.

C:\Users\robertsimoneau>tracert n3fjp.com

Tracing route to n3fjp.com [192.64.150.103]
over a maximum of 30 hops:

1 * 11 ms 10 ms 10.5.0.1
2 11 ms 11 ms 10 ms vlan121.as22.nyc1.us.m247.com [37.120.138.169]
3 13 ms 11 ms 12 ms 193.27.15.166
4 12 ms * 10 ms hu0-6-0-3.rcr21.ewr03.atlas.cogentco.com [38.122.35.209]
5 11 ms 10 ms 12 ms be3506.nr51.b020857-1.ewr03.atlas.cogentco.com [154.24.7.110]
6 10 ms 10 ms 10 ms te0-0-2-3.nr15.b020857-1.ewr03.atlas.cogentco.com [154.24.35.238]
7 11 ms 17 ms 12 ms 38.32.103.58
8 11 ms 11 ms 11 ms web103.dnchosting.com [192.64.150.103]

Trace complete.

 

[ex_bubblehead]

As a test try switching to an outside DNS provider instead of your ISP, such as Google's public DNS servers:

Primary: 8.8.8.8
Secondary: 8.8.4.4

 

[bill001g]

??

Tracing route to n3fjp.com [192.64.150.103]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms G3100.myfiosgateway.com [192.168.1.1]
2 4 ms 5 ms 4 ms N3FJP [192.64.150.103]

...........................

So where did you do this trace. This actually claims the server did respond.

This is extremely strange. It is acting like this is a site that is directly on your ISP network which it is not. From what I can tell the only way to reach this site your traffic must pass through one of 2 large ISP, cogent or zayo. Your VPN trace passes via cogent.

Using some advanced tools that I won't explain this what the actual route look like in a number of different large ISP including verizon.

Path #1: Received by speaker 0
Not advertised to any peer
6461 399522
64.125.15.66 (metric 5736) from 129.250.0.2 (129.250.0.2)
Origin IGP, metric 4294967294, localpref 100, valid, confed-internal
Received Path ID 0, Local Path ID 0, version 0
Community: 2914:390 2914:1003 2914:2000 2914:3000 65504:6461
Path #2: Received by speaker 0
Not advertised to any peer
174 399522
154.54.9.41 (metric 5601) from 129.250.0.9 (129.250.0.9)
Origin IGP, metric 4294967294, localpref 100, valid, confed-internal
Received Path ID 0, Local Path ID 0, version 0
Community: 2914:390 2914:1006 2914:2000 2914:3000 65504:174

What this shows is the traffic must pass at least 3 ISP routers at the very minimum. You should see a verizon router, then either a zayo or cogent router, and then finally a router in the isp that owns the server (this ISP has a number 399522). There always tends to be many more than just 1 routers in each ISP.

>>>>>>>>>>>>

This is acting like there is some server that is hijacking the IP address. If it was just dropped you could think maybe verizon blocked it or had the routing messed up in a router near your house . The problem with that theory is you actually get a response from the tracert.

What is even more strange is the response on the tracert is 5ms away which tends to mean it is not in your house.

Did you set anything related to this IP in your router like static routes or port forwarding rules.