×

Switch Account

Can't connect to specific websites using FIOS home network and/or router

Can't connect to specific websites using FIOS home network and/or router

Reply
Highlighted
Copper Contributor MeepMeep
Copper Contributor
Posts: 7
Registered: ‎12-29-2013
Message 1 of 22
(5,933 Views)

Hi,

 

Just checking to see if anyone else is having this problem.  

 

I can't connect to a specific website if I go thru my home FIOS network/router.  On the other hand, I connect straight away to the website if I use the 3G connection on my phone or if I connect thru a VPN - which means its definitely FIOS and not my equipment.  Tried to see if resetting the router would help, but still couldn't access the website.

 

Anyway, spoke to a very helpful Verizon rep who made a valiant effort to try and figure out what was happening, but no cigar. A Verizon tech is scheduled to come by my house tomorrow to look at it.  

 

I saw that some folks in this forum had similar issues back in November, where their data packets were getting dropped on the way.  Wonder if its the same thing.  I can connect to other websites - it's just this one which isn't connecting (unfortunately, it's a really important one for me).

 

Tracert (below) shows that my data packets aren't even making it out of the Verizon network. 

 

Tracing route to cefims.ac.uk [208.231.27.28]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 11 ms 11 ms L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
3 17 ms 17 ms 15 ms G1-5-0-5.WASHDC-LCR-21.verizon-gni.net [130.81.213.70]
4 78 ms 13 ms 14 ms ae3-0.RES-BB-RTR1.verizon-gni.net [130.81.199.130]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

21 REPLIES 21
Gold Contributor VII Gold Contributor VII
Gold Contributor VII
Posts: 2,153
Registered: ‎11-10-2009

Instead of cefims.ac.uk 

Tracing route to cefims.ac.uk [208.231.27.28]

 

Try making the address www.cefims.ac.uk

Tracing route to www.cefims.co.uk [67.215.65.145]

 

Apparently work fine there and produces the same web site that my phone did after it automatically addedd www

 

 

Copper Contributor MeepMeep
Copper Contributor
Posts: 7
Registered: ‎12-29-2013

Thanks.  

 

I just tried the tracert to www.cefims.ac.uk.  It still didn't allow me to connect but this time the packets made it much further.  Wonder if its a router setting.

 

 


Tracing route to w01.cefims.wf.ulcc.ac.uk [128.86.238.85] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 7 ms L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
3 10 ms 6 ms 11 ms G1-5-0-5.WASHDC-LCR-22.verizon-gni.net [130.81.213.66]
4 7 ms 6 ms 9 ms ae2-0.RES-BB-RTR1.verizon-gni.net [130.81.199.138]
5 11 ms 7 ms 11 ms 0.xe-4-1-1.XL4.IAD8.ALTER.NET [152.63.7.237]
6 14 ms 12 ms 12 ms TenGigE0-7-2-0.GW1.IAD8.ALTER.NET [152.63.35.153]
7 8 ms 9 ms 11 ms teliasonera-gw.customer.alter.net [152.179.50.234]
8 8 ms 5 ms 7 ms ash-bb4-link.telia.net [213.155.133.232]
9 81 ms 81 ms 81 ms ldn-bb2-link.telia.net [213.248.65.209]
10 84 ms 85 ms 84 ms ldn-b3-link.telia.net [80.91.245.29]
11 84 ms 85 ms 83 ms jnt-ic-144809-ldn-b3.c.telia.net [213.248.79.146]
12 81 ms 84 ms 82 ms ae29.londpg-sbr1.ja.net [146.97.33.2]
13 84 ms 83 ms 86 ms be24.londic-rbr1.ja.net [146.97.37.198]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Gold Contributor VII Gold Contributor VII
Gold Contributor VII
Posts: 2,153
Registered: ‎11-10-2009
Message 4 of 22
(5,882 Views)

That's odd

If I ping the url it resolves to the incorrect ip address that you are getting.  I I traecrt to it it works fine.  If I use browser to access it works fine

 

There must be some dns server issue en route.  I see the attempt that resolved to w01 at leat got as far as the uk

 

C:\Users\Peter>ping -a www.cefims.ac.uk

Pinging w01.cefims.wf.ulcc.ac.uk [128.86.238.85] with 32 bytes of data&colon;
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Users\Peter>tracert www.cefims.co.uk

Tracing route to www.cefims.co.uk [67.215.65.145]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Netgear [192.168.30.1]
2 1 ms <1 ms <1 ms Westell [192.168.1.1]
3 8 ms 6 ms 6 ms L101.BSTNMA-VFTTP-66.verizon-gni.net [96.233.107
.1]
4 10 ms 10 ms 7 ms G0-3-3-7.BSTNMA-LCR-22.verizon-gni.net [130.81.1
79.24]
5 44 ms 8 ms 5 ms ae4-0.BOS-BB-RTR2.verizon-gni.net [130.81.151.84
]
6 17 ms 14 ms 14 ms 0.xe-9-0-0.BR1.NYC1.ALTER.NET [152.63.19.213]
7 15 ms 18 ms 17 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
8 16 ms 17 ms 18 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 16 ms 14 ms 14 ms ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33]

10 27 ms 24 ms 17 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]

11 17 ms 14 ms 14 ms ae-1-60.edge1.NewYork1.Level3.net [4.69.155.14]

12 16 ms 14 ms 15 ms OPEN-DNS-IN.edge1.NewYork1.Level3.net [4.78.132.
22]
13 14 ms 14 ms 19 ms 67.215.65.145

Trace complete.

C:\Users\Peter>

Gold Contributor IV
Gold Contributor IV
Posts: 1,217
Registered: ‎12-14-2009

Your trace is making it fine to the other side of the Atlantic.  The last IP address that pinged OK, 146.97.37.198, is registered to University of London Computer Centre.

 

The fact that the trace doesn't make it past that server is a problem after that Univ. of London server.  There's no setting in your router that would have any effect on that.

Gold Contributor VII Gold Contributor VII
Gold Contributor VII
Posts: 2,153
Registered: ‎11-10-2009

@eljefe wrote:

Your trace is making it fine to the other side of the Atlantic.  The last IP address that pinged OK, 146.97.37.198, is registered to University of London Computer Centre.

 

The fact that the trace doesn't make it past that server is a problem after that Univ. of London server.  There's no setting in your router that would have any effect on that.


Well sort of.

You may notice from my traces that Ping and tracert appear to resolve to different ip addresses.  The ping fails as does his tracert but my tracert works fine

 

Gold Contributor IV
Gold Contributor IV
Posts: 1,217
Registered: ‎12-14-2009

Ok.  I stand corrected.  I should've say the last address the traceroute successfully reached, instead of pinged.

 

But my point about it not being a problem that can be solved at the OP's router stands.

Gold Contributor VII Gold Contributor VII
Gold Contributor VII
Posts: 2,153
Registered: ‎11-10-2009
Message 8 of 22
(5,871 Views)

 


@MeepMeep wrote:

Hi,

 

Just checking to see if anyone else is having this problem.  

 

 

(unfortunately, it's a really important one for me).

 

 

If you are really in need of it today you could try using a UK open proxy

 

using proxy 213.133.141.197 with port 8080 will give you an appearance of being on a network in the UK.  I tried it and could access your site with no issues.

Be warned that doing this will probably have adverse effect on local access and you would not want to leave the proxy settings in position for ever.

 

95.154.199.200 port 443   is a much faster proxy

 

To set a proxy in IE

Select tools (the cog symbol)

internet options

connections

lan settings

check use proxy and key in address and port

say ok

 

To turn it off just uncheck the use proxy box

 

Gold Contributor VII Gold Contributor VII
Gold Contributor VII
Posts: 2,153
Registered: ‎11-10-2009

@eljefe wrote:

Ok.  I stand corrected.  I should've say the last address the traceroute successfully reached, instead of pinged.

 

But my point about it not being a problem that can be solved at the OP's router stands.


Not trying to correct you, trying to point out that the dns results are inconsistent from machine to machine

Do you get the results he does or do you get the results I do?

 

Gold Contributor IV
Gold Contributor IV
Posts: 1,217
Registered: ‎12-14-2009

A tracert from here is more similar to the OP's results than to yours:

 

 

Tracing route to w01.cefims.wf.ulcc.ac.uk [128.86.238.85]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     8 ms     6 ms  L100.NYCMNY-VFTTP-119.verizon-gni.net [71.241.153.1]
  3    10 ms     9 ms    10 ms  G0-7-4-1.NYCMNY-LCR-21.verizon-gni.net [130.81.169.238]
  4     7 ms     6 ms     7 ms  ae5-0.NY325-BB-RTR1.verizon-gni.net [130.81.163.208]
  5    11 ms    11 ms    12 ms  0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
  6    13 ms     9 ms    14 ms  TenGigE0-6-1-0.GW8.NYC4.ALTER.NET [152.63.21.113]
  7    18 ms    17 ms    14 ms  tinet-gw.customer.alter.net [152.179.72.122]
  8    88 ms   105 ms    91 ms  xe-5-0-1.lon10.ip4.tinet.net [89.149.184.130]
  9    87 ms    87 ms    87 ms  141.136.103.206
 10     *       88 ms    85 ms  ae29.londtw-sbr1.ja.net [146.97.33.9]
 11    91 ms    90 ms    89 ms  be24.londsh-rbr1.ja.net [146.97.37.210]
 12    88 ms    89 ms    90 ms  ulcc-1.ja.net [146.97.137.54]
 13    85 ms    86 ms    86 ms  fw.ulcc.net [128.86.200.178]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

 

 

 

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.