Wednesday, February 4, 2009

Vista Printer Access Denied

Ran into a weird problem today. We have a W2K print server with a lot of printers on it. I have a few of them mapped to my Vista workstation, no problems. We recently added a Windows 2008 Server that needed some of those printers mapped. Added an Oki printer, no problem, added an HPLJ, no problem. Tried to add a Zebra printer, "Access Denied"\

Hunh? Same security settings, everything.

Well, maybe it's a bad driver? Went back to Zebra's website, dl'd the driver, reinstalled the printer on the print server, tried to map the printer on 2008; "Access Denied".

Went to my Vista PC. I already have several printers from the server installed. Try to install the Zebra: "Access Denied". Nothing in the event logs, NOTHING.

Mapped the printer via IP and installed the driver, not a problem. Tried to map to the server; "Access Denied".

Finally found this info; compiled form a couple of different sources. It works.

On Vista PC go to "Control Panel" - "Printers" - "Add printer".
Believe or not, click "Add a local printer" (I know you want to add a network printer but that way doesn't work, we already know this).
Click "Create a new port" - "Local Port" - "Next"
In the next box you have to enter a port name like this: \\PC name\Printer name
where "PC name" is the network name of the XP PC or Network Share where you have the printer and "Printer name" is the network name of that printer. Be careful with this names.
Choose the manufacturer and printer model of the printer you are adding or browse to add a driver.
Now the printer will be added and you can print a test page.

Note: Creating a local port instructs the client computer to use its own printer driver to render as a RAW print job and send it directly to the port (which in this case goes to the print server). This obviates the need for the print server to provide feedback to the client, which can work around some authentication issues, as well as issues with mismatched driver versions on the print server and the client computer.

No comments:

Post a Comment