>>>>>Hi,
>>>>>
>>>>>I need to check if a client computer has port 1433 open. This client (unlike other client PCs) has a problem connecting to the SQL Server. When I Google for "how to find if port 1433 is open" I come across messages pointing to the TELNET command. I tried telnet on my computer (in Command prompt) but get the message that this command "is not recognized ...". Is there another command that will quickly tell me (on that client PC) if port 1433 is open or not?
>>>>>
>>>>>TIA
>>>>
>>>>If you have PowerShell available, you can test networks connections.
>>>>
>>>>At the program prompt, enter powershell (or search for it), and at the powershell prompt, issue a Test-NetConnection command in the form
>>>>
>>>>

>>>>Test-NetConnection -ComputerName www.levelextreme.com -Port 80
>>>>

>>>>
>>>>(exchange the computer name and port for the ones you want to test). Something like this will be returned (but not with parts in Portuguese, I'll presume):
>>>>
>>>>

>>>>ComputerName     : www.levelextreme.com
>>>>RemoteAddress    : 64.18.88.26
>>>>RemotePort       : 80
>>>>InterfaceAlias   : Ligação de rede sem fios
>>>>SourceAddress    : 192.168.1.71
>>>>TcpTestSucceeded : True
>>>>

>>>
>>>One other thing. When I type PowerShell at the Command Prompt, the prompt changes to PS: C:\ which I think indicates that PowerShell is running. But then when I type Test-NetConnection with or without parameters I invariably get the message (in red):
>>>"The term Test-NetConnection is not recognized as the name of the cmdlet, function, script files....."
>>
>>Perhaps some info on this page could help?
>>http://www.travisgan.com/2014/03/use-powershell-to-test-port.html
>>
>>using the one-line example on that page,
>>I tried:

(New-Object System.Net.Sockets.TcpClient).Connect('www.levelextreme.com', 80)

>>I got no response -- I presume this means the connection succeeded
>>
>>then I tried:

(New-Object System.Net.Sockets.TcpClient).Connect('www.levelextreme.com', 3001)

>>the result is an error message indicating a problem connecting
>
>I believe that my problem with PowerShell (as Antonio said) is that I have Windows 7 and it works with Windows 8.1
>What is the OS of your computer?

I too am using Windows 7 -- I got the same error you were getting when trying to use the Test-NetConnection cmdlet (it is not present in version of PowerShell with Windows 7)