Problem
I am trying to configure my SCO AFPS system to be able to print to a printer that is shared out by a network connected Microsoft NT 4.0 server. I have followed the instructions to set up my server to print to a shared-client printer as detailed in the SCO AFPS Administrators Handbook for Release 3.5.1f. However, when I go to browse the network to find the remote NT 4.0 system printer shares, I get the error message:
No printers local to < .. NT4 Server name appears here..> are available to add
I have other Microsoft Windows 95 clients on the same network and these are able to see the NT printer shares. Is it possible to connect to an NT 4.0 server or am I restricted to Microsoft Windows clients?
Cause
AFPS does provide a client printing mechanism for redirecting print jobs from the UNIX print spooler to Microsoft Windows clients. However, their security model differs from that used by Microsoft NT servers. Microsoft Windows clients offer their local printers as a "share"-level resource and access to this resource is governed by a password that is specific to that resource. Servers such as NT 4.0 offer the printer as a "user"-level resource. This means that individual users must be validated by the server and then checked against the access control list (ACL) for that resource to see if the user has the right to use the resource. In AFPS Release 3.5.1f, the client printing facility assumed that the remote printer resource was available in share-level security mode.
Solution
SCO AFPS Release 3.5.1f did not allow you to connect and print to an NT server shared printer; AFPS Release 3.5.2n does. See the documentation referenced at the end of this article.
As an example only:An AFPS 3.5.2 system called "scotest" was set up as a Primary Domain Controller (PDC) in the domain AFPSDOM. An NT 4.0 system called "ntbox" also exists as its own PDC in the domain NTDOM.
NOTE: The AFPS system does not require the Microsoft Client Software package to be loaded.
+--------------+ +----------------+
| | | |
| | | |
| SCOTEST | | NTBOX |
| | | |
| (AFPSDOM) | | (NTDOM) |
| | | |
+-----|--------+ | +----+
| | | |
| lp -d fred1 file +------|---------+ |
| | |
| | +------------+
||----|------------------------------|---|| | Printer |
LAN | |
+------------+\\NTBOX\PRINTTake these steps:1. Create a printer on the NT 4.0 system and share it out to network users via the "Printers" utility within the "Control Panel". For example, create a local printer and share it out with a share name called "print".
The printer share should be seen by the AFPS system. Log on to the NT domain and check that it can be viewed.
# net logon administrator /DOMAIN:ntdom Type your password: The server \\NTBOX successfully logged you on as administrator. Your privilege level on this domain is ADMINISTRATOR. The last time you logged on was 12/05/97 06:24 PM.
# net view \\ntbox
Shared resources at \\ntboxShare name Type Used as Comment
----------------------------------------------------------
...
print Print Generic / Text Only
...
...2. Log on to the AFPS system and then log on to the AFPSDOM domain using the command:
# net logon administratorEnter the administrator password when requested.3. As root, on the system console, enter scoadmin(F):
# scoadminEnter the Printer Manager utility.Select "Printer", then "Add Remote", then "Windows".
Enter the following information:Name - UNIX printer name
Description - A description of the printer
Model - The Printer interface ("passthrough")
Windows Client - NT 4.0 server name
Share Name - NT print share name
Password - Leave Blank for NT print sharesFor example:- fred1
- Local Printer on NT Server
- passthrough
- ntbox
- print
- -NOTE: There is an option on the screen labeled "Select" that searches for the available print shares of the named Windows Client. This will give the error message:
No printers local to < .. NT4 Server name appears here..> are available to add
This can be ignored. (The print shares are there but are not being seen.) Use the <Tab> key to bypass the "Select" option to avoid the message and also to leave the password option unset.
The Printer Manager can be used normally via the OpenServer GUI Desktop interface. However, OpenServer Release 5.0.4 has a fault in the SCOadmin interface for the Remote Windows component that does not allow you to see all the options available to you on the screen. The CHARM interface of the print manager can be used for the same functions and will show all of the options.
There should now be two files created for the fred1 printer in the directory "/var/opt/K/SCO/asusrv/3.5.2n/clipr", called "fred1" and "fred1.cfg".
The UNIX printer should also be shown by the "lpstat -a" command:
# lpstat -a... testp1 accepting requests since 02:44:54 PM Fri 05 Dec 1 ...
4. As "root", enter the command:/usr/net/servers/lanman/bin/clipadm -m fred1 -ouIn this example, fred1 is the name of the UNIX printer name, NOT the NT share name.
If the command fails with the following error:
Can't open /var/opt/K/SCO/asusrv/3.5.2n/clipr/<printer name>.cfgthe printer in (c) has not been created properly.
5. The printer should now be available to local UNIX users. As an example:
# lp -d fred1 /mytextfileshould print a file to the NT Server "ntbox" local printer. The file spools through the UNIX print spooler and out. The "lpstat -o" command shows the print queue empty. However, the print request does not appear on the NT print queue (if set on "held" via the NT "Printers" interface for inspection) or on the printer. The reason is in step 2.
A network trace reveals that the AFPS server "scotest" sends a LAN Manager SMB (Server Message Block) request for a session between it and the NT server. It passes the username "ADMINISTRATOR" as part of this conversation. The UNIX "root" user automatically maps to the AFPS "ADMINISTRATOR" user but this is NOT the same as the NT servers "ADMINISTRATOR" user. The local UNIX user must log on as the "ADMINISTRATOR" user in the NT domain:
# net logon administrator /domain:ntdomResubmit the print request as before, and it will be successful. This documentation error has been reported to SCO Engineering.
Generally, administrators do not want to divulge the ADMINISTRATOR password to general users. The UNIX users could have accounts created for them on the NT server, but this would be time-consuming and awkward to administer.
If UNIX users are created via scoadmin(F), they automatically are created as AFPS users. This can be turned off, if required, by making the account distribution "local" only. If a UNIX user (for example, called "aine") who has been created as an AFPS user attempts to log on to the NT domain as follows:
$ net logon aine /domain:ntdomthe log on will fail if "AINE" does not exist as an NT user. However, the name or user id passed in the transaction will be "AINE". If a user called "sprog", who is local only, now attempts the same, the user name passed is blank.
A better solution is to use the NT User Manager for Domains to activate the Guest account and set a well-known password. Then, any UNIX user may log on to the NT domain as the "GUEST" user regardless of their UNIX name. For example, as the UNIX only or local user "zippy":
$ net logon guest <NT Server Guest password> /domain:ntdomThe server \\NTBOX successfully logged you on as guest. Your privilege level on this domain is GUEST. The last time you logged on was 12/08/97 03:22 PM.
$ lp -d fred1 file085.txt6. The printer can be shared with PC clients of the AFPS domain using the SCOadmin Printer Manager. In this example, highlight "fred1", choose "Settings", then "Control" and enable the "Share printer with Windows user" option. The name is prepended with "sh". It now appears as a re-share to local AFPS clients under the "# net share" command as:
...
SHFRED1 fred1 Spooled
...NOTES: The details listed above were tested for a shared printer local to
the NT 4.0 server. Printing to an NT printer share, which is actually
a further share from another AFPS system, was also tested but is not
possible.Printing to an NT 4.0 server LPD attached printer is also untested.
NT 4.0 workstation client printing has not been tested but should be similar to other Microsoft Windows clients.
See also
SCO AFPS 3.5.2n Administrators Handbook, Chapter 6, Page 82, "Setting up the server to print to a shared client printer".
ta100055, "I can't manage AFPS shares from the graphical desktop when using SCO OpenServer 5.0.4".
clipadm(AS)