The problem of the day appears to be NDPS. There is quite a push to get NDPS deployed because the server currently being used for queue-based-printing is an ooooold NW4.11 box. We need to get that out of the way. For one, it'll help us on the road to a network that just runs TCP/IP. For two, it'll get rid of some really creaky hardware.
The problems are many. A couple of HP printers are showing decided recalcitrance when it comes to being set up. The HP LaserJet 4200 is a prime offender, with the HP 5M a close second. Also, NDPS-objects that don't distribute a print driver are having issues sending jobs to printers. Sometimes, it'll print two pages. Sometimes, not at all. Unfortunately, that problem doesn't have a pattern yet, which makes troubleshooting problematic.
In other news, it looks possible to wire the Macintosh labs so they route jobs through NDPS. It won't get audited by PCounter, which they aren't now anyway, but it would centralize that function nicely. In the future, once such accounting can be put in place, it will be a matter of changing things on the servers and not on the clients.
The problems are many. A couple of HP printers are showing decided recalcitrance when it comes to being set up. The HP LaserJet 4200 is a prime offender, with the HP 5M a close second. Also, NDPS-objects that don't distribute a print driver are having issues sending jobs to printers. Sometimes, it'll print two pages. Sometimes, not at all. Unfortunately, that problem doesn't have a pattern yet, which makes troubleshooting problematic.
In other news, it looks possible to wire the Macintosh labs so they route jobs through NDPS. It won't get audited by PCounter, which they aren't now anyway, but it would centralize that function nicely. In the future, once such accounting can be put in place, it will be a matter of changing things on the servers and not on the clients.