[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::ms-exchange

Title:Microsoft Exchange Server
Notice:
Moderator:FLASK2::SYSTEM
Created:Fri Feb 17 1995
Last Modified:Thu Jun 05 1997
Last Successful Update:Thu Jun 05 1997
Number of topics:1099
Total number of notes:5174

421.0. "Printing problem" by CRONIC::iss030.hlo.dec.com::dunlop (Ten Forward - Our atmosphere can't be replicated.) Mon Jul 01 1996 21:49

T.RTitleUserPersonal
Name
DateLines
421.1Any Resolution???ALFSS2::64746::lamberson_mThu Dec 05 1996 15:574
421.2Possible privilege or protection problem?MTADMS::SCHEIBLESometimes U'r the Windshield, Sometimes U'r the BugTue Feb 11 1997 13:0511
We experienced the same problem printing from NT workstations to VAXcluster
queues.  The problem was that the LM password (pathworks) on the VAX did not
match the NT password (account name was the same).  Therefore, the user did not
have the privilege to use the printer resource on the VAX.  Once the password
situation was corrected, printing was fine.  Although this is not exactly the
same environment you are in, it seems to be a privilege problem.  Either an
expired password (user hasn't logged out recently), or locked account?  Or user
doesn't have the correct privileges to print to the printer.  Hope this helps
anyone with similar issues.

Mark
421.3We've seen this problem too...TLE::PERRYDave Perry ZKO2-3/L32 DTN:381-2396Wed Apr 09 1997 23:2612
We're seeing the same problem here at ZKO.  It's the same symptoms: NT 
workstation has problems printing to a printer from within Exchnage (with 
the error message shown in .0) yet has no problems printing to the same 
printer from other apps.  "Exiting and logging off" of Exchange, then getting
back into Exchange seems to clear the problem, but I'm not sure how long
it stays "fixed".  It's definately not a privilege problem because other
apps can print just fine.  For now, I've just told the person who has the
problem to "Exit and Log off" then get back into Exchange whenever the
problem pops up.  I've got too many other things to worry about...

-Dave