This site is now a static archive. No new posts or comments can be made.
Scenario After updating the internal CA root certificate, AlwaysOn VPN stops working with an error (at the user end) of " A Certificate could not be found that can be used with this Extensible Authentication Protocol " In this case, we were using an Enterprise integrated CA and renewed the root using the same signing…
Continue readingAs a follow up to my article a few days ago on Always on VPN vs DA - http://www.hayesjupe.com/always-on-vpn-and-da-a-comparison/ - an employee of mine was having a test with some spare time today and came up with the following findings. Configured and tested the VPN server using L2TP/IPSec + PSK, User/Pass using MS-CHAP-V2 Attempted to…
Continue readingDate: 04/09/2018 For a while now, Microsoft salespeople have been telling customers that Direct Access is old technology and that Windows 10 always on VPN is the way to go. There are a number of points which are widely acknowledged when it comes to DA vs Always on VPN, most of which can be found…
Continue reading<rant mode: on> Direct Access (or DA) is awesome. Much like TMG before it, it fits into a segment of the market that nothing else covers in quite the same way. DA is fully supported in 2016, but has had no new features added. I read somewhere that while it is still supported, it is…
Continue readingAt a client - 2012 R2 IPHTTPS DA and win 10 1511..... Client wants force tunnelling so all traffic is routed back through the internal network and the web filter etc.... Issue is, www.msftncsi.com cannot be contacted as soon as force tunnelling is enabled. Tried a couple of basic things, such as adding msftncsi.com into…
Continue reading