Until yesterday everything was working fine - I use Cisco Anyconnect client to connect to my work network when working at home, but this stopped connecting yesterday.
Talking with my work IT folks revealed no issues at their end, and one of them tried remotely logging into his home PC and connecting the vpn with the same result - no connection. He is using a BT home hub (not sure which one) and I'm using a Netgear D6400 but we both now have the same problem.
I tried connecting to the vpn site through my web browser with the same result - can't be reached, site took to long to respond.
Talking to BT support was a joke - the chat line wasn't worth the time and the techexpert phone call stopped at the mention of the D6400, despite the information about my IT guy and his home hub.
Given the circumstances, my work IT folks believe that BT have stopped carrying vpn traffic - is anyone else experiencing an issue?
Can anyone from BT comment and help resolve this problem?
Here's hoping for some progress...
Solved! Go to Solution.
Welcome to this user forum.
This may point to the issue.
The other suggestion would be to change your DNS server adresses on your PC to Google Public DNS 220.127.116.11 and 18.104.22.168 instead of BTs DNS servers.
BT do not block VPNs
If you are using a third party router, then you can change the DNS servers on that. You cannot change them on the BT home hub.
Hi Keith - thanks for your reply.
I've just tried:
- changing the DNS server addresses on both my laptop and D6400 to explicitly use 22.214.171.124 & 126.96.36.199
- rebooting both router & laptop
no change - still no connection to the vpn site via Chrome.
I did try to go to that BT Web Address Help opt-out link at the bottom of the link you posted, but that also won't connect - takes too long to respond.
I'm not having any issues with any other sites.
Have you tried a traceroute to your VPN address?
Use tracert command at Windows command prompt.
Hi Keith - a couple of runs shows the same result:
Tracing route to vpn.domino-printing.com [188.8.131.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 8 ms 7 ms 8 ms 184.108.40.206
5 8 ms 8 ms 7 ms core4-hu0-7-0-8.faraday.ukcore.bt.net [220.127.116.11]
6 8 ms 8 ms 8 ms peer6-hu0-12-0-0.telehouse.ukcore.bt.net [18.104.22.168]
7 7 ms 7 ms 7 ms t2c3-et-3-1-0-0.uk-lon1.eu.bt.net [22.214.171.124]
8 10 ms 10 ms 9 ms i-0-4-0-7-peer.ulco-core02.pr.telstraglobal.net [126.96.36.199]
9 9 ms 10 ms 10 ms i-91.ulco-core02.telstraglobal.net [188.8.131.52]
10 9 ms 9 ms 9 ms i-0-0-2-1.ulhc01.telstraglobal.net [184.108.40.206]
11 14 ms 14 ms 14 ms unknown.telstraglobal.net [220.127.116.11]
12 * * * Request timed out.
13 * * * Request timed out.
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.
Does that look as though it's getting 'stuck' inside 217.151?
yes, that's what I also thought
I've forwarded this information onto my work IT folks to see what they can do
I'm sorry, but as far as I'm concerned this problem is not yet resolved - I still cannot get the vpn to connect, and until I can this enquiry for me is not complete.
So far, we have some information that indicates the problem might be somewhere else, but this cannot be said to be resolved because the initial problem has not yet been fixed.