script fails on 20225 eventID checks if VPNClient is using pulsesecure

[vyguy]

when PulseSecure establishes certificate-based VPN connection, eventid 20225 never gets logged into application log.
Thus author should probably replace 20225 get-winevent with test-netconnection -port 389 with domain controller of admin's choosing (or autoselect the environment variable's logonserver to confirm good line-of-site with a domain controller).

confirmed with pulsesecure 9.1.7 on winx64 10.0.19045.2486

[steve-prentice]

Great spot. This is written specifically for our org and for use with MS's AOVPN, but appreciate it might not worth smoothly with other VPN clients, as you've spotted. Good idea to use test-netconnection, I'd definitely suggest others modify the script and use that approach of not using AOVPN. Who knows, maybe one day I'll get around to updating this script!

[Martony78]

`function Test-DomainConnectivity {
Param (
[Parameter(Position = 0, Mandatory = $true)]
[string]$DomainName,
[Parameter(Position = 1, Mandatory = $false)]
[switch]$TestAllDCs
)
# Resolve domain controllers
$DCs = Resolve-DnsName -Type SRV "_ldap._tcp.dc._msdcs.$DomainName"

if ($DCs) {
    $Connectivity = $false
    foreach ($DC in $DCs) {
        Write-Output "Testing connection to $($DC.Target)"
        
        # Test ping
        $pingResult = Test-Connection -ComputerName $DC.Target -Count 4
                    
        # Test LDAP port connectivity
        $netResult = Test-NetConnection -ComputerName $DC.Target -Port 389

        if ($pingResult.StatusCode -eq 0 -and $netResult.TcpTestSucceeded) {
            Write-Output "Connection to $($DC.Target) is successful."
            $Connectivity = $true
            if (-not $TestAllDCs) {
                return $true
            }

        }
        else {
            Write-Output "Connection to $($DC.Target) failed."
        }
    }

    return $Connectivity
}
else {
    Write-Output "No domain controllers found for $DomainName."
    return $false
}

}
`