There are many command-line tools for the network, such as the familiar ping,tracert,ipconfig,telnet,ftp,tftp,netstat, and the unfamiliar Nbtstat,pathping,nslookup,finger, Route,netsh ...
These commands can be divided into three categories: network detection (such as ping), network connectivity (such as Telnet), and network configuration (such as Netsh). The first two are relatively simple, and this article covers only two network configuration tools.
Netsh
Using netsh in a remote shell first solves the problem of an interactive approach. As mentioned earlier, many shells cannot redirect output output again, so command-line tools such as FTP cannot be used interactively in this environment. The solution is that generally interactive tools allow scripting (or an answer file). Like Ftp-s:filename. So is netsh: netsh-f filename.
The Netsh commands are very powerful and can be configured with IAS, DHCP, RAS, WINS, NAT servers, TCP/IP protocols, IPX protocols, routing, and more. We are not administrators, generally do not need to know so much, just use Netsh to understand the target host's network configuration information.
1,TCP/IP Configuration
Echo Interface IP >s
Echo Show config >>s
Netsh-f s
del s
From this you can understand that the host has more than one network card and IP, whether the dynamic allocation of IP (DHCP), intranet IP is how much (if any).
This command is about the same as Ipconfig/all.
Note that the following command requires the target host to start the RemoteAccess service. If it is disabled, please lift it by importing the registry first, and then
net start RemoteAccess
2,arp
Echo Interface IP >s
Echo Show Ipnet >>s
Netsh-f s
del s
This is a little more information than the ARP-A command.
3,TCP/UDP Connection
Echo Interface IP >s
Echo Show Tcpconn >>s
Echo Show Udpconn >>s
Netsh-f s
del s
This set of commands is the same as Netstat-an.
4, network card information
If the Netsh command has other commands to replace, what is the need for it to exist? There's no substitute for this one.
Echo Interface IP >s
Echo Show Interface >>s
Netsh-f s
del s
Other features of Netsh, such as the modification of IP, generally do not need to use (in case of IP after the change is not connected, "call the sky should not be called"), so all skipped.
Ipsec
The first thing to point out is that IPSec and TCP/IP filtering are different things and don't confuse them. TCP/IP filtering has very limited functionality and is far less flexible and powerful than IPSec. Let's talk about how to control IPSec at the command line.
Current 1/3 page
123 Next read the full text
