PING Causes Reboot If Executed Outside Windows for Workgroups

 Last reviewed: January 26, 1995
Article ID: Q123077
The information in this article applies to:
  • Microsoft Windows for Workgroups version 3.11

SYMPTOMS

After you install Microsoft 32-bit TCP/IP and issue a PING.EXE, ARP.EXE, NBTSTAT.EXE, NETSTAT.EXE, or ROUTE.EXE command from a real mode MS-DOS command prompt, one of the following problems occurs:

  • The machine reboots

    -or-

  • The machine stops responding (locks up)

    -or-

  • The system generates an EMM exception error

CAUSE

Because Microsoft TCP/IP-32 is an NDIS3 protocol, the utilities must be run from within Windows for Workgroups while the protocol is loaded.

RESOLUTION

To correctly use the TCP/IP utilities, choose the MS-DOS Prompt icon to open an MS-DOS window within Windows for Workgroups, and then run the utility using its proper syntax. For example, to run the PING command, type the following: 

   c:\windows>ping 127.0.0.1

KBCategory: kbnetwork kbinterop kbusage kbtshoot
KBSubcategory: wfwg wfw
Additional reference words: 3.11 tcpip tshoot execute

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: January 26, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.