Prev: windows xp and windows server 2003 remote access login question
Next: Volume Shadow copy question
From: Alan Morris [MSFT] on 31 Mar 2010 12:19
If you are using the driver name for the printer name, changing the driver
will change the printer name and break the connection. I'll assume 2003 is
32bit. Set the printer name to something other than the driver name in any
multi user environment.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"JohnB" <jbrigan(a)yahoo.com> wrote in message
news:%23lFj87M0KHA.3680(a)TK2MSFTNGP04.phx.gbl...
> I'm using the Postscript driver, and for whatever reason, that works fine
> with PDFs.
> I still haven't figured out the other problem.... why workstations lose
> their connection to this shared printer, when I change the driver on the
> server. And... if I change the driver on my workstation, it changes the
> driver on the server. At which point I lose connection with that printer.
> Very strange.
>
> So what I've done for now is use direct TCP/IP printing (with the PS
> driver) for those that had the problem with PDFs.
>
>
>
> "DaveMills" <DaveMills(a)newsgroup.nospam> wrote in message
> news:9s12r5tkg2m22gtu07knq7dhgt6abnt9n4(a)4ax.com...
>> On Wed, 24 Mar 2010 08:48:09 -0400, "JohnB" <jbrigan(a)yahoo.com> wrote:
>>
>>>We have a HP 2605dtn that is shared out on a Windows 2003 server. This
>>>week
>>>people have been complaining that PDF files take a long time to print.
>>>It
>>>prints a page, then stops, then starts back up.
>>>
>>>The driver on the server is a PCL6 driver. I have had problems in the
>>>past
>>>with PCL6 drivers, so I went to HP's site, but did not find a PCL5
>>>driver,
>>>just a PostScript driver.
>>>
>>>I downloaded that and changed the driver on the server. Now on my PC,
>>>it's
>>>saying "printer not found on server". The share name is the same. If I
>>>change it back to the PCL6 driver, my workstation finds the printer
>>>again.
>>>I wasn't expecting it to work that way. Is that normal behavior? All I
>>>changed was the driver on the server, not the share name.
>>>
>>>Thanks.
>>>
>> I think the 2605 is supported by the HP Universal Driver, you might try
>> switching to that.
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that
>> don't.
>
>


From: Mervyn Zhang [MSFT] on 29 Mar 2010 21:15
Hello,

The managed support service of the newsgroup Windows Server General is now
available instead on:

Windows Server
http://social.technet.microsoft.com/Forums/en-US/category/windowsserver

Would you please repost the question in the forum with the Windows Live ID
used to access your Subscription benefits? Our engineers will assist you in
the new platform. In the future, please post Windows Server related
questions directly to the forums. If you have any questions or concerns,
please feel free to contact us: tngfb(a)microsoft.com.

Regards,
Mervyn Zhang
Microsoft Online Community Support

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

From: JohnB on 1 Apr 2010 11:53
Yes it's 2003 32bit. Yeah, it does change the printer name on the server
when I change the driver. So I just changed the printer name on the server
to just "HP Deskjet 2605". And changed to the PS driver. And changing that
name did break the connection. I deleted the printer on a couple clients
and re-added it.

So you're saying, if I were to change the driver again on the server, if I
made sure the printer name stayed the same as I have it now it would not
break the connection?

Seems counter-intuitive to me. I thought all that mattered with a shared
resource was the NetBIOS name.



"Alan Morris [MSFT]" <alanmo(a)online.microsoft.com> wrote in message
news:OasQ63O0KHA.220(a)TK2MSFTNGP06.phx.gbl...
> If you are using the driver name for the printer name, changing the driver
> will change the printer name and break the connection. I'll assume 2003
> is 32bit. Set the printer name to something other than the driver name in
> any multi user environment.


From: Alan Morris [MSFT] on 1 Apr 2010 14:00
The spooler connects to the printer name even when connecting to the share
name. Now that you have setup the printer name so it does not correspond to
the driver name, you will not break the connection. You can always change
the printer name back to the previous driver name and that will allow the
clients access. Netbios is just the server name, it has nothing to do with
the shares. Change a shared folder name, you will break anyone's mapped
drive.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"JohnB" <jbrigan(a)yahoo.com> wrote in message
news:OISC0Nb0KHA.4832(a)TK2MSFTNGP04.phx.gbl...
> Yes it's 2003 32bit. Yeah, it does change the printer name on the server
> when I change the driver. So I just changed the printer name on the
> server to just "HP Deskjet 2605". And changed to the PS driver. And
> changing that name did break the connection. I deleted the printer on a
> couple clients and re-added it.
>
> So you're saying, if I were to change the driver again on the server, if I
> made sure the printer name stayed the same as I have it now it would not
> break the connection?
>
> Seems counter-intuitive to me. I thought all that mattered with a shared
> resource was the NetBIOS name.
>
>
>
> "Alan Morris [MSFT]" <alanmo(a)online.microsoft.com> wrote in message
> news:OasQ63O0KHA.220(a)TK2MSFTNGP06.phx.gbl...
>> If you are using the driver name for the printer name, changing the
>> driver will change the printer name and break the connection. I'll
>> assume 2003 is 32bit. Set the printer name to something other than the
>> driver name in any multi user environment.
>
>


From: DaveMills on 2 Apr 2010 02:44
On Thu, 1 Apr 2010 11:00:47 -0700, "Alan Morris [MSFT]"
<alanmo(a)online.microsoft.com> wrote:

>The spooler connects to the printer name even when connecting to the share
>name. Now that you have setup the printer name so it does not correspond to
>the driver name, you will not break the connection. You can always change
>the printer name back to the previous driver name and that will allow the
>clients access. Netbios is just the server name, it has nothing to do with
>the shares. Change a shared folder name, you will break anyone's mapped
>drive.

Personally I find the default printer names confuses users in a network printing
environment. I always name the local printer the same as the share name for it.
Thus I may use the printer name Room101Col and the same for the share name.
Users get a bit confused if the name is "HP Color JoaseJet 2600n" but they have
to connect to "HP2600"
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
First  |  Prev  | 
Pages: 1 2
Prev: windows xp and windows server 2003 remote access login question
Next: Volume Shadow copy question