Skip to main content

Show localports opening in Advfirewall using netsh




Old command to show ports opening in netsh is:
netsh firewall show portopening

For Windows OSes which uses Advance Firewall the above command may not work anymore.

PowerShell of course can get the list of ports used by Windows advance firewall with security.

The link below shows on how to use PowerShell to query advance firewall:
http://blogs.technet.com/b/jamesone/archive/2009/02/18/how-to-manage-the-windows-firewall-settings-with-powershell.aspx

If a program or application utilizes a specific port and is not open or not being set on the firewall then the particular program or application may not be accessible remotely.

If command line is preferable, netsh is able to get or list the ports used by the firewall.

netsh advfirewall firewall show rule name=all  verbose | findstr "LocalPort:"

Sample output for the command above:

LocalPort:                            3540
LocalPort:                            Any
LocalPort:                            1900
LocalPort:                            Any
LocalPort:                            RPC
LocalPort:                            445
LocalPort:                            RPC-EPMap
LocalPort:                            RPC
LocalPort:                            445
LocalPort:                            RPC-EPMap
LocalPort:                            RPC
LocalPort:                            RPC-EPMap
LocalPort:                            RPC
LocalPort:                            RPC-EPMap
LocalPort:                            5985
LocalPort:                            5985
LocalPort:                            80
LocalPort:                            80
LocalPort:                            RPC
LocalPort:                            RPC-EPMap
LocalPort:                            RPC
LocalPort:                            RPC-EPMap
LocalPort:                            1701
LocalPort:                            Any
LocalPort:                            1723

Check out link below for more Netsh commands or click the labels below:
https://support.microsoft.com/en-us/kb/947709


Labels:

Comments

Post a Comment

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Delete Directories with Wildcards using rd or rmdir

  Deleting files in command prompt using wildcards is quite straight forward. Command below will delete all text (".txt") files on the specified path.      Del D:\txtlog\*.txt Command above will delete all files with ".txt" extension in d:\txtlog directory. Easy enough to delete all matching files. Using the same method with rmdir or rd command this will not work. For example, if we have a directory on d drive that is auto-generated by an application and the filename is consistent with a pattern plus incrementing number at the end to differentiate the folder from other folders.    D:\baklogs\log1\    D:\baklogs\log2\    D:\baklogs\log3\    Etc..    D:\baklogs\log100\ The folder name has a consistent pattern that is preceded by the word “log” plus incrementing number. If the command below is executed to remove the directories in one go, an error is shown which h...
16 comments
Read more