My company uses Pulse Secure VPN. Per the support team for the VPN software/appliance, there is an issue with ASUS routers working with Windows 10. I'm pasting their description of the issue below.
Do you have any thoughts around a possible fix for this issue? I prefer not having to move away from ASUS.
Thanks in advance.
Start Company Note > Some models of consumer routers do not correctly respond when Windows 10 sends a Dynamic Host Configuration Protocol (DHCP) request. These requests ask for common items such as the IP Address to use, the DNS servers to use etc. Windows 10 also asks for Web Proxy Auto Discovery (WPAD) information as well. Routers that are not configured to send WPAD information are supposed to ignore the request and not return any information for WPAD. However, some routers return a Line Feed character for the WPAD information instead of ignoring the request. This causes Internet Explorer to be unable to find the corporate proxy servers when you make a VPN connection to the company. What the user sees is that they make a VPN connection and then cannot get to any sites on the Internet (such as WebEx, SalesForce, etc.) while internal sites continue to work fine. If they drop the VPN connection then Internet sites work just fine.
Most, if not all, of the routers that have this problem are from Asus. We’ve seen at least the following models – even when running firmware as recent as 7-July-2017:
• • Asus RT-N66R
• • Asus RT-AC68U
• • Asus RS-N12
• • Asus RT-AC3200
Permanent fixes
The most supportable and permanent fix is to replace the router with a new one from a vendor whose firmware correctly handles DHCP requests from Windows 10 machines. We do not make recommendations for home / consumer routers, but most all other brands are fine including those from Netgear, Linksys, Orbi, Eero, Google WiFi and many more. There are many great choices out there that will meet most anyone’s needs from new whole house mesh systems to classic single router setups.
It is also possible that, at some point, ASUS may update their firmware. At the time of this writing, in August of 2017, it does not look like this is going to happen though. If ASUS does fix this in a newer firmware then upgrading to that firmware would also be a permanent fix.
Do you have any thoughts around a possible fix for this issue? I prefer not having to move away from ASUS.
Thanks in advance.
Start Company Note > Some models of consumer routers do not correctly respond when Windows 10 sends a Dynamic Host Configuration Protocol (DHCP) request. These requests ask for common items such as the IP Address to use, the DNS servers to use etc. Windows 10 also asks for Web Proxy Auto Discovery (WPAD) information as well. Routers that are not configured to send WPAD information are supposed to ignore the request and not return any information for WPAD. However, some routers return a Line Feed character for the WPAD information instead of ignoring the request. This causes Internet Explorer to be unable to find the corporate proxy servers when you make a VPN connection to the company. What the user sees is that they make a VPN connection and then cannot get to any sites on the Internet (such as WebEx, SalesForce, etc.) while internal sites continue to work fine. If they drop the VPN connection then Internet sites work just fine.
Most, if not all, of the routers that have this problem are from Asus. We’ve seen at least the following models – even when running firmware as recent as 7-July-2017:
• • Asus RT-N66R
• • Asus RT-AC68U
• • Asus RS-N12
• • Asus RT-AC3200
Permanent fixes
The most supportable and permanent fix is to replace the router with a new one from a vendor whose firmware correctly handles DHCP requests from Windows 10 machines. We do not make recommendations for home / consumer routers, but most all other brands are fine including those from Netgear, Linksys, Orbi, Eero, Google WiFi and many more. There are many great choices out there that will meet most anyone’s needs from new whole house mesh systems to classic single router setups.
It is also possible that, at some point, ASUS may update their firmware. At the time of this writing, in August of 2017, it does not look like this is going to happen though. If ASUS does fix this in a newer firmware then upgrading to that firmware would also be a permanent fix.