Windows NT Service Can't Connect to Network Printer on 3.51   [winnt]
ID: Q139649    CREATED: 14-NOV-1995   MODIFIED: 15-NOV-1995
3.51
WINDOWS
PUBLIC | kbprint kbnetwork kbbug3.51

----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.51
 - Microsoft Windows NT Server version 3.51
----------------------------------------------------------------------

SYMPTOMS
========

If a Windows NT service attempts to connect to a network printer resource
while running on Windows NT 3.51, the connection attempt fails.

If the service attempts to call CreateDC on the "winspool" driver, the call
fails with rc=126 (specified module could not be found). The actual error
observed by the user will vary depending on how the service handles this
error condition.

This problem occurs with any Windows NT service which attempts to connect
to a network print resource, including the NetSoft NS/Print Server for
Windows NT.

CAUSE
=====

If the printer is remote, the spooler passes an invalid parameter causing
the service's CreateDC call to fail.

RESOLUTION
==========

The service can still connect to any local printer resources. So, to
workaround the problem, the administrator must create local printers using
the Print Manager.

However, a Windows NT 3.51 fix is also available which allows a service to
dynamically connect to a network print resource, as described below.

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version 3.51.
A fix to this problem is in development, but has not been regression-tested
and may be destabilizing in production environments. Microsoft does not
recommend implementing this fix at this time. Contact Microsoft Product
Support Services for more information on the availability of this fix.

KBCategory: kbprint kbnetwork kbbug3.51
KBSubcategory: ntprint
Additional reference words: 3.51 prodnt prodsna