V5R1M0 CUM screwed up our Windows printing -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: V5R1M0 CUM screwed up our Windows printing
From: Jim Langston <jlangston@xxxxxxxxxxx>
Date: Wed, 31 Oct 2001 16:55:43 -0800
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We installed the latest CUM for V5R1M0 last weekend.  Since then people
have had problems printing to AS/400 shared windows printers.  I've
determined
the problem is when the NT user profile name and password do not match
the AS/400 user profile name and/or password.  Before this was never a
problem, and we want everyone to be able to print to these printers.  We
are simply sharing them in Ops Nav and installing them on the Windows
clients as network printers.

I can't find out where to set it so anyone can print to these printers.

Is there a solution?

Regards,

Jim Langston

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.