Network printer shows in AD directory and clients with server printer name and not shared name

Posted on 2011-05-03
Medium Priority
Last Modified: 2012-05-11
Hello experts,

I have a Windows 2008 R2 domain server where I have a dozen of printers configured. The clients are XP sp3 computers.

Say, I have a printer in the server named "2FL-HP3600N-IP157" and the shared name is "2_WEST_HP_COLOR"

When I go through the Add Printer wizard, I reach the "find now" part where it lists the printers in the directory. Here are my issues:

1- The network printer directory does not show the "friendly" share names I created
2- When the printer is added, it also uses the non-friendly name (2FL-HP3600N-IP157)

How can I fix the above?
Question by:xperttech

Accepted Solution

reijer earned 1600 total points
ID: 35515446
I think this is by design. the shared name is never used as the printer name on the client. if you have a printer named "Laserjet Black" and you share this printer as LJBLACK then after adding the printer the printer is named "Laserjet Black on servername". So I don't think you can change this.
LVL 43

Assisted Solution

by:Adam Brown
Adam Brown earned 400 total points
ID: 35515527
You can change it by modifying the printer properties and changing the name that shows on the General tab. The share name is used to connect to the printer, but the printer name shown in the Printer Properties screen is what is used when the printer is listed in AD and in the Printers list on client computers.

Author Closing Comment

ID: 35516678
Thanks for your answers!

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question