Microsoft KB Archive/254252

= Some Configurations Are Not Written Correctly to the NetShell (NetSh) Dump File =

Article ID: 254252

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server

-



This article was previously published under Q254252



SUMMARY
This article describes how to manually edit the dump file when you use the NetShell utility for Windows 2000-based remote access routers that are running the Routing and Remote Access service.



MORE INFORMATION
Some configurations are not written to the dump file correctly when you use the NetShell (NetSh) utility to configure interfaces, routing protocols, filters, routes, and remote access behavior for Windows 2000-based remote access routers that are running the Routing and Remote Access service.

Six issues are discussed in this article. They are:


 * 1) Internet Protocol (IP) in IP tunnels are not stored correctly in a NetSh dump file.
 * 2) Internet Packet Exchange (IPX) set filter, static route, and static service commands do not dump correctly and are not executed when Frame types are present.
 * 3) IPX add static service commands dump with tags, but are executed only if the tags are removed.
 * 4) IPX network basic input/output system (NetBIOS) names do not get added to a NetSh dump.
 * 5) Remote Access Service (RAS) IPX set pool command values are dumped as hex values. These values must be in decimal to execute.
 * 6) For remote execution of NetSh dump, connectivity outside of RRAS is required.

The following information restates each of these six issues and includes instructions and examples for dealing with it.

If these issues occur, manually edit the dump file as described below:

 Internet Protocol (IP) in IP Tunnels are not stored correctly in a NetSh dump file:

If an IP-only tunnel is configured in the router and subsequently dumped, using NetSh, it is incorrectly stored in the dump file, under the interface context. This causes the tunnel not to be configured at all when the dump file is executed to configure a server.

To modify the dump file so that the tunnel will be properly configured when the dump is executed, make the following changes:   Locate the Interface configuration section of the dump file. In this section, find and delete the line with this syntax: add interface name = "" type = tunnel srcaddr =  destaddr =  ttl =    Locate the Routing configuration section, IP configuration section, and add the following line to create the tunnel: add ipiptunnel [name=] [localaddr=] [remaddr=] [ttl=] </li></ul> </li>  Internet Packet Exchange (IPX) set filter, static route, and static service commands do not dump correctly and are not executed when Frame types are present:

When these IPX commands are dumped, they lack a closing bracket ']'. Edit the dump and add the bracket to solve this problem.

Example:

Incorrect dump: #-- set filter "Private Net [802.2" Output Deny set filter "Private Net [802.2" Input Deny set filter "Private Net [802.3" Output Deny set filter "Private Net [802.3" Input Deny set filter "Private Net [EthII" Output Deny set filter "Private Net [EthII" Input Deny set filter "Private Net [SNAP" Output Deny set filter "Private Net [SNAP" Input Deny set filter "Internal" Output Deny set filter "Internal" Input Deny
 * 1) IPX Traffic Filter configuration
 * 1) IPX Static Route configuration
 * 1) IPX Static Route configuration

add staticroute "Private Net [802.2" 0x10000000 nexthopmacaddress = 0x100000000000 ticks = 001 hops = 001


 * 1) IPX Static Service configuration
 * 1) IPX Static Service configuration

add staticservice "Private Net [802.2" 0001 1 network = 0x10000000 node = 0x100000000000 socket = 0x1000 hops = 1 Corrected Dump: #-- set filter "Private Net [802.2]" Output Deny set filter "Private Net [802.2]" Input Deny set filter "Private Net [802.3]" Output Deny set filter "Private Net [802.3]" Input Deny set filter "Private Net [EthII]" Output Deny set filter "Private Net [EthII]" Input Deny set filter "Private Net [SNAP]" Output Deny set filter "Private Net [SNAP]" Input Deny set filter "Internal" Output Deny set filter "Internal" Input Deny
 * 1) IPX Traffic Filter configuration
 * 1) IPX Static Route configuration
 * 1) IPX Static Route configuration

add staticroute "Private Net [802.2]" 0x10000000 nexthopmacaddress = 0x100000000000 ticks = 001 hops = 001


 * 1) IPX Static Service configuration
 * 1) IPX Static Service configuration

add staticservice "Private Net [802.2]" 0001 1 network = 0x10000000 node = 0x100000000000 socket = 0x1000 hops = 1 </li>  IPX add static service commands dump with tags, but execute only if the tags are removed:

To enable add static service commands to be executed from a NetSh dump file, the tags added during the dump must be removed.

Example:

Static Service Configuration as dumped: #--
 * 1) IPX Static Service configuration

add staticservice "Local Area Connection" 0001 1 network = 0x10000000 node = 0x100000000000 socket = 0x1000 hops = 1 Corrected Configuration: #--
 * 1) IPX Static Service configuration

add staticservice "Local Area Connection" 0001 1 0x10000000 0x100000000000 0x1000 1 </li> IPX network basic input/output system (NetBIOS) names are not added to a NetSh dump:

The IPX NETBIOS configuration section of a dump file does not contain commands for adding NetBIOS names. These must be added manually. The format for these commands in this section of the dumpfile is:

ADD NBNAME ifname nbname [nbtype]

</li> Remote Access Service (RAS) IPX set pool command values are dumped as hex values. These values must be in decimal to execute:

In a NetSh dump file the set pool commands to configure a RAS server's IPX address pool have the values dumped as hex. These must be modified to decimal values in order for the dump file to execute correctly.

Example:

Dumped Command:

set pool firstnet = 2 size = d

Correct Command:

set pool firstnet = 2 size = 13

</li> For remote execution of NetSh dump, connectivity outside of RRAS is required:

In order to reliably execute a NetSh dump remotely to configure a Routing and Remote Access Service (RRAS) server, the connection to that server must be available regardless of the state of the RRAS service. In other words, the system executing the dump against the server must maintain connectivity with the Routing or Remote Access service not running.

One reason this is necessary is that when IP Routing is being configured, reset commands are issued to set the IP router state to a 'clean' state. This causes loss of the connectivity provided through the IP router.

If connectivity to the system being configured is lost during execution of the dump, and 'routing ipx' commands are being executed, an access violation can occur in IPXMONTR.DLL. You must reestablish connectivity and then start the configuration over again.</li></ol>

Additional query words: win2krelnotes

Keywords: kbinfo KB254252

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.