Hi ianfretwell,
Yes, that's the correct IP address, and nowhere in the configuration I've looked at myself and been suggested to look at have any route blocking/filtering/redirects.

I could try full factory reset as it's effectively only in test at the moment, so I will try that next - though I think I may have tried that before opening my post here.

Thanks

Hi ianfretwell,
OK, done that, it picked up the WAN and gave internet access straight away. Tried the site as before and blocked.

Can access Amazon, Google etc. - all fine

Checked the firewall, disabled it along with disabling Allow pass inbound large packets and Enable Strict security firewall (which should be disabled if firewall disabled - but just in case).

Checked Routing static routes (empty).
Checked NAT Port Redirection - all disabled and empty

And just to confirm on latest FW - 4.4.5.8 BT

So still flummoxed. Considering rolling back FW to previous version.

4.4.5.8 here too so I can't see rolling back making any difference.

If you do a tracert to that IP address does it just get as far as the router and then start timing out responses ?

I get: -

router   192.168.1.1
91.193.8.3
91.193.8.170
* * *
* * *
* * *
* * *
ukpro5.fcomet.com  80.85.87.183

​​​​​​​

Hmmm - interesting , tracert takes it beyond router to Virgin (ISP) but times out after Virgin at akamiatechnologies which is gateway to domain host.

But if I run tracert on a PC connected to working TP Link router using same WAN connection, it resolves all the way to domain host beyond akamai.

Belt & braces I've just tried the following:-

2866Lac 4.4.5.8 (on Zzoomm)
2866ax 4.4.5.8 (on BTNet)
2927Lac 4.4.5.8 (on BTNet)
2762ac 3.9.9.1 (on TalkTalk)

All work just fine to slingpath.com

Well I don't know - with more knowledge comes more confusion. Plainly Draytek seems to be working, something external doesn't like it.