Hello all,
I was wondering if anyone might be able to shed any light on this problem.
I made a post about the issue in the BT Infinity thread, but I'm not sure that's the problem here.
The scenario is, we used to have the BT Hub 5 with BT Infinity. It worked perfectly with all my devices, never had any real issues with the WiFi connectivity. As of this month, I've renegotiated the contract with BT and upgraded to the BT Smart Hub (Hub 6).
We received the new hub as of Monday. It's all set up and everything is working perfectly, except my phone (HTC One M8, Android 6.0). It was working fine at first, but as of Tuesday the phone refuses to connect to most websites whilst connected to the WiFi network. In Chrome, I get "This site cant be reached" and ERR_CONNECTION_REFUSED error displayed.
My phone is the only device on the wireless network which does this. My girlfriends iPhone works fine and our Galaxy Tab 10.1 (also an Android device) is also unaffected. It is only my phone, and it is only (most) websites that wont load. Services such as YouTube, WhatsApp, Facebook etc seem to work, albeit slowly, so the phone appears to be connected successfully, just refusing website traffic.
I've done some hunting and found a few common problems which appear very similar and I've tried the following which were listed as solutions:
- Setting the SmartHub to use separate 2.4GHz and 5.GHz wireless SSIDs. Apparently this solves a very similar Android issue.
- Enabling Dynamis DNS on the Hub and setting it to use a DNS Service ("NoIP" - I was going to use Google DNS but it wasn't on the supported list on the hub options screen.
Neither of these solutions have worked, although using a dynamic DNS seems to have improved website loading times on other devices, so I will probably leave this on for now. On other wireless networks and using mobile data, websites load absolutely fine. It just doesn't seem to like the home network.
Does anyone have any clues? I'm at a bit of a loss now, so would really appreciate if anyone else has experienced this problem.
I was wondering if anyone might be able to shed any light on this problem.
I made a post about the issue in the BT Infinity thread, but I'm not sure that's the problem here.
The scenario is, we used to have the BT Hub 5 with BT Infinity. It worked perfectly with all my devices, never had any real issues with the WiFi connectivity. As of this month, I've renegotiated the contract with BT and upgraded to the BT Smart Hub (Hub 6).
We received the new hub as of Monday. It's all set up and everything is working perfectly, except my phone (HTC One M8, Android 6.0). It was working fine at first, but as of Tuesday the phone refuses to connect to most websites whilst connected to the WiFi network. In Chrome, I get "This site cant be reached" and ERR_CONNECTION_REFUSED error displayed.
My phone is the only device on the wireless network which does this. My girlfriends iPhone works fine and our Galaxy Tab 10.1 (also an Android device) is also unaffected. It is only my phone, and it is only (most) websites that wont load. Services such as YouTube, WhatsApp, Facebook etc seem to work, albeit slowly, so the phone appears to be connected successfully, just refusing website traffic.
I've done some hunting and found a few common problems which appear very similar and I've tried the following which were listed as solutions:
- Setting the SmartHub to use separate 2.4GHz and 5.GHz wireless SSIDs. Apparently this solves a very similar Android issue.
- Enabling Dynamis DNS on the Hub and setting it to use a DNS Service ("NoIP" - I was going to use Google DNS but it wasn't on the supported list on the hub options screen.
Neither of these solutions have worked, although using a dynamic DNS seems to have improved website loading times on other devices, so I will probably leave this on for now. On other wireless networks and using mobile data, websites load absolutely fine. It just doesn't seem to like the home network.
Does anyone have any clues? I'm at a bit of a loss now, so would really appreciate if anyone else has experienced this problem.
