Routing and Remote Access Release Notes Readme.doc File

Removing an Interface when the Router is stopped In Routing and RAS Admin, if you remove a demand-dial interface when the router is stopped, the interface is removed from the Registry, but is left behind in the router phonebook file. If you want to add the interface again and you continue to receive the error "interface already exists," you must delete the entry from the router phonebook file.

To delete an entry from the router phonebook

1. In your Systemroot\System32\Ras directory, open the Router.pbk file in a text editor.

2. Delete the entry for the demand-dial interface.

3. Save and close the file.

 * If your Windows NT router is a primary domain controller (PDC) that
   uses only the IPX protocol, then clients that dial in to that Windows
   NT router will not be validated on the router's domain. To avoid this
   problem, add the IP protocol on the router, or move the Windows NT
   router to a different computer.

 * If your Windows NT router is using File and Print Services for NetWare
   (FPNW), the router cannot connect to any FPNW shares on the router.
   This does not affect any other aspect of FPNW. Clients can still
   connect and use FPNW on the router, and the router can connect and use
   FPNW on other NetWare servers.

 * If the IPX protocol does not route with Eicon Technology WAN Services
   for Windows NT V3R4, then use the Eicon Configuration tool
   (Ecadmin.exe) supplied by Eicon. Run Ecadmin.exe, select router, select
   connections, and then select the X25 entry on the right. Select
   properties, and ensure that 00 appears in the User Data field. Repeat
   this procedure on all the systems that use Eicon WAN Services for IPX
   to route.

Do not delete the NWLink IPX/SPX Compatible Transport protocol or disable the bindings for IPX in Network in Control Panel. If you do, Routing and RAS Admin will not start.

To disable IPX routing

1. In Routing and RAS Admin, under IPX Routing, select RIP for IPX or SAP for IPX.

2. Right-click an interface, and then select Configure Interface.

3. In the Interface Configuration dialog box, clear the Enable RIP or SAP on this Interface check box.

Disable RIP or SAP Protocol There is no way to individually remove RIP for IPX or SAP for IPX routing protocols. However, you can disable them by using the Routing and RAS Admin tool in the Start/Programs/Administrative Tools (Common) folder.

To disable IPX RIP or IPX SAP on an interface

1. In Routing and RAS Admin, under IPX Routing, select RIP for IPX or SAP for IPX.

2. Right-click an interface, and then select Configure Interface.

3. In the Interface Configuration dialog box, clear the Enable RIP or SAP on this Interface check box.

To check the network number

* Under IPX Routing, click Summary, and then select the demand-dial

  interface. Check the number that is displayed in the Network Number
  column.

To do this, copy the Nwlnkipx.sys file from the directory in which you installed the Routing and Remote Access Service files on your computer to your Systemroot\System32\Drivers directory, and then restart your computer.

For more details about this problem, see the Ipxfix.txt file that is located in the \Support directory in the directory in which you installed the Routing and Remote Access Service files on your computer.

OSPF Issues General OSPF Issues

* In Routing and RAS Admin, in the global OSPF Configuration dialog box,

  do not configure the router identification number to be 0.0.0.0.

  identification numbers. The router identification number must uniquely
  identify a router throughout the OSPF autonomous system.

* Remove the interface from OSPF. * Change the IP address. * Restart your computer. * Add the interface to OSPF.

To remove the interface from OSPF

1. In Routing and RAS Admin, under IP Routing, select OSPF by Bay Networks.

2. Right-click the interface and then click Remove interface.

1. In Network in Control Panel, configure the TCP/IP Protocol.

2. In the IP Address tab, click Advanced.

3. In the Adapter box, select an adapter.

4. In IP Addresses, click Edit.

5. Type the new IP address and click OK.

6. Restart your computer.

1. In Routing and RAS Admin, under IP Routing, right-click OSPF by Bay Networks, and then click Add interface.

2. Select the interface to add and then click OK.

3. On the General tab, select each IP address in the IP Address box, and then click the Enable OSPF on this interface check box.

4. When you are finished configuring the interface, click OK.

If you configure the TCP/IP protocol by using Network in Control Panel and enable a default gateway, adding this same default gateway address on an OSPF interface might cause the unintentional advertisement.

The problem occurs when the router is defined as an autonomous system boundary router (ASBR) and you add the interface to OSPF, then enable OSPF to run on the interface. OSPF, as a result, picks all of the non-OSPF routes that are configured on the interface and advertises them to the AS. This means that the router also picks the default route (0.0.0.0) and advertises it to the other OSPF routers. If the router that is the default gateway also runs OSPF, it will learn about the default route and thus learn that the next hop for the default route is itself. This causes the default gateway to drop all the packets destined to the default route since the next hop is its own interface. This can cause major network problems.

Note: This can also occur when you add a static route to the address 0.0.0.0.

If you still need the default route locally, you can prevent OSPF from picking it up and advertising it by adding a route filter that processes all the external routes except the default route.

To add the route filter

1. In Routing and RAS Admin, right-click OSPF by Bay Networks and then click Configure OSPF.

2. On the External Routing tab, click Routes.

3. In the OSPF External Route Filters dialog box, click Process all routes except those listed.

4. Enter a route with the address 0.0.0.0 and the mask 0.0.0.0, and then click Add.

Use OSPF and RIP Together If two routers use OSPF, do not use any other routing protocols between them. This is because you do not want the routers to exchange intra-area or inter-area routes through another routing protocol that were originally learned by OSPF.

To work around this problem, configure only one router to listen to RIP. Configure the other router not to listen at all.

To do this, you can use either of these methods: * Set a peer filter to drop RIP packets that come from the remote OSPF

  router.

To set a peer filter for RIP

1. In Routing and RAS Admin, right-click RIP for IP, and then click Configure RIP.

2. On the Security tab, select the Discard all announcements from the routers listed check box.

3. Enter the address of the computer to ignore, and click Add.

1. In Routing and RAS Admin, select RIP for IP.

2. Right-click the interface, and then click Configure interface.

3. On the General tab, in the Protocol for incoming packets box, select Ignore incoming packets.

 * If the router process (Routing and Remote Access Service) is not
   responding, restart your computer.

 * If you save the configuration of a remote computer by using Save
   Configuration from the Server menu, the directory and drive into which
   you are saving must exist on both the local and the remote computers.
   For example, if you are saving a configuration to the C:\Save directory
   on the computer on which you are running Routing and RAS Admin, then
   make sure the C:\Save directory exists on the remote computer you are
   administering.

 * To monitor a Windows NT router you must use the Routing and RAS Admin
   tool in the Start/Programs/Administrative Tools (Common) folder. To
   administer a Windows NT version 4.0 or earlier RAS Server, you must use
   the Remote Access Admin tool (Rasadmin.exe).

 * Routing and Remote Access Service supports only 40-bit encryption. If
   you upgrade a RAS server that uses 128-bit encryption to Routing and
   Remote Access Service, you will have only 40-bit demand-dial and RAS
   encryption.

 * You cannot remove a routing protocol by using the Routing and RAS Admin
   tool (Mpradmin.exe). However, you can remove a routing protocol by
   using the routemon command. You can add a routing protocol by using the
   Routing and RAS Admin tool or the routemon command. To delete a routing
   protocol by using routemon, at the command prompt, type:
   ROUTEMON IP DELETE PROTOCOL PROTO= { RIP | OSPF | BOOTP }

   * The following are limits for Routing and Remote Access Service:
   *  16 LAN interfaces
   *  48 demand-dial interfaces
   *  256 RAS clients

Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Microsoft, MS-DOS, MS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.