Leaked source code of windows server 2003
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><HTML DIR="LTR"><HEAD><META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252"><style type="text/css">@import url(td.css);</style><TITLE>Network Shell Component Description</TITLE></HEAD><body topmargin=0 id="bodyID" class = "dtBODY"><H1 class="dtH1"><A NAME="_network_shell_component_description"></A><SUP></SUP>Network Shell Component Description</H1>
<P>Netsh, also called NetShell or Network Shell, is a scriptable, command-line based tool that configures and monitors many Dynamic Host Configuration Protocol (DHCP), Remote Access Server (RAS) and routing network services. A Netsh context is a state in which Netsh accepts commands related to a specific set of functions. Each Netsh context contains the features for managing a related set of specific networking functions. You can change to other contexts by typing the name of a context. A routing context has many subcontexts, such as <B>autodhcp</B>, <B>dnsproxy</B>, <B>igmp</B>, <B>nat</B>, <B>ospf</B>, r<B>elay</B>, <B>rip</B>, <B>routerdiscovery</B>, <B>netbios</B>, <B>rip and sap</B>.</P>
<H1 class="dtH1">Component Configuration</H1>
<P>No configuration is required for this component.</P>
<!--Footer--><div class="footer"><br><center><font color=228B22 size="1">Built on Friday, May 11, 2001</font></center></div></BODY></HTML>
|
