Hi All

Been installing HP2600N's at schools no problem in a server environment.

Installed 2 today (ie configured static ip on each (school rule), installed
the driver on the Win2k3 server via the installer cd, restarted the server
(mandatory), shared the printers and config'd GPO to 'push' these printers
to the user accounts) and had a absolute shocker when I came to log on with
any user account.

Basically bombs with a exception error when each printer drops in, says that
Windows' DE has protected me from the SubSpool something app, stopped the
print spooler service and won't let me restart it and lost all of my
printers (inc 2 other network ones that were on there).

Tried to login on several machines and all doing the same.

Phoned HP up and they said the HP2600N Win2k3 server driver wasn't designed
to run this way it was designed for client machines that run Win2k3 server
instead of WinXP Pro - what absolute crap!

Removed all printers, ports and drivers from the server (several restarts
later), downloaded the latest driver from their web site, logged into each
machine and ran the print uninstaller from the C:\windows\system32\spool
folder and then installed the new driver on the server and re-shared/pushed
it back. Didn't get the spooler blow ups, but when I printed a doc the doc
would just sit there and wouldn't go until I stopped and start the print
spooler service on the server!

Noticed that the printers were using HP ports instead of standard TCP/IP
ports so changed these over to see if it makes a difference.

Noticed that limited users couldn't 'add' the printers when logging on
because the system said they didn't have the necessary permissions. Logged
on again and then for some reason they could add the printer, but others
couldn't with the exact same printer!

Even though a lot of them could print without resetting the print spooler
still found that the odd ones would still have docs sat waiting in the
queue!

What on earth has gone wrong???

Has anybody else had this kind of problem?

Is there any way to properly cure this?

Thanks

Hello Blackberry,

To install the printer for 2003 server and xp clients, you have to specify
the different drivers for both operating systems. On the server install it
as local printer with TCP/IP port and the preconfigured ip address with the
2003 driver. Just choose the option if windows does not know the printer
"Have Disk..." and point to the folder where you have put the drivers (take
the new from HP website).
Configure the printer settings for your needs.
Then you have to add the drivers for XP as additional drivers to the print
server, under the sharing tab you can find a button additional drivers. Here
you can add the drivers for XP, so that the clients get the correct drivers
for XP from the server.

Drivers for 2000 2003 XP Vista etc.:
http://h20000.www2.hp.com/bizsupport...153&taskId=135

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.dts-l.org/goodpost.htm

> Hi All
>
> Been installing HP2600N's at schools no problem in a server
> environment.
>
> Installed 2 today (ie configured static ip on each (school rule),
> installed the driver on the Win2k3 server via the installer cd,
> restarted the server (mandatory), shared the printers and config'd GPO
> to 'push' these printers to the user accounts) and had a absolute
> shocker when I came to log on with any user account.
>
> Basically bombs with a exception error when each printer drops in,
> says that Windows' DE has protected me from the SubSpool something
> app, stopped the print spooler service and won't let me restart it and
> lost all of my printers (inc 2 other network ones that were on there).
>
> Tried to login on several machines and all doing the same.
>
> Phoned HP up and they said the HP2600N Win2k3 server driver wasn't
> designed to run this way it was designed for client machines that run
> Win2k3 server instead of WinXP Pro - what absolute crap!
>
> Removed all printers, ports and drivers from the server (several
> restarts later), downloaded the latest driver from their web site,
> logged into each machine and ran the print uninstaller from the
> C:\windows\system32\spool folder and then installed the new driver on
> the server and re-shared/pushed it back. Didn't get the spooler blow
> ups, but when I printed a doc the doc would just sit there and
> wouldn't go until I stopped and start the print spooler service on the
> server!
>
> Noticed that the printers were using HP ports instead of standard
> TCP/IP ports so changed these over to see if it makes a difference.
>
> Noticed that limited users couldn't 'add' the printers when logging on
> because the system said they didn't have the necessary permissions.
> Logged on again and then for some reason they could add the printer,
> but others couldn't with the exact same printer!
>
> Even though a lot of them could print without resetting the print
> spooler still found that the odd ones would still have docs sat
> waiting in the queue!
>
> What on earth has gone wrong???
>
> Has anybody else had this kind of problem?
>
> Is there any way to properly cure this?
>
> Thanks
>

Hi Meinolf

Many thanks for this.

I did set up both printers as raw tcp/ip ports, but for some reason on one
PC the print jobs won't leave the queue. I can't even delete them. I have
to stop and start the print spooler service for the job to move on.

Rgds

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb666b7868c9f38c655ef57d@msnews.microsoft .com...
Hello Blackberry,

To install the printer for 2003 server and xp clients, you have to specify
the different drivers for both operating systems. On the server install it
as local printer with TCP/IP port and the preconfigured ip address with the
2003 driver. Just choose the option if windows does not know the printer
"Have Disk..." and point to the folder where you have put the drivers (take
the new from HP website).
Configure the printer settings for your needs.
Then you have to add the drivers for XP as additional drivers to the print
server, under the sharing tab you can find a button additional drivers. Here
you can add the drivers for XP, so that the clients get the correct drivers
for XP from the server.

Drivers for 2000 2003 XP Vista etc.:
http://h20000.www2.hp.com/bizsupport...153&taskId=135

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.dts-l.org/goodpost.htm

> Hi All
>
> Been installing HP2600N's at schools no problem in a server
> environment.
>
> Installed 2 today (ie configured static ip on each (school rule),
> installed the driver on the Win2k3 server via the installer cd,
> restarted the server (mandatory), shared the printers and config'd GPO
> to 'push' these printers to the user accounts) and had a absolute
> shocker when I came to log on with any user account.
>
> Basically bombs with a exception error when each printer drops in,
> says that Windows' DE has protected me from the SubSpool something
> app, stopped the print spooler service and won't let me restart it and
> lost all of my printers (inc 2 other network ones that were on there).
>
> Tried to login on several machines and all doing the same.
>
> Phoned HP up and they said the HP2600N Win2k3 server driver wasn't
> designed to run this way it was designed for client machines that run
> Win2k3 server instead of WinXP Pro - what absolute crap!
>
> Removed all printers, ports and drivers from the server (several
> restarts later), downloaded the latest driver from their web site,
> logged into each machine and ran the print uninstaller from the
> C:\windows\system32\spool folder and then installed the new driver on
> the server and re-shared/pushed it back. Didn't get the spooler blow
> ups, but when I printed a doc the doc would just sit there and
> wouldn't go until I stopped and start the print spooler service on the
> server!
>
> Noticed that the printers were using HP ports instead of standard
> TCP/IP ports so changed these over to see if it makes a difference.
>
> Noticed that limited users couldn't 'add' the printers when logging on
> because the system said they didn't have the necessary permissions.
> Logged on again and then for some reason they could add the printer,
> but others couldn't with the exact same printer!
>
> Even though a lot of them could print without resetting the print
> spooler still found that the odd ones would still have docs sat
> waiting in the queue!
>
> What on earth has gone wrong???
>
> Has anybody else had this kind of problem?
>
> Is there any way to properly cure this?
>
> Thanks
>

Hi there,

in fact, HP 2600 is not supported in terminal services too. We're having a
very similar problem trying to use it in Citrix over Win2k3.

Best regards,

SaRuRo

"Blackberry" wrote:

> Hi Meinolf
>
> Many thanks for this.
>
> I did set up both printers as raw tcp/ip ports, but for some reason on one
> PC the print jobs won't leave the queue. I can't even delete them. I have
> to stop and start the print spooler service for the job to move on.
>
> Rgds
>
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb666b7868c9f38c655ef57d@msnews.microsoft .com...
> Hello Blackberry,
>
> To install the printer for 2003 server and xp clients, you have to specify
> the different drivers for both operating systems. On the server install it
> as local printer with TCP/IP port and the preconfigured ip address with the
> 2003 driver. Just choose the option if windows does not know the printer
> "Have Disk..." and point to the folder where you have put the drivers (take
> the new from HP website).
> Configure the printer settings for your needs.
> Then you have to add the drivers for XP as additional drivers to the print
> server, under the sharing tab you can find a button additional drivers. Here
> you can add the drivers for XP, so that the clients get the correct drivers
> for XP from the server.
>
> Drivers for 2000 2003 XP Vista etc.:
> http://h20000.www2.hp.com/bizsupport...153&taskId=135
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** us YOU!!! http://www.dts-l.org/goodpost.htm
>
> > Hi All
> >
> > Been installing HP2600N's at schools no problem in a server
> > environment.
> >
> > Installed 2 today (ie configured static ip on each (school rule),
> > installed the driver on the Win2k3 server via the installer cd,
> > restarted the server (mandatory), shared the printers and config'd GPO
> > to 'push' these printers to the user accounts) and had a absolute
> > shocker when I came to log on with any user account.
> >
> > Basically bombs with a exception error when each printer drops in,
> > says that Windows' DE has protected me from the SubSpool something
> > app, stopped the print spooler service and won't let me restart it and
> > lost all of my printers (inc 2 other network ones that were on there).
> >
> > Tried to login on several machines and all doing the same.
> >
> > Phoned HP up and they said the HP2600N Win2k3 server driver wasn't
> > designed to run this way it was designed for client machines that run
> > Win2k3 server instead of WinXP Pro - what absolute crap!
> >
> > Removed all printers, ports and drivers from the server (several
> > restarts later), downloaded the latest driver from their web site,
> > logged into each machine and ran the print uninstaller from the
> > C:\windows\system32\spool folder and then installed the new driver on
> > the server and re-shared/pushed it back. Didn't get the spooler blow
> > ups, but when I printed a doc the doc would just sit there and
> > wouldn't go until I stopped and start the print spooler service on the
> > server!
> >
> > Noticed that the printers were using HP ports instead of standard
> > TCP/IP ports so changed these over to see if it makes a difference.
> >
> > Noticed that limited users couldn't 'add' the printers when logging on
> > because the system said they didn't have the necessary permissions.
> > Logged on again and then for some reason they could add the printer,
> > but others couldn't with the exact same printer!
> >
> > Even though a lot of them could print without resetting the print
> > spooler still found that the odd ones would still have docs sat
> > waiting in the queue!
> >
> > What on earth has gone wrong???
> >
> > Has anybody else had this kind of problem?
> >
> > Is there any way to properly cure this?
> >
> > Thanks
> >
>
>
>
>