Paradox for DOS Over CSNW Causes Windows NT to HangLast reviewed: November 6, 1997Article ID: Q125747 |
3.50
WINDOWS
kbnetwork kb3rdparty kbprb
The information in this article applies to:
SYMPTOMSIf you start Paradox for DOS version 4.0 or 4.5 by running PDOXDOS.PIF on Windows NT version 3.5 using Client Service for NetWare (CSNW) to connect to a NetWare server and you "shell out" to a command prompt from Paradox and run a few MS-DOS commands, Windows NT stops responding (hangs).
CAUSEYou used the NUPDATE utility to configure Paradox for a Microsoft LAN Manager network. However, because you are using CSNW, you are actually using a NetWare network protocol and must configure Paradox for a Novell network.
RESOLUTIONWhen you run Paradox on a Windows NT computer using CSNW to connect to a NetWare server, configure Paradox for a Novell network. NOTE: The same does not hold true when using Microsoft Gateway Services for NetWare (GSNW). When you run Paradox on a Windows NT computer connecting to a NetWare server through a Windows NT GSNW gateway, you are actually using an Server Message Block (SMB) network protocol and must configure Paradox for a Microsoft LAN Manager network. Paradox is manufactured by Borland, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.
|
KBCategory: kbnetwork kb3rdparty kbprb
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |