- #NETEXTENDER 8.6.265 NOT SAVING PROFILES HOW TO#
- #NETEXTENDER 8.6.265 NOT SAVING PROFILES PROFESSIONAL#
- #NETEXTENDER 8.6.265 NOT SAVING PROFILES WINDOWS#
To address the shortcomings of DirectAccess, Microsoft introduced Always On VPN for Windows 10. And as organizations migrate applications, data, and even infrastructure to the cloud, a mobility solution that supports cloud integration and modern management will be required. But DirectAccess relies heavily on Active Directory and Group Policy and requires DirectAccess clients and servers to be joined to a domain. Persistent network access also allows administrators to better manage their predominantly field-based devices. It provides seamless, transparent, always-on connectivity for mobile users, enabling them to be productive anywhere. RICHARD: Well, for many years DirectAccess has been the remote access solution of choice for enterprise organizations everywhere. MITCH: Richard, please start by giving us a refresher on why Always On VPN might make sense for many organizations looking for an improved remote connectivity solution.
Richard previously provided us with a brief overview of Always On VPN in this TechGenix article but today he’s going to go into much more technical detail about setting it up using Microsoft Intune.
#NETEXTENDER 8.6.265 NOT SAVING PROFILES PROFESSIONAL#
He is a Microsoft Most Valuable Professional in the Cloud & Datacenter and Enterprise Security award categories and can be found on Twitter here. Hicks Consulting and focuses on helping organizations implement edge security, remote access, and PKI solutions on Microsoft and third-party platforms. Richard is the founder and principal consultant of Richard M.
#NETEXTENDER 8.6.265 NOT SAVING PROFILES HOW TO#
I’ve used this solution myself and I personally prefer it over using DirectAccess, and to help our readers better understand how to deploy and configure it I interviewed my colleague Richard Hicks asking him to refresh our understanding of this technology and walk us through how to deploy and configure it. With Windows 10, however, the pendulum has now swung the opposite way by introducing a new remote connectivity solution called Always On VPN. While this promise was in fact realized by this technology, implementing and managing it was often challenging for many administrators. DirectAccess, a Microsoft technology introduced in Windows Server 2008 R2 and Windows 7, promised to provide seamless connectivity between remote clients and corporate networks without the requirement of deploying and using VPN connections. Deploying and configuring such solutions, however, has often been a headache. This makes me think the problem lies with the modem's configuration.I’ve often had to employ various virtual private networking (VPN) solutions over the years as I’ve worked developing documentation, white papers, courseware, and other technical collateral for business partners and large vendors like Microsoft. Nothing has changed on the configuration side of the Sonicwall or the Windows server (DHCP and DNS), and I noticed the problem a few days after the new modem was put in. The sonicwall VPN is configured to issue an address between 192.168.1.70 & 192.168.1.80 to clients. Local devices are given address on this 192.168.1.100+ pool. The sonicwall has no DHCP or DNS services enabled, it just sends its traffic to our Windows server that runs DHCP and DNS on 192.168.1.XXX. DHCP is enabled on the modem, and that issues a local address of 10.1.10.9 to the Sonicwall. The modem connects only to the Sonicwall. More details on the network setup that may be useful: No ports are being blocked at the modem level as far as i can tell, but that traffic just isn't getting through. No settings have been changed on the firewall, but under the new modem, people can no longer connect.
The dell sonicwall SSL-VPN is configured to run on port 4433 (the default). Here's how the NetExtender app was previously used to connect:īut now when people hit connect, it pops up that error message from above, so the Server address must not actually be handing off? The server may be down or your internet settings may be down. The client PCs can no longer connect over the VPN- the NetExtender app pops up with the message: Error: The server is not reachable. We have a static IP business connection from Comcast, and a few weeks back the box crapped out. So we have a Dell Sonicwall unit that serves as our firewall and also runs the VPN functionality via the Sonicwall SSL-VPN and the accompanying client side application, Sonicwall NetExtender.