RE: Netserver, printers and NT domains

Well, with help from Chris Bipes and Johnny Helms, and with further info
from Usenet (comp.sys.ibm.as400.misc) and IBM's NetServer site
(http://www.iseries.ibm.com/netserver/index.htm), I have actually found
a solution for this one.  If you remember, I was trying to find a way
for NT PC users to use an AS/400 line printer for simple text printing,
using NetServer, and having a few problems.  Below, for your
edification, and for the archives, is my complete solution.  Of course,
that's only "complete" until I find the next thing that breaks it.

Mind you, I _still_ can't see the AS/400 with the printers in Network
Neighborhood :-)

Thanks for the help, and I hope this will be of use to someone else.


Setting up a Windows NT PC to use an AS/400 printer using NetServer
===================================================================

You should be logged on to the NT PC with administrator rights, as you
will have to install drivers.

1. You need to have NetServer running on the relevant AS/400.

2. Set up a guest profile for NetServer.  This should have a password,
be enabled, have initial program *NONE and initial menu *SIGNOFF;
according to IBM's Informational APAR II11239: 

        This guest would be previously created by the AS/400
administrator with *SECADM special authority, and MUST not have any
special authorities.  If used for print serving, this user profile
should have a password and must be enabled for signon.  The AS/400
NetServer user will not be prompted for this password when requesting
file and print services.  The guest User Profile allows AS/400 file and
print sharing by users who otherwise would not require an AS/400 User
Profile.


(See
http://as400service.ibm.com/n_dir/NAS4APAR.NSF/c79815e083182fec862564c00
079d117/7d64bba66d1ff1ff86256619002f1bd1?OpenDocument for this APAR (and
note that the URL should be a single line without breaks; you may need
to paste it into your browser in multiple parts)).

(Note further that if the QDLS file system is to be shared, this user
must be enrolled in the system distribution directory (ADDDIRE command).
This should not affect printing, though.)

3. Using Operations Navigator (OpsNav), configure NetServer to use this
guest profile (Network|Servers|TCP/IP in the left-hand pane, select
AS/400 NetServer in the right-hand pane and take Properties; go to the
Advanced tab and press the Next Start button).  Stop and restart
NetServer.

4. Share the line printer using NetServer (Ops Nav: Basic
Operations|Printers; right-click on the required printer and select
Sharing|New Share; select User ASCII in the Spooled file type box if
only plain-text output is required).

5. Use Windows Add Printer dialogue to add it.  You can either navigate
to the AS/400 using Network Neighborhood or enter its UNC address
(\\<server-name>\<printer-name>).  If this is successful, go to step 9.
If this results in an eror message, proceed as follows.

6. Try using the fully-qualified domain name of the computer in the UNC
address: \\<server-name>.<domain>.<tld>\<printer-name>.  For example,
\\lnw.midas-kapti.com\lp6.  If this is successful, go to step 9.
Otherwise proceed as follows.

7. Attempt to find the NetServer name of the computer using the
Find|Computer dialogue.  If this is unsuccessful,try using the
fully-qualified domain name of the computer (lnw.midas-kapti.com, for
example).

If neither of these work, then I _REALLY_ can't help you.

8. If the find dialogue was successful, double-click on the computer.  A
window should open showing all the shares on the computer, including the
printers; double-click on the relevant printer.  This should give a
dialogue saying that the printer must be installed as a Windows printer.
Accept this and proceed as follows.

9. You will (probably) see a dialogue saying that a driver has to be
installed locally; accept this.

10. Select "Generic" in the "Manufacturers" box, and "Generic/Text Only"
in the "Printers" box (for the simplest configuration).

9. You may be prompted for your Windows NT CD for drivers.  If any files
cannot be found, you may have to copy them from another PC.  I had
problems finding RASDDUI.HLP and had to copy it from an NT server in the
end.

*** End ***


Cheers,

Martin

--                                                                     
Martin McCallion                 
Midas-Kapiti International
Work:  mccallim@midas-kapiti.com
Home: martin.mccallion@ukonline.co.uk

Apologies for the length of this sig, but company policy says:
This email message is intended for the named recipient only.  It may be
privileged and/or confidential.  If you are not the intended named
recipient of this email then you should not copy it or use it for any
purpose, nor disclose its contents to any other person.  You should
contact Midas-Kapiti International as shown below so that we can take
appropriate action at no cost to yourself.

Midas-Kapiti International Ltd, 1 St George's Road, Wimbledon, London,
SW19 4DR, UK
Email: Postmaster@midas-kapiti.com Tel: +44 (0)208 879 1188 Fax: +44
(0)208 947 3373
Midas-Kapiti International Ltd is registered in England and Wales under
company no. 971479 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---