Configuer Printer Connected through Router

[Harikrishna Babu]

Hi,

We're using HP-UX 11.0 and some of our printers are installed in a remote site. The remote site is connected through a router with different gateway address.

Now, I could able to ping the print server but the print jobs are not moving out from the queue.

Looks like, i need to configure those router/gateway in the HP-UX Server. If so, how to proceed. Please send some guidelines.

Rgds,

[Alexander M. Ermes]

Hi there.
Download the jetadmin software.

http://www.hp.com/cposupport/nonjsnav/netprn.html

Then you should be able to confgure your printers as network printers no matter where they are. The data you will need from these printers are :

MAC ( hardware ) address
IP-address
Gateway
subnet mask

Rgds
Alexander M. Ermes

[Harikrishna Babu]

Hi,

I've already configured similar printers which is on site, using the HP Jet Direct Software.

But this one is unique, sitting in the remote site under different gateway. I could able to configure, but whatever jobs I submit, all sitting in the queue. Not printing at all!

Rgds,

[Harikrishna Babu]

Hi Ermes,

From the jetadmin, when I access "View HP JetDirect interface's current configuration"
for this printer, it comes out with following information.

Card IP Address : lp1 (10.7.128.3)
Network Mask : 10.7.128.3
Default Gateway : ??? (10.7.128.1)
Idle Timeout : 90 seconds

I found that the Network Mask is same as my jetdirect's IP address instead of 255:255:255:0. It's fine with other printers configured in our main site. I suspect this could be the cause for failure. Any clues?

Best Rgds,

[Stefan Schulz]

If you have a slow connection to the remote site, your timeout might be to small. Its possible that your lp deamon gets a timeout because it takes more than 90 seconds to build up the connection and get a response from the printer.

Just for a test i would reconmend setting your timeout vlaue to e.g. 300.

Hope this helps

Regards Stefan

[Bill Hassell]

Since you have JetAdmin already installed, just run the hpnpadmin command---there are MANY options, the easiest to remember is:
/opt/hpnp/bin/hpnpadmin -v 12.34.56.78 (where the 12.34.56.78 is the IP address).

If all is well, you will get a lot of response information. If the printer does not have a community name or tftp downloaded data like a location and a person's name to contact, you'll see Fail(1) on one line, but that's fine. If hpnpadmin fails, use the various options to determine the reason. ping is far too simple to verify anything except the IP address.

[Wodisch]

Hello Harikrishna,

might be a silly question, but:
Have you checked if you can "ping" that remote printer?
Perhaps you do not have to route to it or it does not
have a route back to your station...

HTH,
Wodisch