Incorrect Token Ring Frame Type Causes "Request Timed Out"

Last reviewed: September 9, 1996
Article ID: Q148630

The information in this article applies to:

Microsoft Windows for Workgroups version 3.11
Microsoft TCP/IP-32 for Windows for Workgroups versions 3.11, 3.11a, and 3.11b

SYMPTOMS

When you attempt to Ping an address within or beyond your local token ring subnet using TCP/IP-32 and NetWare IPX/ODI stack in Windows for Workgroups, the following error message appears:

   Request Timed Out

RESOLUTION

To correct this problem, manually change the frame type in the PROTOCOL.INI (or NET.CFG) file. The following are the required Token Ring frame type syntaxes for workstations that need PROTOCOL.INI modifications:

Network Client version 3.0 for MS-DOS and Windows:
```
      FRAME=TOKENRING
```
Windows for Workgroups 3.11:
```
      FRAME=TOKEN-RING
```
NetWare (modify NET.CFG):
FRAME=TOKEN-RING and TOKEN-RING_SNAP

KBCategory: kbnetwork
KBSubcategory: ntinterop nttcp
Additional reference words: 3.11 wfw wfwg

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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.