Microsoft KB Archive/246860

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:13, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Server Configured for Open Shortest Path First Does Not Select Optimum Path

Article ID: 246860

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT 4.0 Service Pack 3
  • Microsoft Windows NT 4.0 Service Pack 4
  • Microsoft Windows NT 4.0 Service Pack 5
  • Microsoft Windows NT 4.0 Service Pack 6



This article was previously published under Q246860

SYMPTOMS

When you configure Windows NT 4.0 Server for Routing and Remote Access Service (RRAS) and Open Shortest Path First (OSPF), the server may not select the optimum path to a network resource.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Date      Time     Size      File name   Platform
   -------------------------------------------------
   11/17/99  06:46p   136,464   Ospf.dll    Intel
   11/17/99  06:45p   209,680   Ospf.dll    Alpha
                



WORKAROUND

To work around this problem, disable OSPF and add known static routes.

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0.

Keywords: kbhotfixserver kbqfe kbbug kbenv kbfix KB246860