No HTTP Browsing, but HTTPS Browsing works fine..

[soveryapt]

Afternoon all

 

Interesting situation here. A client of mine (on BT Infinity for Business, running a 2008R2 Server with Windows 7 clients) is having internet access issues.

 

It would seem that whilst HTTP browsing just isn't working, HTTPS browsing is (i.e. Google doesn't get you anywhere and times out where as https://www.google.co.uk get's you straight to Google).

 

Apparently, the issues reared it's head yesterday initially, but as it was later in the day, they left it to see if it was just a hiccup, but it still persisted this morning. It was me who discovered the HTTPS was working.

 

I wonder if it's a BT issue as I've suddenly not been able to reach their main router through the BT hub, let me explain that..

 

They had infinity installed about a month back now (after 3 failed attempts from BT doing a No Show for the install, but that's a different story). When it was installed, it wouldn't talk to anything other than the BT Hub through the OpenReach Infinity Modem. So the internet comes in on the OpenReach Fibre Modem, into the Hub3 and then through the use of assigned static IP addresses to devices connected to the DHCP over the Hub3, their DrayTek router picks up a public IP address. Long winded, and on my next site visit, I'll be looking to rectify this and getting the DrayTek working a bit more directly, but at the time, they were without internet access as BT didn't complete the job properly in the first instance, so it was a quick fix that worked.

 

Anywho, I just wonder if anyone knows of any reason why this should be happening or has experienced this sort of thing before and knows of anything I could try? I've checked the DNS settings on the server, and even tried overriding them at client side with direct connections to the Google Public DNS, but still the same issue.

 

Any suggestions are greatly welcomed!

 

Thanks

Andy

[twin--turbo]

have you checked your proxy settings are not disimilar for http https?

[soveryapt]

have you checked your proxy settings are not disimilar for http https?

 

They don't need proxy settings. Direct connection.

 

Anyway, problem solved after a quick phone call to BT. It would seem that BT haven't added the Broadband account into the Direct Debit agreement as my client had requested, so there was an outstanding balance on the account, at which point BT block "web access" or http traffic, but https is still permitted! I don't know if that's a fail from BT or not .. but it's resolved now ..

[soveryapt]

Further update on this..

 

BT Contacted me back with regards to payment on this so called "outstanding bill" to which my client had said they hadn't seen a bill for that so they needed one to be able to pay it .. BT's response .. "Oh yes, we can see you won't have received the bill yet as we allow you 7 working days to receive a bill and we only generated it on Monday" - Monday being when the problems started .. so they basically generated a bill and then "cut off" (read blocked HTTP Traffic) the broadband provision .. needless to say, my client is putting in a rather hefty complaint about this to them and lots of other issues they've had with this install on BT's part .. Grrr!