What does it mean when Test-NetConnection gives both "Status: TimeOut" and "TcpTestSucceeded : True"?

Hemmerling, Ken 21 Reputation points
2020-07-14T16:05:52.133+00:00

I am so friggin confused. I'm trying to use Azure file storage on a windows server and Test-NetConnection gives both "Status: TimeOut" and "TcpTestSucceeded : True". Can anyone explain what this means?

PS C:\Users\a-khemmerling> Test-NetConnection -ComputerName ([System.Uri]::new($AzStorageAcct.Context.FileEndPoint).Host) -Port 445
WARNING: Ping to o365sqlfsw.file.core.windows.net failed -- Status: TimedOut


ComputerName           : o365******.file.core.windows.net
RemoteAddress          : 52.239.190.8
RemotePort             : 445
InterfaceAlias         : Ethernet0
SourceAddress          : 192.168.84.94
PingSucceeded          : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : True
Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,163 questions
0 comments No comments
{count} votes

7 additional answers

Sort by: Most helpful
  1. Leon Laude 85,651 Reputation points
    2020-07-14T16:22:18.367+00:00

    Hi,

    The Test-NetConnection PowerShell cmdlet uses Write-Progress for status messages and Write-Warning to report failure states (Ping or TCP connect failed) to the console. There is no way to define a timeout value for any of the tests.

    The cmdlet always does a ping test and name resolution, even if you are using it to test a TCP port or to perform a traceroute (you get both results, with ping and name resolution seemingly being performed first which can slow the performance of the cmdlet overall).

    Best regards,
    Leon

    1 person found this answer helpful.
    0 comments No comments

  2. Dave Patrick 426.1K Reputation points MVP
    2020-07-14T16:21:28.687+00:00

    The PingSucceeded False just tells that ICMP echo is being blocked somewhere.

    0 comments No comments

  3. Hemmerling, Ken 21 Reputation points
    2020-07-14T16:57:39.71+00:00

    If I understand your answers correctly then the result of my Test-NetConnection is that it is NOT working.

    I've checked with my firewall admin and he tells me there's a rule to allow all communication between my server and the internet on port 445.

    So... any advice on what the next steps are? Is this something I should open a ticket with Microsoft support on?

    Ken

    0 comments No comments

  4. Dave Patrick 426.1K Reputation points MVP
    2020-07-14T17:50:01.277+00:00

    From what you posted it looks like port 445 succeeded, it was the ICMP ping that failed.

    0 comments No comments