Re: Event ID 6161 for HP 6840



Thanks for the replies.

I managed a workaround.

I found an earlier post from late August in this group regarding a security
patch related to an exposure via the print spooler service (KB896423). The
user in this case backed the patch off and his error went away.

I did not wish to start swaping patches around, so I used another trick that
has worked in the past for sharing printers that do not have network capable
drivers. I uninstalled all the HP software and reinstalled from the latest
download (not the CD) which offers the option of a local (LPTx,COMx) port. I
installed the driver and (lying through my teeth) told it that the printer
was on COM1. After that, I added a Microsoft Standard TCP/IP port for the
real printer at its fixed IP and then swapped the printer from COM1 to the IP
port. Voila! It works!

If it is so that this patch was the root, then HP needs to update their
TCP/IP port driver.

The only downside is that I blew over 6 hours on this problem...shheeesh!

HTH

Ken

"Alan Morris" wrote:

> Event 6161 will also return the Win32 error code. If it error 5 that is
> access denied. Without knowing the driver I am not sure where it is
> attempting to write data. Try \windows\system32\spool\printers or
> \windows\temp. If you get error 0 it's usually in the print processor, set
> this to winprint on the Advanced tab of printer properties to see if that
> resolves the issue.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> "KenMon" <KenMon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F2B253AD-A7AC-4863-8BE6-AAF64E968059@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I have just installed an HP DeskJet 6840. This printer includes a
> built-in
> > ethernet adapter with an HP Jet Direct print server.
> >
> > There were no problems with the install and the printer works find so long
> > as I am logged in on the admin account. Any attempt to print (Word,
> notepad,
> > test page) from a non-admin account fails with the job hung in the queue
> with
> > a status of "Print - failed" and must be purged.
> >
> > I have seen similar posts in this forum and so, for the record:
> >
> > 1) All machines are running Windows XP with all current services packs
> > and patches.
> >
> > 2) All users have Print and Manage permissions.
> >
> > 3) All machines on the network can connect to the printer via Internet
> > Explorer.
> >
> > 4) Yes, I have read the Sanders posting at:
> >
> >
> http://members.shaw.ca/bsanders/Printing%20to%20Print%20Server%20device.htm
> >
> > His advice seems odd as he recommends installing to a single machine via
> a
> > network port and then adding a share for all the other machines. Why pay
> for
> > the print server, just to use a single machine to connect and then share?
> > USB is lots cheaper.
> >
> > 5) Yes, I have contacted HP. That was a waste of time. I chatted with
> two
> > techs (the first bailed when he read the description - just closed out of
> the
> > session) and the only advice was to uninstall and reinstall. More wasted
> > time, problem still there.
> >
> > Any other ideas?
> >
> > Cheers
> >
> > Ken
> >
>
>
>
.



Relevant Pages

  • Automatically patching machine with hotfix KB824146 using mbsafu.
    ... I didn't want to spend as many hours patching machines with KB824146 exploit ... Mbsafu is an automatic remote patching tool that applies Security updates ... Download and install mbsa. ... Setup a network share with full privileges for the account you will patch ...
    (NT-Bugtraq)
  • Re: SunOs patching - How to
    ... I've been reading a lot on how to patch SunOs but I'm ... If this isn't the same on both machines, then a different release of Solaris 8 has been installed. ... Such update releases differ in two ways: A set of current patches is pre-installed, and new features might have been added in new packages. ... If you have the chance to do so, either upgrade or reinstall both machines with latest release of the Solaris version you need, or at least install a current set of patches on both. ...
    (comp.unix.solaris)
  • Re: Shame on Microsoft
    ... I'm not even going to waste my time rereading the original advisory. ... All I remember is the port numbers and patch install. ...
    (microsoft.public.security)
  • Re: OT: Microsoft sucks, part 953
    ... corp license version we use for the machine image library was WGA-proof. ... Baseline Security Analyzer onto machines running the older server ... That tool doesn't install patches, ... I often get asked to verify that a particular patch is present on the ...
    (misc.consumers)
  • 832894 phish fix -- TCP broken
    ... terminal window and tried to connect to port 25 -- connection refused. ... 10/2003 so I tried fixing the current install. ... Patch 832894 shows no information for rolling the patch back. ... Made a ghost image of my current Win2K partition. ...
    (microsoft.public.win2000.security)