| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
TCP/IP Configuration Utilities (ipconfig, winipcfg and ifconfig) (Page 3 of 5) The ipconfig Utility Windows takes a somewhat different approach to network configuration than UNIX. As we have seen, the UNIX ifconfig program can be used both to view and modify a wide range of configuration parameters. In Windows, however, most setup and parameter modification is done using the Windows Control Panel. Windows does include a utility that is somewhat similar to UNIXs ifconfig, but it has far less functionality, and is used mainly to inspect the existing configuration, not change it. It also allows an administrator to easily perform a few simple functions on a host. On most newer versions of Windows, the equivalent of ifconfig is a command-line utility called ipconfig. Like ifconfig, the Windows utility is controlled using options that are supplied to the program. However, because it is so much simpler than ifconfig, there are only a few different options that can be used. These are summarized in Table 308.
As mentioned earlier, ipconfig is most often used to just examine the existing configuration. When simplified information is needed it is called with no options; an example of the output from this use of the command is shown in Table 309. For detailed information on interfaces, the /all option is used; an example is in Table 310 (slightly modified so it is easier to read).
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||