Network printer name

  • Thread starter Thread starter Microemission24
  • Start date Start date
M

Microemission24

I have a win2003sbs server connected to several printers, all shared
on the network.

Two client machines can see these with no problems, and prints to them
fine, even form the dos program they rely so heavily on.

One client has problems though, even if he can connect to the printers
from windows XP all right, he cannot use them in the dos program,
since they are named incorrectly in windows printer setup

The problem is that the printer gets named by a combination of its
name on the ser ver, and the server name.
And the server name is written in uppercase letters.
I.e. the printer is called HP5_letters and the server is called
Server1 then the printer would be named "HP5_letters on SERVER1"
Where it's named "HP5_letters on Server1" on the other client
machines, some running a windowsXP some running win2k

Can anybody help me figure out how to name the server part of the
printer name with normal lettering ?

T.i.a.
Claus
 
So I understand the problem is that the name SERVER1 in all caps is the
issue?


Open the registry in the users context.

In HKCU\Printers\Connections you will see the connection listed with the
"incorrect" (the server name typically gets added here the same way the user
typed in the name of the server the first time (\\PrintSErvernaMe\) when
adding the printer ) name. Rename ,,SERVER1,, portion of the key. You will
need to really rename it once since PRINTSERVERNAME=printservername, then
rename the key using the name you expect in the UI. If you have the
printers folder open you will see the printer connection fail when changing
the name, but return to ready with the lower case name after the second
rename operation in the registry.

--
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.
 
Thanks a lot !
I am unable to explain why it didn't occur to me to check the
registry.
Worked like a charm, thanks again for the response.

Claus
 
Back
Top