B
Blackberry
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
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