Re: AS/400 printer sharing printing from PCs

If you have a printer shared out with the AS/400 and a user tries to access
it, it will take the windows login/password and attempt to verify against
that on the AS/400.

If there is not an username that matches and/or the password doesn't match,
you will not have access, even to a guest established printer.

When mapping QDLS to a local drive, I am assuming you either windows is
reusing that login/password pair for connecting to the printer or the AS/400
remembers the connection (sort of sounds silly, so I am assuming windows is
caching).

The issue is going to be people logging into their windows machine with a
valid AS/400 username and password.

Also, if you have a drive mapping set to reconnect at login, I don't think
it uses the same user/login you set it up with (as that would probably be a
security hole).

What you coudl do is put the net use command into a login script or startup
script on the computer to map it each time they restart their computer.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Jim Langston" <jlangston@celsinc.com>
To: <midrange-l@midrange.com>
Sent: Friday, August 16, 2002 5:59 PM
Subject: AS/400 printer sharing printing from PCs


> We have some shared AS/400 printers set up in Ops Nav.  We are trying to
print to these from Windows NT 4.0 workstations and having mixed luck.
>
> It seems that if the user has Client Access installed, there's not really
a problem.  We may have to map a drive to the AS/400 to establish the
connection, but it works.
>
> The problem is with PCs that do not have Client Access installed.  It is a
royal pain to establish a connection to the AS/400 so that the user has
access authority to the printers.  I have created a user with no rights,
can't even log in, but if a connection to the AS/400 is made with this
profile, such as mapping a drive to \\192.168.0.99\QDLS then the user has
rights to print to the AS/400 printers, which is what we want.
>
> The problem is, the AS/400 does not seem to remember the users connection,
so each time they log out and in (go home for day and come back) they can
not print to the AS/400 printers unless they remove the share and
re-establish it.
>
> NET USE X: \\192.0.0.99\QDLS USER /USER:USER
>
> This is fine, the user can browse the AS/400 at 192.168.0.99, and can
print to the printers.  They log off, X: is still mapped but they can't
browse or print.  I've tried net use x: /delete first then mapping, same
thing.  Once user is logged in fully if we net use x: /delete and remap, now
they can print.
>
> How do I get the AS/400 to allow people to print to the shared printers?
The AS/400 is not visible to the internet, and really it doesn't matter if
they don't use a user name or password at all, I would like anyone to be
able to print to these printers, but I can't find any type of permission
settings in the Ops Nav for shared printers.
>
> I've been fighting with this a long time, and we've been printing to our
NT Server printer as a work around, but the NT Server and the AS/400 fight
over this printer and sometimes print outs get half printed.
>
> Regards,
>
> Jim Langston
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>