General discussion

Locked

IP Printing In An NT 4.0 Environment

By Kevdog78 ·
I have a question dealing with IP Printing in a Windows NT 4.0 environment. I currently have several Hewlett-Packard Jet Direct devices on my network that are currently using a printer share one of my servers. What I am hoping to do is relieve the Windows NT 4.0 Servers from providing their resources to these Jet Direct printers. What I have been doing to set the current configuration up is as follows:

1.) Create a printer on the Windows NT 4.0 Server using the My Computer option.
2.) The next thing that I do is select the HP Jet Direct port and specify the MAC address of the Jet Direct device.
3.) Next I provide both a local printer name and a share name.
4.) What I do next is visit my customer?s desktop and add the printer viathat Network Printer option and simply provide the remaining printer information. (i.e. print driver, etc.)

As I said earlier in this posting I am hoping to have my users print directly to these JetDirect printers using strictly IP. Please contact me at kev_barry@hotmail.com Any and all assistance will be greatly appreciated.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

IP Printing In An NT 4.0 Environment

by DAO251 In reply to IP Printing In An NT 4.0 ...

I believe your scenario is not very good from administrative point of view. How much resources do JetDirects eat??? I believe just few percents...

Using NT as printserver you could install JetAdmin and printer dirivers (for NT and 95 clients) only ONCE on the server. Clients then just connect to the printer and drivers are updated automatically every time. And they do not depend on protocols, printer address etc.

In your scenario you'll have to do that on every client. In case you decide to reconfigure something (upgrade jetdirect firmware, change addresses, names, etc) -- you'll have reconfigure every client machine.

You want to:
1) either install JetAdmin software on every client or use LPR port (if your JetDirect firmware supports this)
2) install printer driver on every client.

Collapse -

IP Printing In An NT 4.0 Environment

by Kevdog78 In reply to IP Printing In An NT 4.0 ...

I am sorry to say that this information did not help me to solve the problem at hand. I do have JetAdmin installed on my workstation and I am able to monitor the status of JetDirect printers; however, I am not able to specify drivers or anything like that to that specific printer via JetAdmin. What I am really trying to do is take Windows NT totally out of the picture and just print directly to the JetDirect.

Collapse -

IP Printing In An NT 4.0 Environment

by gregpip In reply to IP Printing In An NT 4.0 ...

In our network we have several HP printers that have Jet Direct cards. At each workstation you will need to ensure that Microsoft TCP/IP printing is installed.
1.) Add Printer -> Select My Computer -> Next
2.) Click the Add Port button -> select LPR Port then click the New Port button.
3.) Type in the IP address of the printer. For the port name type 'RAW'. Then OK.
4.) Close the Add Port dialog box. Then continue with the rest of the printer installation.

This setup has worked well for most all of the HP printers that we have on our network.

Collapse -

IP Printing In An NT 4.0 Environment

by Kevdog78 In reply to IP Printing In An NT 4.0 ...

I had a feeling that I was going to need to install that Service on the clients. That is actually the same exact procedure that we are doing now; however instead of having the clients print to something like \\ServerName\PrinterName I wanted to have the print directly to the printer. I believe that this will work by specifying something like this \\10.1.1.5, but what I ideally wanted to to do was have the clients reference these printers as \\HP LaserJet 4. The only way that I can think of doing it to possibly make a DNS host entry for each printer and name each printer uniquely. Please advise if you have any further suggestions.

Collapse -

IP Printing In An NT 4.0 Environment

by DAO251 In reply to IP Printing In An NT 4.0 ...

Let me rephrase (sorry for my English)

you cannot reference JetDirect as \\10.x.x.x or \\name.

In your scenario, printer must be LOCAL and must be connected to a "port" -- either LPR port or JetDirect port.

LPR port is a part of Windows TCP/IP printing services and HP Jet Direct port is part of JetAdmin package.

In both cases you must install:
1) port driver and
2) printer driver
locally on the client (because JetDirect knows nothing about windows and drivers)

Installing LPRor JetDirect port on the server you would be able to:
1) control printers queues from SINGLE point
2) install printer drivers only once (and change when needed in ONE place)
3) control access rights
etc. etc.

Collapse -

IP Printing In An NT 4.0 Environment

by Kevdog78 In reply to IP Printing In An NT 4.0 ...

Poster rated this answer

Collapse -

IP Printing In An NT 4.0 Environment

by dbowlin In reply to IP Printing In An NT 4.0 ...

Re-read #2. Your notes look like you do not understand what it is telling you. You are adding a workstation local port (LPR) to the Printer IP address, not a network share. When setting up the port I usually choose the name I want to use for the printer instead of RAW. After the port is created and you continue with the printer set up you will be asked to name the printer, this is where you can put in a user friendly name.

One other note: I would recommend shortening your printer name and not using any spaces. There are a lot of programs out there, even current generation, which will not properly print to printers with long printer names, or names with spaces.

Good luck,

Collapse -

IP Printing In An NT 4.0 Environment

by Kevdog78 In reply to IP Printing In An NT 4.0 ...

Poster rated this answer

Collapse -

IP Printing In An NT 4.0 Environment

by Kevdog78 In reply to IP Printing In An NT 4.0 ...

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums