Network Printing in a Windows World

[mheffernan]

Hi...I am loathe to rely on Windows 2000 Server to reliably handle network print jobs to our 25 or so HP laser printers, especially since I have had a NW 3.20 machine doing it so well for so many years.

But the 3.20 machine is old and needs to be replaced. Should I build another 3.20 server with IDE drives (or SCSI if I can find drivers) or bump up to NW 5 and eliminate IPX altogether? I used to be a CNE and am completely unimpressed with Windows network print job spooling.

Jus' looking for opinions...thanks.
Mike

 

[LawnBoy]

By all means, upgrade to 5.1 (at least), eliminate IPX, and install NDPS (Novell Distributed Print Services). NDPS is easy and bulletproof.

One caveat: When selecting gateways for your printers, use the Novell gateway. HP does have a gateway, but they (HP) stopped supporting it and it has become dated, causing some problems with newer HP printers.

Go for it, you'll never look back.

 

[marvhuffaker]

I concur. Update NetWare and install NDPS. NDPS is by far the best printing system ever developed. Windows printing can't touch it. If you're going to upgrade, you might as well go to NW6.5 - but only if you upgrade your hardware as well. NetWare 5.1 is probably a better choice for your existing hardware as NetWare 6.5 is a resource hog (compared to NW5.1).

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[summoner]

Just curious, and if up to me, I'd use NetWare for printing anyway. But I have to ask, whats so bad about windows printing/spooling? You would think that network printing is not a new concept. I've implemented shared windows printers and it works. What does netware, perhaps besides iPrint, have that windows doesnt?

 

[LawnBoy]

Windows shares are unmanaged and therefore beneath contempt
(where's the job if the connection's broken? how many jobs ran today?)

As far as server-based print systems go, I consider NDPS better than NT4 DC methodology (I don't know if AD works differently, never tried it) in the following categories:

1. recovery and/or reassignment of jobs
2. creation/configuration of printers
3. assignment of user rights to various printers
4. control and installation of drivers used
5. general ease of use (productivity)

But most of all I like it because it's STABLE. It doesn't demand my attention, or do strange, quirky things that only a server reboot will fix. Even if it were dificult to manage (which it is far from) I would still use it because it's STABLE.

One more time for the back row: NDPS IS STABLE.

I'll climb off my soapbox now...

 

[marvhuffaker]

The funny thing is that a lot of people these days think that printing is just a dumb service that has been around for years and all Printing services are the same. So who cares if it's running on Windows or Netware or something else. It all works the same, right? Well, if you are a Windows flunky than that is true. But if you've used NDPS you know that NDPS is far superior to anythink Windows has ever done with their printing services.

Besides the stuff that Lawnboy mentioned, and I agree with completely....

NDPS is FULLY integrated with eDirectory. You leverage the power of eDirectory to deploy the printers automatically. What I mean is that you can control who gets a printer (automatically) based on their Context, Group, or UserID.. You don't have to run clunky utilities to push out printers. You don't have to babysit the printers, nor do you have to babysit the end users to keep their printers working. You can see all of the printers and their status in one location and troubleshoot and manage them centrally. You can easily update the drivers and change drivers completely and have those updates automatically pushed out to the users. You can prevent users from installing any printers except the ones you assign to them. You can also remove printers from the users workstations automatically if you ever decommission a printer. The amount of maintenance for each end user is so small that you almost forget that it's part of your job.

You will find that in a Windows printing environment where you either have shares or everybody prints using direct IP, that there is a significant amount of work involved with setting up and managing printers on each workstation. Not too big of a deal with small companies, but with bigger companies this can mean tons and tons of money wasted maintaining a Windows printing system. Talk to anybody that uses NDPS and you'll find that the cost of managing printers is minimal.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[lgarner]

I agree. I wouldn't switch to NetWare to get NDPS, but it is great for NetWare shops. I would definitely upgrade to something. I'm pretty sure that NW 3.2 is EOL, and IPX is passe. NW 5.0 was terrible, 5.1 was pretty good. I have no production experience with 6.x as I switched jobs and no longer work with NetWare. I do remember that NDPS worked nicely. If you're going to keep NetWare, that's definitely the way to go.

 

[ITsmyfault]

fwiw
I'd move up to 5.1, pure IP and put in NDPS as well. 6.x is going to need a hardware boost. NW 5.1 is 7 support packs in and is very stable. Skip 5.0.. it was not fully baked, esp NSS. Also agree on not using hp gateway. Use the Novell gateway and read the TID on lpr names for the various brands. that's the key to getting them all to work right IME. NDPS is like zen for printing.. it's easy to use, saves you tons of time and just works. I image a workstation, put it in place and when the person logs in all of the appropriate printers install themselves. You can even set their default printer up in the directory.. The only time they have trouble printing is when the windows spooler crashes!