Test-NetConnection returns TRUE when run manually but when in a looping script, only some of the ports returns TRUE.

---

I wrote a powershell script that loops through port numbers to do a Test-NetConnection:

```
$machine = '[targetmachinename]'
$this_machine = $env:COMPUTERNAME
$port_arr = @(8331, 8332, 8333, 8334, 8335, 8310, 8311)

foreach ($port in $port_arr) {
    Test-NetConnection $machine.domain.name.com -port $port -InformationLevel Quiet
}

```

When I run the script, it always returns TRUE on the same two port numbers and returns FALSE on the other ports.

When I manually run the code for each port, they each come back as TRUE for all ports.

I have tried messing around with the port numbers by removing, adding, and moving them around but it always gives the same results with only the same two port numbers returning TRUE.

I suspected maybe the variable, array, foreach loop or something might be bad, but if that was the case, why would it work for the same two ports and not for the others even when I change up the array?  

I was thinking about putting a delay or wait in between loops but have not tested it yet. 

This script works fine when run locally from the target machine. Having this issue when running the script from another machine.

---

UPDATE:
Looking at the powershell log:

```
Command start time: 20191111121539
**********************
PS>TerminatingError(New-Object): "Exception calling ".ctor" with "2" argument(s): "No connection could be made because the target machine actively refused it [IPADDRESS]:[PORT]""

```

I noticed that the IPADDRESS does not match up with the target machine name, but instead matches up with the source machine.

---

I replaced the $machine.domain.name.com to the actual ip address of the machine and that got the script working as expected.

Why does $machine.domain.name.com resolve to the source machine? Even if I concatenate that incorrectly, wouldn't that normally become an unresolved address and error? Shouldn't all port checks have failed at that point?