I like Hewlett Packard for their whole range of products including their network printers.
Now a days it is almost difficult to get a printer that is NOT network ready… but for a nice stable network without to much collisions and traffic towards those network printers there are some features that you might want to close down on those printers.
Hewlett Packard and other manufactures support several protocols on their network interface. To reduce traffic you can close down all that you don’t need for you network.
The TCP/IP protocoll is the most widely used for all kin of networks so you will keep that running.
If you are not running an Novell or Apple based network you can disable their respective protocols IPX/SPC and Appletalk.
Have your printers installed on a separate print-server with a enough free disk space to make sure the processing of the print job will not be hindered. if you need to you can assign the spool directory to a differen disk than the default c: drive on the server.
Name you printers so you can recognized them, but keep the names short and without blanks for installation purposes. You can give more information about the location of the printer in the seperate comments field on the server where you installed the printer and its driver.
Hello Herbert,
I’ve used the Network DNA structure for a few years. I saw it had stagnated for a while thanks for bringing it back. I use it to document my networks and systems. While I have won any awards, yet, I’ve received a lot of praise on it’s clarity and consistency. I’d like to see if I could help you flesh your site out a bit more. Please let me know if I could help.
@Joel, The NetworkDNA structure is indeed really clear work with and I hope you will win some Awards with it!
I am currently in the process of gathering all the information I collected over the years and are looking into the best way to put in into this site. Thank you for your offer and I might just take you up on that later on in the process.