Limited Users cannot Print

[Guest]

I've researched this problem and so far none of the solutions have worked for
me.

It's the ol' "Limited users cannot print to the network printer but
Administrative users can" problem. I am using Windows XP Pro SP2 and my
printer is an HP All-in-one 2600 series printer. I have McAfee Security
Center as my firewall/anti-virus software.

Here are the tasks I have performed without success:
1. Changed properties on the printer to print directly to printer and not to
spooler.
2. Changed registry permissions for Hewlett-Packard, HP, and LEAD
Technologies to all everyone control of those registry entries, as well as
inherit from parent and replace permission entries, etc. The was the
solution provided from the HP support site.
3. Allowed Everyone full control to the windows\system32\spool\PRINTERS
folder.

Anything else I should try?

 

[Cari \(MS-MVP\)]

Were they able to print before you installed McAfee?

 

[Guest]

We never tried printing beforehand (new computer and installation) so I
uninstalled McAfee, rebooted, and tried printing again from a Limited user
account with the same problem.

 

[Cari \(MS-MVP\)]

Try Bruce Sanderson's method:
http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm

 

[Guest]

Tried that method and still no luck. I don't think I was able to supply the
correct parameter for the printer. The printer is not a network printer but
it is accessed through the network (ie, the printer is connected via cat5 to
the router). So there isn't a printer server so to speak. The printer does
have a hostname. I tried sharing the printer and then using
hostname/sharedname for the printer parameter in Bruce's cmd. But all I got
was a new printer connection that "Cannot connect".

I can print from multiple PCs to this printer through the network as long as
the user has admin rights on that machine.

Here is the error I get from the system event log:
The description for Event ID ( 6161 ) in Source ( Print ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: Test Page, <user
name>, HP Photosmart 2600 series, NT EMF 1.008, 78900, 0, 1, 2, \\<PC Name>,
67 (0x43),

 

[Guest]

Cari, I did uncover something interesting. When I reconfigure the printer
port to use the printer IP address instead of the printer hostname,
everything works just fine. So apparently the limited users cannot resolve
the IP-hostname. Any idea on how to do that? I could leave the IP address
but I believe it may change every time the printer power is cycled.

 

[Cari \(MS-MVP\)]

Hmm, no suggestions off the top of my head, I'll have to research this one.
Bruce does have a page for print servers (which of course be as yours is, a
TCP/IP card in the printer itself)... I'm not sure if there's anything on it
which will assist.

http://members.shaw.ca/bsanders/Printing to Print Server device.htm

 

[Alan Morris [MSFT]]

very odd From the message with the eventlog, error 67
is
ERROR_BAD_NET_NAME

you are on the right track but I think someone in networking might have a
better understanding of this one.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.