XP network printer names

[JayE]

Hi,

Just bought 2 new PCs for my company with XP for me and one of the Directors, a few more to follow very soon.

I cannot understand how the network printer names are shown in the print dialog boxes, ie. \\servername\printername (as installed on the server). How do I get it to show the printer name in user-friendly language, ie Kyocera FS-7000 via network or Smart Label Printer instead of \\1008\slp on 1008?

It already proving EXTREMELY HARD to pick out the printer name I want to use each time I want to print an e-mail/document, etc. But perhaps I'll get used to us. However, as IT Support Co-ordinator, though, I am concerned for my colleagues who will find this very hard to deal with, and will probably keep pressing the wrong printer, which could have disastrous results if the document is sensitive/confidential!!

It's going to cause me a lot of hassle and a lot of time because I have an Access database where about 250 reports are set to print to a specific printer and it doesn't recognise the new printer name, it's still looking for the printer name I set up on Windows 98, so each time it stops and pauses and asks which printer to use. The only way to prevent this happening each time is to go into Setup on each report and change the name/location. The reports run from macros, so I can't use them until I change each printer setup.

Our IT Support company's person said that the network name installed on the server HAS to be used, it cannot be changed. I find this baffling, and am very annoyed that I can't choose printer names for MY OWN PC.

Can this behaviour be changed in some way? Or is there a workaround? - or a way to quickly change all of my Access reports?

I keenly await your reply, as I need to decide on the next few PCs I am ordering shortly.

Regards,
Jay/UK

 

[uctxs]

If your running a Network which is sounds like you are. Try setting up one of your Pc's as a main Print server which is just simply attaching the printer of choice to that machine then set it as default and on the security tab add the user or users you want to have access to the printer if you want all employees to be able to print just add everyone to the security setting and add the priv.Then once that is done Map your printer to the other pc's and also set it as there default printer. Then all they have to do is hit print and off they go. Now you will be able to use multiple printers as well but they will have to remember if they want to use a diff printer then they will have to choose it from the dropdown list if not it will go to the default printer. Well hope this helps.

 

[Marcs41]

I really don't see the problem, or am I missing something?
If you setup / connect to a printer, that printer driver is on you own PC, You can Rename that printer to anything you want. Mind you, not the share name, just rightclick it and select rename. The solution is out there.

 

[JayE]

Hi,

Printer is connected to SBS 4.5 network.

Just looked at my colleague's PC, also XP/Office 2000 Pro and noticed that when she prints from Outlook, she gets a "user friendly" dialogue box which shows the proper names of the printers, whereas I get the \\servername\printername for each printer.

Since my IT man said that using UNC names for printers is "par for the course" with XP, I am amazed at the difference between our 2 PCs.

Can you give me any clue at to the differences between the 2 PCs setup, as they were both set up for XP/printers at exactly the same time by the same IT man?

I do hope you can assist.

Regards,
Jay/UK

 

[Marcs41]

I am running 2 2000 Servers, each sharing a printer, all the workstations are 2000 or XP (also 1 sharing a printer), they can all print everywhere and I name my printers anything I like.

So, again, on YOUR PC, open the printers in control panel, rightclick the printer, select properties, the first thing that pops up is the General page with the printername next to the printer icon.
There, you can type anything you want.
Unless ... the administrator has taken away thos privileges on your PC, but that is another issue.

The solution is out there.