So I'm just bouncing this again, because I'm sure there's a Networking Guru hiding out there who can figure out where this fault lies, how to fix it, and — most importantly — how to get it in front of the right BT team.
In simple terms, I'm paying two companies for two parts of one service: Ecohosting to host my email, and BT to provide the Internet connection by which I access it. Obviously those two networks have to interact for the service to work, and I'd like to think both sides would want to help establish where that interaction is failing.
Ecohosting have certainly tried. They've checked their firewall, checked the relevant IPs, whitelisted both of my BT public IPs, carried out further testing, and escalated the issue to their infrastructure team. Though they're taking their time..m
BT, so far, have essentially told me that there is no fault because their standard broadband tests show that my broadband is working. That is true — but it doesn't explain why this particular destination is unreachable.
The evidence is now quite specific:
• 91.238.161.174 is the server hosting my email and cPanel.
• It works perfectly from my phone over EE 4G.
• From the same Mac over BT, connections to .174 are immediately refused.
• From that same BT connection, the adjacent addresses .173 and .175 connect successfully.
• Changing my BT public IP from 81.152.17.174 to 217.42.97.128 made no difference.
• DNS and BT Web Protect have both been ruled out.
So this isn't really a question of whether "my broadband works". It does.
The question is: where, between the BT network and 91.238.161.174, is the connection being refused?
Ecohosting are investigating from their side. BT Consumer Resolutions have had my complaint since last week but I have yet to receive a response.
Is there anyone here with the network expertise — or knowledge of how to reach the appropriate BT network team — who can look at this as a destination-specific connectivity problem rather than simply a broadband fault?
HELP!
