cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Aspiring Contributor
3,158 Views
Message 21 of 313

Re: BT Infinity and https connection issues

Still happening!

 

It's not a PC issue but willing to accept it's a BT Hub 3 issue or white modem. Why - well, I've tried the HTTPS website on Windows XP, a Windows 7 computer and an Android phone in the house - all don't connect to it. I disconnect from WIFI on the phone and run through the G connection - website loads fine.

0 Ratings
Highlighted
Aspiring Contributor
3,053 Views
Message 22 of 313

Re: BT Infinity and https connection issues

In response to the original poster. I've recently upgraded to BT Infinity, in the Portishead area also, from BT Broadband. I'm experiencing similar issues in particular the Natwest HTTPS login just times out. Also had new issues with things like Ventrilo outgoing voice and other random sites. Almost seems like there are routing issues on the new network as some sites work well others just hang. As with you, this is truely independent of PC, operating system or hardware as I get the same happening to the same sites on my work PC, Home PC and iPhone via the same hub. Previous to Infinity install ALL these were able to connect to the sites in question. So Infinity is the only variable thats changed. If I find anything out I'll post here.
0 Ratings
Highlighted
Aspiring Contributor
3,044 Views
Message 23 of 313

Re: BT Infinity and https connection issues

Tried setting up port forwarding on the hub for HTTPS and Ventrilo.  Still no change in the behaviour when trying to access these sites or use these applications.  Other Https sites work successfully so not sure how that fits in?

 

However I have seen on this forum that the Hub 3 Portforwarding has been reported by many users as broken as far back as March and there are still ongoing issues.

 

Kev

0 Ratings
Highlighted
Aspiring Contributor
3,022 Views
Message 24 of 313

Re: BT Infinity and https connection issues

Update:

 

I've tested 2 external Ventrillo servers, one of which lags out the other doesn't.  Therfore this is a test of the same software/hardware.  Only the core routing is different.   Below is a pathping for the one thats not working.  100% loss on the some hops.  This could be due to the routers being protected in some way but I'd like a Moderator to comment and investigate please?  I suspect this is also why https://www.nwolb.com/ is very slow/times out and other secure sites don't.  The routing will be different.

 

pathping -q 100 82.103.143.138

Tracing route to v66.darkstarllc.com [82.103.143.138]
over a maximum of 30 hops:
  0  ASUS.home [192.168.1.66]
  1  api.home [192.168.1.254]
  2  217.32.141.5
  3  217.32.140.222
  4  213.120.161.34
  5  217.41.222.26
  6  217.41.222.178
  7  acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.248.70]
  8  core1-te0-2-5-0.ealing.ukcore.bt.net [109.159.248.0]
  9  transit1-xe11-0-0.ealing.ukcore.bt.net [62.6.200.110]
 10  t2c3-xe-10-1-0.uk-eal.eu.bt.net [166.49.168.5]
 11  t2c1-ge7-2.uk-glo.eu.bt.net [166.49.237.29]
 12  t2c2-p3-0-0.uk-lon1.eu.bt.net [166.49.208.210]
 13  t2a1-ge6-0.uk-lon1.eu.bt.net [166.49.135.17]
 14  te9-8.ccr01.lon01.atlas.cogentco.com [130.117.14.49]
 15  te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.110]
 16  te0-3-0-0.ccr21.ams03.atlas.cogentco.com [130.117.48.142]
 17  te0-0-0-0.ccr21.ham01.atlas.cogentco.com [130.117.50.42]
 18  te1-1.ccr01.cph01.atlas.cogentco.com [130.117.2.150]
 19  149.6.136.138
 20  v66.darkstarllc.com [82.103.143.138]

Computing statistics for 500 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ASUS.home [192.168.1.66]
                                           0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  api.home [192.168.1.254]
                                           0/ 100 =  0%   |
  2    7ms     0/ 100 =  0%     0/ 100 =  0%  217.32.141.5
                                           0/ 100 =  0%   |
  3   10ms     0/ 100 =  0%     0/ 100 =  0%  217.32.140.222
                                            0/ 100 =  0%   |
  4   11ms     0/ 100 =  0%     0/ 100 =  0%  213.120.161.34
                                            0/ 100 =  0%   |
  5  ---     100/ 100 =100%   100/ 100 =100%  217.41.222.26
                                            0/ 100 =  0%   |
  6   11ms     0/ 100 =  0%     0/ 100 =  0%  217.41.222.178
                                            0/ 100 =  0%   |
  7  ---     100/ 100 =100%   100/ 100 =100%  acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.248.70]
                                             0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  core1-te0-2-5-0.ealing.ukcore.bt.net [109.159.248.0]
                                             0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  transit1-xe11-0-0.ealing.ukcore.bt.net [62.6.200.110]
                                             0/ 100 =  0%   |
 10   23ms     1/ 100 =  1%     1/ 100 =  1%  t2c3-xe-10-1-0.uk-eal.eu.bt.net [166.49.168.5]
                                             0/ 100 =  0%   |
 11   18ms     0/ 100 =  0%     0/ 100 =  0%  t2c1-ge7-2.uk-glo.eu.bt.net [166.49.237.29]
                                             0/ 100 =  0%   |
 12   18ms     0/ 100 =  0%     0/ 100 =  0%  t2c2-p3-0-0.uk-lon1.eu.bt.net [166.49.208.210]
                                             0/ 100 =  0%   |
 13   16ms     0/ 100 =  0%     0/ 100 =  0%  t2a1-ge6-0.uk-lon1.eu.bt.net [166.49.135.17]
                                             0/ 100 =  0%   |
 14   49ms     0/ 100 =  0%     0/ 100 =  0%  te9-8.ccr01.lon01.atlas.cogentco.com [130.117.14.49]
                                             0/ 100 =  0%   |
 15   33ms     0/ 100 =  0%     0/ 100 =  0%  te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.110]
                                             0/ 100 =  0%   |
 16   34ms     0/ 100 =  0%     0/ 100 =  0%  te0-3-0-0.ccr21.ams03.atlas.cogentco.com [130.117.48.142]
                                             0/ 100 =  0%   |
 17   41ms     0/ 100 =  0%     0/ 100 =  0%  te0-0-0-0.ccr21.ham01.atlas.cogentco.com [130.117.50.42]
                                             0/ 100 =  0%   |
 18   64ms     0/ 100 =  0%     0/ 100 =  0%  te1-1.ccr01.cph01.atlas.cogentco.com [130.117.2.150]
                                             0/ 100 =  0%   |
 19   51ms     0/ 100 =  0%     0/ 100 =  0%  149.6.136.138
                                             0/ 100 =  0%   |
 20   51ms     0/ 100 =  0%     0/ 100 =  0%  v66.darkstarllc.com [82.103.143.138]

Trace complete.

0 Ratings
Highlighted
Aspiring Contributor
3,013 Views
Message 25 of 313

Re: BT Infinity and https connection issues

And here's the Tracert for the Natwest Online Banking.  There are definately core network issues here...

 

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

>tracert www.nwolb.com

Tracing route to www.nwolb.com [155.136.72.107]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  api.home [192.168.1.254]
  2     7 ms     7 ms     7 ms  217.32.141.5
  3     8 ms     8 ms     8 ms  217.32.140.222
  4    12 ms    11 ms    12 ms  213.120.161.34
  5    12 ms    11 ms    11 ms  217.41.222.26
  6    12 ms    11 ms    12 ms  217.41.222.178
  7    13 ms    12 ms    13 ms  acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.248.70]
  8    23 ms    23 ms    24 ms  core1-te0-2-5-0.ealing.ukcore.bt.net [109.159.248.0]
  9    23 ms    23 ms    23 ms  core1-pos1-0.birmingham.ukcore.bt.net [62.172.103.81]
 10    33 ms    33 ms    33 ms  core1-pch4.reading.ukcore.bt.net [62.6.204.134]
 11    33 ms    33 ms    32 ms  interconnect1-gig2-0.edinburgh.fixed.bt.net [62.6.199.35]
 12    32 ms    32 ms    32 ms  62.172.57.238
 13    32 ms    32 ms    32 ms  194.72.41.158
 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.

0 Ratings
Highlighted
Aspiring Contributor
3,004 Views
Message 26 of 313

Re: BT Infinity and https connection issues

Final update:

 

Natwest support directed a hub and router reset (with a 10 minute) down time to force a new connection.  This new connection solved both the Natwest Online Banking Secure login and Ventrillo ruoting issues.  However they stated that they had seen quite an increase in these routing problems from BT and Orange networks since Nov 2010.

 

Hope a reset solves any issues you may find also

 

 

0 Ratings
Highlighted
Recognised Expert
2,987 Views
Message 27 of 313

Re: BT Infinity and https connection issues


@Mirski wrote:

Final update:

 

Natwest support directed a hub and router reset (with a 10 minute) down time to force a new connection.  This new connection solved both the Natwest Online Banking Secure login and Ventrillo ruoting issues.  However they stated that they had seen quite an increase in these routing problems from BT and Orange networks since Nov 2010.

 

Hope a reset solves any issues you may find also

 

 


Hi there,

 

I've been reading the thread with some interest and it seems to me that there may be an issue with BT's DNS servers, hence the reason that some sites are unreachable, others time out and still others remain accessible.

 

Here's what I would suggest: use either Google DNS or Open DNS, instead of the default BT DNS settings in the HomeHub and hopefully you should find that you can connect as usual.

 

I hope this info helps. 😄

 

0 Ratings
Highlighted
Recognised Expert
2,982 Views
Message 28 of 313

Re: BT Infinity and https connection issues

Instant for me too,IE8.
But I have OpenDNS servers for DNS in my router.

208.67.222.222

208.67.220.220

 

 

 

0 Ratings
Highlighted
Aspiring Contributor
2,906 Views
Message 29 of 313

Re: BT Infinity and https connection issues

Thanks for the feedback.  I've encountered random routing issues (Slow or blocked pings are points in the Tracert and VPN issues) since the router restart.  Doing another power cycle on the router and hub tends to clear these again until it all happens again and another restart is necessary.  Why I should need to reboot my router to clear out issues on the network is baffelling but it seems the only effective solution.

 

I'll try the other DNS server if this continues.  If it proves to be BT's DNS server and Infinity routing then shame on them.  Major data provider being unable to give reliable consistant routing is in-excusable...

 

 

0 Ratings
Highlighted
Beginner
2,858 Views
Message 30 of 313

Re: BT Infinity and https connection issues

Also having the same issue and I'm also in the Portishead area.  BT ought to have fixed this by now, ridiculous.

 

We have the older BT Home Hub so it's not specific to BT Home Hub 3.  It's a problem with their network, but try convincing them that over the telephone! Smiley Wink

 

I don't think this a DNS issue, if it was it would get stuck on "Connecting to <website>..."

0 Ratings