Windows 2008 Printing

[Gerald Werner]

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

 

[DaveMills]

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.

 

[Gerald Werner]

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

the printers that go offline and have to restart via stop/start spooler.

regards
Gerald

"DaveMills" schrieb im Newsbeitrag
news:umq3e557agkpknv5jla78rsuim3lrvd2nr@4ax.com...
> 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.