MS-DOS "For" Command Fails when Run Against an FPNW Server

Last reviewed: March 24, 1997
Article ID: Q148487

The information in this article applies to:

- Microsoft File and Print Services for NetWare version 3.51

SYMPTOMS

On your computer running Windows with the NetWare NETX.COM redirector installed, when you run the For command (which is an internal COMMAND.COM command) against a File and Print Services for NetWare (FPNW) server, the command fails after the first pass. For example, the following command only lists the first file and then quits:

   for %f in (*.*) do dir %f /b

CAUSE

The NetWare NETX.EXE redirector causes it to get the task numbers mixed up. The server closes all open file searches when the client sends an EndOfJob request after the first For-loop executes. The For command fails when the client asks for more files on a search that the client had just implicitily closed.

WORKAROUND

To resolve this problem, install the fix mentioned below.

To work around this problem, obtain the fix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in File and Print Services for NetWare version 3.51. This problem was corrected in the latest U.S. Service Pack for Windows NT Workstation or Server version 3.51. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words: prodnt
Keywords : kbbug3.51 kbnetwork ntprotocol NTSrvWkst
Version : 3.51
Platform : WinNT


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: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.