Windows 2008 Printing

Hello,

we have several windows 2008 servers x64 at different locations.
All have the actual patchlevel with sp2. Mostly there is one DC with
additional terminalservers.
In general we have printing problems on all machines with different
printers.
The real problem is, that the printers on the terminalservers often go
offline and the jobs in the queue will hang up.
Then we must restart the spooler first on the printserver (DC) and then
restart the spooler on the terminalserver.
After that, the job will print out. That´s allways the only way out.

Indeed I think the drivers are pretty bad in general! Most of the drivers
have problems accessing the trays correctly and we have allways a really
hard job if we had to change a different driver if the just installed one
doesn´t satisfiy ours needs. With the good old windows 2003, we have choosen
a driver from within the printer object and configure ist. That worked very
well also for the client in the network wich takes the new printer
automatically after that.
Most of the time, we must now delete the printer at the client, then delete
the printer at the printserver, add a new one at the print server and then
add a network printer on the client. If I only change the driver in the
running printer object, that doesn´t work really. That´s not what I call a
user-friendly system!

Does anybody have similar problems and maybe a solution?

best regards

Gerald Werner

On Fri, 23 Oct 2009 12:20:50 +0200, "Gerald Werner" <>
wrote:

>Hello,
>
>we have several windows 2008 servers x64 at different locations.
>All have the actual patchlevel with sp2. Mostly there is one DC with
>additional terminalservers.
>In general we have printing problems on all machines with different
>printers.
>The real problem is, that the printers on the terminalservers often go
>offline and the jobs in the queue will hang up.
>Then we must restart the spooler first on the printserver (DC) and then
>restart the spooler on the terminalserver.
>After that, the job will print out. That´s allways the only way out.

Are you using the HP TCPIP ports, On w2003 these will stop all printing if any
printer goes offline. Use the Standard TCPIP port.
>
>Indeed I think the drivers are pretty bad in general! Most of the drivers
>have problems accessing the trays correctly and we have allways a really
>hard job if we had to change a different driver if the just installed one
>doesn´t satisfiy ours needs. With the good old windows 2003, we have choosen
>a driver from within the printer object and configure ist. That worked very
>well also for the client in the network wich takes the new printer
>automatically after that.
>Most of the time, we must now delete the printer at the client, then delete
>the printer at the printserver, add a new one at the print server and then
>add a network printer on the client. If I only change the driver in the
>running printer object, that doesn´t work really. That´s not what I call a
>user-friendly system!
>
>Does anybody have similar problems and maybe a solution?

Is this maybe because the x64 system does not have a 32bit driver so the client
is getting the drive from the install source CD and then not knowing it needs
updating.

>
>best regards
>
>Gerald Werner
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Hello dave,

thabks for your reply. We allways use the standard tcpip ports.
The clients I spoke of are the 64-bit terminalservers, sorry, I was not
clear enough.
I know the problems, that the 32-bit clients have, when they are attached to
an 64-bit printserver, but that´s not the problem. If a 32-bit client is
attached to the 64-bit printer, we use the correct driver if supported.
The problem is
a) "changing the driver" for a printer and
b) the printers that go offline and have to restart via stop/start spooler.

regards
Gerald

"DaveMills" <> schrieb im Newsbeitrag
news:...
> On Fri, 23 Oct 2009 12:20:50 +0200, "Gerald Werner"
> <>
> wrote:
>
>>Hello,
>>
>>we have several windows 2008 servers x64 at different locations.
>>All have the actual patchlevel with sp2. Mostly there is one DC with
>>additional terminalservers.
>>In general we have printing problems on all machines with different
>>printers.
>>The real problem is, that the printers on the terminalservers often go
>>offline and the jobs in the queue will hang up.
>>Then we must restart the spooler first on the printserver (DC) and then
>>restart the spooler on the terminalserver.
>>After that, the job will print out. That´s allways the only way out.
>
> Are you using the HP TCPIP ports, On w2003 these will stop all printing if
> any
> printer goes offline. Use the Standard TCPIP port.
>>
>>Indeed I think the drivers are pretty bad in general! Most of the drivers
>>have problems accessing the trays correctly and we have allways a really
>>hard job if we had to change a different driver if the just installed one
>>doesn´t satisfiy ours needs. With the good old windows 2003, we have
>>choosen
>>a driver from within the printer object and configure ist. That worked
>>very
>>well also for the client in the network wich takes the new printer
>>automatically after that.
>>Most of the time, we must now delete the printer at the client, then
>>delete
>>the printer at the printserver, add a new one at the print server and then
>>add a network printer on the client. If I only change the driver in the
>>running printer object, that doesn´t work really. That´s not what I call a
>>user-friendly system!
>>
>>Does anybody have similar problems and maybe a solution?
>
> Is this maybe because the x64 system does not have a 32bit driver so the
> client
> is getting the drive from the install source CD and then not knowing it
> needs
> updating.
>
>>
>>best regards
>>
>>Gerald Werner
>>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that
> don't.

If you have HP drivers, HP recommends adding a new printer rather than
changing the print driver. Normally this is due to registry
incompatibilities between the print drivers. You can work around this in
many cases by changing the print driver to one that does not contain the
registry bloat before switching to the new driver.
Take a look at the printer registry data under the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Printers

Change the driver to some other driver and refresh the registry to view the
changes.

Don't delete any of the values unless you know what you are doing.

--
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.

"Gerald Werner" <> wrote in message
news:...
> Hello dave,
>
> thabks for your reply. We allways use the standard tcpip ports.
> The clients I spoke of are the 64-bit terminalservers, sorry, I was not
> clear enough.
> I know the problems, that the 32-bit clients have, when they are attached
> to an 64-bit printserver, but that´s not the problem. If a 32-bit client
> is attached to the 64-bit printer, we use the correct driver if supported.
> The problem is
> a) "changing the driver" for a printer and
> b) the printers that go offline and have to restart via stop/start
> spooler.
>
> regards
> Gerald
>
> "DaveMills" <> schrieb im Newsbeitrag
> news:...
>> On Fri, 23 Oct 2009 12:20:50 +0200, "Gerald Werner"
>> <>
>> wrote:
>>
>>>Hello,
>>>
>>>we have several windows 2008 servers x64 at different locations.
>>>All have the actual patchlevel with sp2. Mostly there is one DC with
>>>additional terminalservers.
>>>In general we have printing problems on all machines with different
>>>printers.
>>>The real problem is, that the printers on the terminalservers often go
>>>offline and the jobs in the queue will hang up.
>>>Then we must restart the spooler first on the printserver (DC) and then
>>>restart the spooler on the terminalserver.
>>>After that, the job will print out. That´s allways the only way out.
>>
>> Are you using the HP TCPIP ports, On w2003 these will stop all printing
>> if any
>> printer goes offline. Use the Standard TCPIP port.
>>>
>>>Indeed I think the drivers are pretty bad in general! Most of the drivers
>>>have problems accessing the trays correctly and we have allways a really
>>>hard job if we had to change a different driver if the just installed one
>>>doesn´t satisfiy ours needs. With the good old windows 2003, we have
>>>choosen
>>>a driver from within the printer object and configure ist. That worked
>>>very
>>>well also for the client in the network wich takes the new printer
>>>automatically after that.
>>>Most of the time, we must now delete the printer at the client, then
>>>delete
>>>the printer at the printserver, add a new one at the print server and
>>>then
>>>add a network printer on the client. If I only change the driver in the
>>>running printer object, that doesn´t work really. That´s not what I call
>>>a
>>>user-friendly system!
>>>
>>>Does anybody have similar problems and maybe a solution?
>>
>> Is this maybe because the x64 system does not have a 32bit driver so the
>> client
>> is getting the drive from the install source CD and then not knowing it
>> needs
>> updating.
>>
>>>
>>>best regards
>>>
>>>Gerald Werner
>>>
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that
>> don't.
>
>

Thank you very much for your reply.
I will test it next week due hollidays

regards
Gerald Werner

"Alan Morris [MSFT]" <> schrieb im Newsbeitrag
news:e8Hm2O$...
> If you have HP drivers, HP recommends adding a new printer rather than
> changing the print driver. Normally this is due to registry
> incompatibilities between the print drivers. You can work around this in
> many cases by changing the print driver to one that does not contain the
> registry bloat before switching to the new driver.
> Take a look at the printer registry data under the
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Printers
>
> Change the driver to some other driver and refresh the registry to view
> the changes.
>
> Don't delete any of the values unless you know what you are doing.
>
> --
> 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.
>
> "Gerald Werner" <> wrote in message
> news:...
>> Hello dave,
>>
>> thabks for your reply. We allways use the standard tcpip ports.
>> The clients I spoke of are the 64-bit terminalservers, sorry, I was not
>> clear enough.
>> I know the problems, that the 32-bit clients have, when they are attached
>> to an 64-bit printserver, but that´s not the problem. If a 32-bit client
>> is attached to the 64-bit printer, we use the correct driver if
>> supported.
>> The problem is
>> a) "changing the driver" for a printer and
>> b) the printers that go offline and have to restart via stop/start
>> spooler.
>>
>> regards
>> Gerald
>>
>> "DaveMills" <> schrieb im Newsbeitrag
>> news:...
>>> On Fri, 23 Oct 2009 12:20:50 +0200, "Gerald Werner"
>>> <>
>>> wrote:
>>>
>>>>Hello,
>>>>
>>>>we have several windows 2008 servers x64 at different locations.
>>>>All have the actual patchlevel with sp2. Mostly there is one DC with
>>>>additional terminalservers.
>>>>In general we have printing problems on all machines with different
>>>>printers.
>>>>The real problem is, that the printers on the terminalservers often go
>>>>offline and the jobs in the queue will hang up.
>>>>Then we must restart the spooler first on the printserver (DC) and then
>>>>restart the spooler on the terminalserver.
>>>>After that, the job will print out. That´s allways the only way out.
>>>
>>> Are you using the HP TCPIP ports, On w2003 these will stop all printing
>>> if any
>>> printer goes offline. Use the Standard TCPIP port.
>>>>
>>>>Indeed I think the drivers are pretty bad in general! Most of the
>>>>drivers
>>>>have problems accessing the trays correctly and we have allways a really
>>>>hard job if we had to change a different driver if the just installed
>>>>one
>>>>doesn´t satisfiy ours needs. With the good old windows 2003, we have
>>>>choosen
>>>>a driver from within the printer object and configure ist. That worked
>>>>very
>>>>well also for the client in the network wich takes the new printer
>>>>automatically after that.
>>>>Most of the time, we must now delete the printer at the client, then
>>>>delete
>>>>the printer at the printserver, add a new one at the print server and
>>>>then
>>>>add a network printer on the client. If I only change the driver in the
>>>>running printer object, that doesn´t work really. That´s not what I call
>>>>a
>>>>user-friendly system!
>>>>
>>>>Does anybody have similar problems and maybe a solution?
>>>
>>> Is this maybe because the x64 system does not have a 32bit driver so the
>>> client
>>> is getting the drive from the install source CD and then not knowing it
>>> needs
>>> updating.
>>>
>>>>
>>>>best regards
>>>>
>>>>Gerald Werner
>>>>
>>> --
>>> Dave Mills
>>> There are 10 types of people, those that understand binary and those
>>> that don't.
>>
>>
>
>

Hi Gerald
We have similary problems - did you ever find a solution for you "printer-offline" problem?

best regards /ti



Gerald Werner wrote:

Thank you very much for your reply.
29-Oct-09

Thank you very much for your reply.
I will test it next week due hollidays

regards
Gerald Werner

Previous Posts In This Thread:

On Friday, October 23, 2009 6:20 AM
Gerald Werner wrote:

Windows 2008 Printing
Hello,

we have several windows 2008 servers x64 at different locations.
All have the actual patchlevel with sp2. Mostly there is one DC with
additional terminalservers.
In general we have printing problems on all machines with different
printers.
The real problem is, that the printers on the terminalservers often go
offline and the jobs in the queue will hang up.
Then we must restart the spooler first on the printserver (DC) and then
restart the spooler on the terminalserver.
After that, the job will print out. That?s allways the only way out.

Indeed I think the drivers are pretty bad in general! Most of the drivers
have problems accessing the trays correctly and we have allways a really
hard job if we had to change a different driver if the just installed one
doesn?t satisfiy ours needs. With the good old windows 2003, we have choosen
a driver from within the printer object and configure ist. That worked very
well also for the client in the network wich takes the new printer
automatically after that.
Most of the time, we must now delete the printer at the client, then delete
the printer at the printserver, add a new one at the print server and then
add a network printer on the client. If I only change the driver in the
running printer object, that doesn?t work really. That?s not what I call a
user-friendly system!

Does anybody have similar problems and maybe a solution?

best regards

Gerald Werner

On Friday, October 23, 2009 1:44 PM
DaveMills wrote:

wrote:Are you using the HP TCPIP ports, On w2003 these will stop all printing
wrote:


Are you using the HP TCPIP ports, On w2003 these will stop all printing if any
printer goes offline. Use the Standard TCPIP port.

Is this maybe because the x64 system does not have a 32bit driver so the client
is getting the drive from the install source CD and then not knowing it needs
updating.

--
Dave Mills
There are 10 types of people, those that understand binary and those that do not.

On Saturday, October 24, 2009 1:07 PM
Gerald Werner wrote:

Hello dave,thabks for your reply. We allways use the standard tcpip ports.
Hello dave,

thabks for your reply. We allways use the standard tcpip ports.
The clients I spoke of are the 64-bit terminalservers, sorry, I was not
clear enough.
I know the problems, that the 32-bit clients have, when they are attached to
an 64-bit printserver, but that?s not the problem. If a 32-bit client is
attached to the 64-bit printer, we use the correct driver if supported.
The problem is
a) "changing the driver" for a printer and
b) the printers that go offline and have to restart via stop/start spooler.

regards
Gerald

"DaveMills" <> schrieb im Newsbeitrag

On Wednesday, October 28, 2009 1:25 PM
Alan Morris [MSFT] wrote:

If you have HP drivers, HP recommends adding a new printer rather thanchanging
If you have HP drivers, HP recommends adding a new printer rather than
changing the print driver. Normally this is due to registry
incompatibilities between the print drivers. You can work around this in
many cases by changing the print driver to one that does not contain the
registry bloat before switching to the new driver.
Take a look at the printer registry data under the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Printers

Change the driver to some other driver and refresh the registry to view the
changes.

Don't delete any of the values unless you know what you are doing.

--
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.

On Thursday, October 29, 2009 6:00 AM
Gerald Werner wrote:

Thank you very much for your reply.
Thank you very much for your reply.
I will test it next week due hollidays

regards
Gerald Werner


Submitted via EggHeadCafe - Software Developer Portal of Choice
Generic Feed Parsers Redux
http://www.eggheadcafe.com/tutorials...sers-redu.aspx

The connections go "Offline" or the printers on TCP/IP Ports go into offline
state?

--
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.

<Thomas Iwang> wrote in message news:...
> Hi Gerald
> We have similary problems - did you ever find a solution for you
> "printer-offline" problem?
>
> best regards /ti
>
>
>
> Gerald Werner wrote:
>
> Thank you very much for your reply.
> 29-Oct-09
>
> Thank you very much for your reply.
> I will test it next week due hollidays
>
> regards
> Gerald Werner
>
> Previous Posts In This Thread:
>
> On Friday, October 23, 2009 6:20 AM
> Gerald Werner wrote:
>
> Windows 2008 Printing
> Hello,
>
> we have several windows 2008 servers x64 at different locations.
> All have the actual patchlevel with sp2. Mostly there is one DC with
> additional terminalservers.
> In general we have printing problems on all machines with different
> printers.
> The real problem is, that the printers on the terminalservers often go
> offline and the jobs in the queue will hang up.
> Then we must restart the spooler first on the printserver (DC) and then
> restart the spooler on the terminalserver.
> After that, the job will print out. That?s allways the only way out.
>
> Indeed I think the drivers are pretty bad in general! Most of the drivers
> have problems accessing the trays correctly and we have allways a really
> hard job if we had to change a different driver if the just installed one
> doesn?t satisfiy ours needs. With the good old windows 2003, we have
> choosen
> a driver from within the printer object and configure ist. That worked
> very
> well also for the client in the network wich takes the new printer
> automatically after that.
> Most of the time, we must now delete the printer at the client, then
> delete
> the printer at the printserver, add a new one at the print server and then
> add a network printer on the client. If I only change the driver in the
> running printer object, that doesn?t work really. That?s not what I call a
> user-friendly system!
>
> Does anybody have similar problems and maybe a solution?
>
> best regards
>
> Gerald Werner
>
> On Friday, October 23, 2009 1:44 PM
> DaveMills wrote:
>
> wrote:Are you using the HP TCPIP ports, On w2003 these will stop all
> printing
> wrote:
>
>
> Are you using the HP TCPIP ports, On w2003 these will stop all printing if
> any
> printer goes offline. Use the Standard TCPIP port.
>
> Is this maybe because the x64 system does not have a 32bit driver so the
> client
> is getting the drive from the install source CD and then not knowing it
> needs
> updating.
>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that
> do not.
>
> On Saturday, October 24, 2009 1:07 PM
> Gerald Werner wrote:
>
> Hello dave,thabks for your reply. We allways use the standard tcpip ports.
> Hello dave,
>
> thabks for your reply. We allways use the standard tcpip ports.
> The clients I spoke of are the 64-bit terminalservers, sorry, I was not
> clear enough.
> I know the problems, that the 32-bit clients have, when they are attached
> to
> an 64-bit printserver, but that?s not the problem. If a 32-bit client is
> attached to the 64-bit printer, we use the correct driver if supported.
> The problem is
> a) "changing the driver" for a printer and
> b) the printers that go offline and have to restart via stop/start
> spooler.
>
> regards
> Gerald
>
> "DaveMills" <> schrieb im Newsbeitrag
>
> On Wednesday, October 28, 2009 1:25 PM
> Alan Morris [MSFT] wrote:
>
> If you have HP drivers, HP recommends adding a new printer rather
> thanchanging
> If you have HP drivers, HP recommends adding a new printer rather than
> changing the print driver. Normally this is due to registry
> incompatibilities between the print drivers. You can work around this in
> many cases by changing the print driver to one that does not contain the
> registry bloat before switching to the new driver.
> Take a look at the printer registry data under the
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Printers
>
> Change the driver to some other driver and refresh the registry to view
> the
> changes.
>
> Don't delete any of the values unless you know what you are doing.
>
> --
> 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.
>
> On Thursday, October 29, 2009 6:00 AM
> Gerald Werner wrote:
>
> Thank you very much for your reply.
> Thank you very much for your reply.
> I will test it next week due hollidays
>
> regards
> Gerald Werner
>
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Generic Feed Parsers Redux
> http://www.eggheadcafe.com/tutorials...sers-redu.aspx

On Fri, 05 Mar 2010 02:48:53 -0800, Thomas Iwang wrote:

> Hi Gerald
> We have similary problems - did you ever find a solution for you "printer-offline" problem?
>

Check out these links:

http://support.microsoft.com/kb/968585
http://support.microsoft.com/kb/958894

If it helps, let us know.

--
Pozdrav
===========

I experienced the problem with having a printer as showing offline in the
print queue on my print server. It happened after I disabled protocols I
didn't user (or thought I didn't use). I had to enable SNMP on the printer
and the print queue recongized the printer as online (which it was the whole
time).

"Matija Kapraljevic [Revenger]" wrote:

> On Fri, 05 Mar 2010 02:48:53 -0800, Thomas Iwang wrote:
>
> > Hi Gerald
> > We have similary problems - did you ever find a solution for you "printer-offline" problem?
> >
>
> Check out these links:
>
> http://support.microsoft.com/kb/968585
> http://support.microsoft.com/kb/958894
>
> If it helps, let us know.
>
> --
> Pozdrav
> ===========
> .
>