Shows IP addressing method and IP addresses for each adapter.<\/p>\n\n\n\n
netsh interface ip show config<\/strong> netsh interface ip show dnsservers<\/strong> netsh interface ip show ipstats<\/strong> netsh interface ip show tcpconnections<\/strong> netsh interface ip show tcpstats<\/strong> netsh interface ip show udpconnections<\/strong> netsh interface ip show udpstats<\/strong> With Netsh you change the TCP\/IP properties of network connections: static or dynamic (DHCP) addressing, client IP address, gateway IP address, subnet mask, and DNS servers.<\/p>\n\n\n\n This is useful, for example, if you want to change the addressing of multiple computers to static, or back to dynamic. Additionally, you could change the assigned static IP addresses or change the DNS servers to a different address.<\/p>\n\n\n\n In the following examples, you can replace Local Area Connection<\/i> with Wireless Network Connection<\/i> to configure the Wi-Fi adapter instead of the wired Ethernet card. If the default names aren’t used on your PC, replace it with the correct name of the desired adapter. You can see the exact names on the Network Connections window in Windows or when viewing the network details at the command-line.<\/p>\n\n\n\n Here’s an example of how to assign a network connection with a static IP:<\/p>\n\n\n\n netsh interface ip set address \"Local Area Connection\" static 192.168.0.101 255.255.255.0 192.168.0.1<\/tt><\/p>\n\n\n\n (The IP address order is: client IP, subnet mask, and gateway IP.)<\/p>\n\n\n\n If you also want to manually assign the IP addresses for DNS servers, or change them from their current IP, try this:<\/p>\n\n\n\n netsh interface ip add dns \"Local Area Connection\" 208.67.222.222<\/tt><\/p>\n\n\n\n netsh interface ip add dns \"Local Area Connection\" 208.67.220.220 index=2<\/tt><\/p>\n\n\n\n (These IP addresses are for the OpenDNS servers; feel free to use different ones. The second line configures the secondary server address.)<\/p>\n\n\n\n Here’s how to change to dynamic addressing:<\/p>\n\n\n\n netsh interface ip set address \"Local Area Connection\" dhcp<\/tt><\/p>\n\n\n\n You can also tell the adapter to receive the DNS addresses automatically:<\/p>\n\n\n\n netsh interface ip delete dnsserver \"Local Area Connection\" all<\/tt><\/p>\n\n\n\n (You could replace all<\/i> with one of the current addresses to remove only it.)<\/p>\n\n\n\n The Netsh also lets you manage the built-in Windows Firewall. Before you start adding or removing firewall entries or changing settings, you may want to check the current configuration. Here are several commands you may want to try:<\/p>\n\n\n\n netsh firewall show allowedprogram<\/strong> netsh firewall show portopening<\/strong> netsh firewall show config<\/strong> netsh firewall show currentprofile<\/strong> netsh firewall show logging<\/strong> Changing the firewall settings via the command-line is also beneficial. Maybe you installed a local server and need to add the port to Windows Firewall on all the PCs. Whatever the reason, we’ll discuss adding program- and port-based exceptions.<\/p>\n\n\n\n Here’s an example of adding a program to the exception list:<\/p>\n\n\n\n netsh firewall set allowedprogram C:MyAppMyApp.exe \"My Application\" ENABLE<\/tt><\/p>\n\n\n\n (Replace the path and filename, plus the application’s name for easier identification in firewall settings. To block the application, use DISABLE instead.)<\/p>\n\n\n\n Here’s how you might add a port to the firewall:<\/p>\n\n\n\n set portopening TCP 80 \"My Web Port\" ENABLE<\/tt><\/p>\n\n\n\n (Replace TCP with UDP as necessary and insert name for exception within the quotes. To block the port, use DISABLE instead.)<\/p>\n\n\n\n There’s one last tip to take away: from the Command Prompt you can type netsh<\/i> to enter the tool itself, so you don’t have to keep typing netsh before the command. Plus you can move to contexts, such as by entering netsh<\/i> firewall<\/i>. Then you can, for example, simply enter show config<\/i>, set allowedprogram<\/i>, or other netsh firewall commands directly, without preceding them with netsh<\/i> firewall<\/i>.<\/p>\n\n\n\n You should now be able to quickly review the networking and firewall settings at the command-line with Netsh. Plus you should be able to make simple configuration changes. Remember, there are many more commands to discover; we reviewed the basic ones.<\/p>\n\n\n\n Eric Geier<\/a>\u00a0is the Founder and President of\u00a0Sky-Nets, Ltd.<\/a>, a Wi-Fi Hotspot Network. He is also the author of many networking and computing books, including\u00a0Home Networking All-in-One Desk Reference For Dummies<\/em>\u00a0(Wiley 2008) and\u00a0100 Things You Need to Know about Microsoft(R) Windows Vista<\/em>\u00a0(Que 2007).<\/p>\n<\/div>\n\n\n\n By Eric Geier Netsh is a powerful command-line tool that is installed by default on Windows 2000, XP, Vista, and recent Server editions. It lets you view and change TCP\/IP, authentication, firewall, and other network settings. The beauty is that you can configure multiple computers by using a logon script or other means, such as a batch file. Without this you have to bring up the GUIs for the network settings on each computer and manually modify them. Instead, you can write a script and run it from one PC to push the changes to all the others, or take a <\/p>\n","protected":false},"author":2,"featured_media":5591,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"_links":{"self":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/227"}],"collection":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/comments?post=227"}],"version-history":[{"count":3,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/227\/revisions"}],"predecessor-version":[{"id":7062,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/227\/revisions\/7062"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media\/5591"}],"wp:attachment":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media?parent=227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/categories?post=227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/tags?post=227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Shows same information from above but includes\u00a0DNS<\/a>\u00a0and\u00a0WINS\u00a0details.<\/p>\n\n\n\n
Displays just the DNS server addresses.<\/p>\n\n\n\n
Displays overall IP statistics.<\/p>\n\n\n\n
Displays the TCP connections.<\/p>\n\n\n\n
Shows only TCP statistics.<\/p>\n\n\n\n
Displays the\u00a0UDP\u00a0connections.<\/p>\n\n\n\n
Shows only UDP statistics.<\/p>\n\n\n\nChanging the Network Configuration<\/h4>\n\n\n\n
Viewing the Windows Firewall Configuration<\/h4>\n\n\n\n
Displays the details of programs added to the exception\/allowed list.<\/p>\n\n\n\n
Displays the details of port added to the exception\/allowed list.<\/p>\n\n\n\n
Shows the status of the main settings.<\/p>\n\n\n\n
Shows current firewall profile.<\/p>\n\n\n\n
Displays logging file location and other details.<\/p>\n\n\n\nModifying the Windows Firewall Settings<\/h4>\n\n\n\n
We Passed the Command Line<\/h4>\n\n\n\n
![\"eric-w-geier-3160694\"](\"https:\/\/www.practicallynetworked.com\/wp-content\/uploads\/2022\/10\/eric-w-geier-3160694.webp\")
<\/figure>\n<\/div>\n\n\n\nAuthor<\/h3>\n\n\n\n