Start EDGE1 and 2-EDGE1 if they are not already running, and make sure they are connected to the Internet subnet.īefore performing these tests, unplug CLIENT1 and CLIENT2 from the Internet switch and connect them to the Homenet switch. First run the tests on CLIENT1 and then run the tests on CLIENT2. In order to demonstrate IP-HTTPS connectivity, Teredo is disabled on the client computers. The second set of tests are performed when the DirectAccess client is configured to use IP-HTTPS. This is the automatic setting when the NAT device allows outbound access to UDP port 3544. The first set of tests are performed when the DirectAccess client is configured to use Teredo.
The following procedures are performed on both client computers: IP-HTTPS connections also fail if the web proxy performs outbound SSL inspection, due to the fact that the HTTPS session is terminated at the web proxy instead of the Remote Access server. If the web proxy requires authentication, the IP-HTTPS connection will fail. If Teredo access is not available, the DirectAccess client falls back to IP-HTTPS over outbound TCP port 443, which enables access through firewalls or web proxy servers over the traditional SSL port. If the NAT device enables outbound UDP port 3544 to the Remote Access server's public IP address, then Teredo is used. When a DirectAccess client is connected to the Internet from behind a NAT device or a web proxy server, the DirectAccess client uses either Teredo or IP-HTTPS to connect to the Remote Access server. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016
0 kommentar(er)
