RRAS Stops Routing After Encountering Zero Checksum

 Last reviewed: December 12, 1997
Article ID: Q162834
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Routing and Remote Access Service Update for Windows NT Server version 4.0

SYMPTOMS

Your Routing and Remote Access Service (RRAS) Server may stop routing network between segments and you may receive some event log messages regarding checksum errors from neighbors.

CAUSE

One of your neighboring routers has sent a packet containing something other than ffff. When the checksum of a packet equals zero, which is illegal, RRAS expects to receive ffff.

STATUS

Microsoft has confirmed this to be a problem in Routing and Remote Access Update for Windows NT Server version 4.0. This problem was corrected in the Routing & Remote Access Service Hotfix Update. You can obtain this update from Microsoft's World Wide Web Site on the Internet at the following location: 

   http://www.microsoft.com/communications/routing&ras.htm
NOTE: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address: 

   http://www.microsoft.com/

Additional query words: protocol
Keywords : kbbug4.00 NTINTEROP ntnetserv NTPROTOCOL ntrouter NTSrv nttcp kb3rdparty kbinterop kbnetwork
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.