chanv
asked on
IP Printing.
Conceptual Question. Should be easy.
Any things to watch out when you do IP Printing on NT4 environment? Any web site talk about IP Printing?
Thanks
Any things to watch out when you do IP Printing on NT4 environment? Any web site talk about IP Printing?
Thanks
We have four HP Printers on our network. When you add a printer to the workstations or server, all you have to do is specify the type of port (not LP1, LP2 etc) and type the IP address of the printer. Our HP Printers came with HP JetAdmin that will go out and find the Network Id for the printer and return it to you setup dialog box. Your printer should have a similar type routine. The older HP650c prints out the Network ID the "Print Test Page"
ASKER
Well...hm...
I know how to add ip printer.. I was not asking that... I was wondering if there is something special I have to watch out for..
Plus, do you mind giving me a web page which talks about ip printing, or related materials...
Thanks anyway, Davcos
I know how to add ip printer.. I was not asking that... I was wondering if there is something special I have to watch out for..
Plus, do you mind giving me a web page which talks about ip printing, or related materials...
Thanks anyway, Davcos
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The answer to this question probably depends on the type of print engine you will be attaching to (i.e. HP JetDirect, etc.)
I know that new HP JetDirect cards (ones that support TCP/IP) accept print jobs from Windows NT print spoolers using TCP/IP print services with no problems. I did have issues when trying to send print jobs specifically from NT spooler to a Fiery print engine that was located across a router on another IP subnet (i.e. printing within the local subnet was fine) and the problem was restricted to NT only. The problem turned out to be in the newest Fiery print driver for NT, switching back to the old driver fixed the problem (and EFI is now aware of the bug).
One "issue" to be concerned with is security. Most print engines (like JetDirect cards) don't have the capabilities of restricting IP packets. If you share an LPR port on you NT server, you can restrict what users are able to attach to that "share" but you may not be able to stop someone with a Windows 95 IP print spooler from directly attaching and printing their favorite GIF images to your expensive, high speed color printer.
There are new print servers out that fit in the palm of your hand, attach to the parallel port of your printer, that have a mini UNIX kernel inside that you can telnet to and configure. They are very functional and allow for a more advanced level of configuration/security.
Good luck to you . . .
I know that new HP JetDirect cards (ones that support TCP/IP) accept print jobs from Windows NT print spoolers using TCP/IP print services with no problems. I did have issues when trying to send print jobs specifically from NT spooler to a Fiery print engine that was located across a router on another IP subnet (i.e. printing within the local subnet was fine) and the problem was restricted to NT only. The problem turned out to be in the newest Fiery print driver for NT, switching back to the old driver fixed the problem (and EFI is now aware of the bug).
One "issue" to be concerned with is security. Most print engines (like JetDirect cards) don't have the capabilities of restricting IP packets. If you share an LPR port on you NT server, you can restrict what users are able to attach to that "share" but you may not be able to stop someone with a Windows 95 IP print spooler from directly attaching and printing their favorite GIF images to your expensive, high speed color printer.
There are new print servers out that fit in the palm of your hand, attach to the parallel port of your printer, that have a mini UNIX kernel inside that you can telnet to and configure. They are very functional and allow for a more advanced level of configuration/security.
Good luck to you . . .
ASKER
Thansks davcos and mbreuker