[BUG] :: PnP 2.3.0 Host not reachable if VPN is used

[stefknoe]

Reporting an Issue or Missing Feature

After updating to PnP.PowerShell 2.3.0 we get the error message "host not reachable" when trying to connect via the "Connect-PnPOnline" cmdlt. It has worked with PnP.PowerShell 2.2.0.
In our special case we use a VPN connection to connect to our company network. As long as the VPN connection is enabled "host not reachable" is thrown. If we disconnect from VPN the "Connect-PnPOnline" cmdlt works smoothly and we can connect to our tenant.

Expected behavior

Connect-PnPOnline should also work in case a VPN connection is used.

Actual behavior

If VPN connection is enabled we see two IPv4 adresses (starting with 10 is the VPN address). With this setting the "Connect-PnPOnline" cmdlt fails with "host not reachable"

PS C:\Users\****> [System.Net.Dns]::GetHostAddresses('******').IPAddressToString 10.***.***.* 192.***.***.* fe80::**** fe80::**** 2001:**** 2001:**** fd00::**** fd00::**** PS C:\Users\****> Connect-PnPOnline -Url "https://*****.sharepoint.com/sites/APITests" -Interactive Connect-PnPOnline: Host not reachable

If VPN is disabled the connection to our tenant can be established. There's only one IPv4 address used.

PS C:\Users\****> [System.Net.Dns]::GetHostAddresses('************').IPAddressToString 192.168.***.* fe80::***** 2001:**** 2001:**** fd00::**** fd00::**** PS C:\Users\****> Connect-PnPOnline -Url "https://******.sharepoint.com/sites/APITests" -Interactive PS C:\Users\****> Get-PnPTenantSite Url Template LocaleId https://*****-my.sharepoint.com/ SPSMSITEHOST#0 1033 https://*****.sharepoint.com/ SitePagePublishing#0 1033 https://******.sharepoint.com/search SRCHCEN#0 1033

Steps to reproduce behavior

Use the "Connect-PnPOnline" cmdlt in connection with VPN.

What is the version of the Cmdlet module you are running?

PnP.PowerShell 2.3.0

Which operating system/environment are you running PnP PowerShell on?

• Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[GumbyKen]

I am encountering the same issue.
When I am connected to my company network with VPN and version 2.2 of PnP.PowerShell installed, I am able to successfully connect to a SharePoint site using Connect-PnPOnline, but when version 2.3 of PnP.PowerShell is installed, Connect-PnPOnline ends with a "Host not reachable" error.
When I disconnect from VPN, Connect-PnPOnline is successful with both versions of PnP.PowerShell.

However, I also get the "Host not reachable" error from version 2.3 of PnP.PowerShell when I execute Connect-PnPOnline on a machine that is directly connected to my company network.

[valpvt]

Same here, I get the issue on PnP.PowerShell 2.3.0 and now also with 2.4.0. I don't know if it's the same context but my company uses ZScaler as proxy and I suspect it to be the cause of the "Host not reachable" issue

[valpvt]

I found an update in the code that was not present in version 2.2.0. It is located in ConnectOnline.cs, line 784.
The following code does not work behind corporate proxy var conn = System.Net.Dns.GetHostEntry(nameOrAddress);

[mrupaner]

I'm having the same issue for versions 2.3.0 and 2.4.0. At proxy level (ZScaler), we just found allowed traffic 200 http code.