help testing connectivity to a given site from a BT line

[casaschi]

I'm having issues reaching certain web destinations from my BT home broadband connection.

Those destinations are managed by the godaddy subdomain forwarding offer, so it might be there's an issue reaching the godaddy forwarding server from my BT line. Other connections work, like my mobile phone (not BT); even running a VPN over the BT line works.

May I ask some helpful member of this community to check if they can reach FROM THEIR BT LINE the following website: http://forward2google.casaschi.net  This should just redirect to the google homepage. From my home BT line I get an error message such as "server took too long to respond" or similar depending on the browser (Chrome, Edge, Firefox).

Thanks for your help.

[licquorice]

Works for me.

[licquorice]

Are you attempting to connect to the site by port forwarding on your home hub? Not all home hubs support NAT loopback so you won't be able to connect to your public IP address from within your LAN.

[casaschi]

Thanks for checking.

I'm not doing anything unusual on the client side, just entering the URL in the browser. Nothing to do with port forwarding, the forwarding is done by a server outside of the BT network. The server is a godaddy server configured to forward the request to google.com.

The traceroute does not show me any obvious problem either.

tracert forward2google.casaschi.net

Tracing route to forward2google.casaschi.net [184.168.131.241]
over a maximum of 30 hops:

1 22 ms 11 ms 2 ms bthub [xxx.xxx.xxx.xxx]
2 19 ms 5 ms 6 ms xxx.xxx.xxx.xxx
3 * * * Request timed out.
4 15 ms 6 ms 7 ms xxx.xxx.xxx.xxx
5 28 ms 12 ms 7 ms core1-hu0-2-0-1.southbank.ukcore.bt.net [195.99.127.14]
6 23 ms 7 ms 7 ms peer8-et-0-0-2.telehouse.ukcore.bt.net [62.172.103.172]
7 15 ms 12 ms 6 ms 166-49-214-168.gia.bt.net [166.49.214.168]
8 * * * Request timed out.
9 * * * Request timed out.
10 208 ms 125 ms 127 ms ae6.ibrma1205-02.phx3.bb.godaddy.com [4.16.137.146]
11 * * * Request timed out.
12 142 ms 125 ms 126 ms 148.72.32.5
13 140 ms 125 ms 129 ms ip-184-168-0-113.ip.secureserver.net [184.168.0.113]
14 150 ms 125 ms 126 ms ip-184-168-1-134.ip.secureserver.net [184.168.1.134]
15 127 ms 125 ms 126 ms ip-184-168-131-241.ip.secureserver.net [184.168.131.241]
16 125 ms 139 ms 129 ms ip-184-168-131-241.ip.secureserver.net [184.168.131.241]

[casaschi · Accepted solution]

Sorted now, not sure what happened, the issue remained for a number of days then cleared.