Can't configure Laserjet 2840 print server

[Annelise Wilken]

Hello,

A Customer has a HP Colour laserjet2840 he has manually added the IP address: 192.168.22.201 gateway: 192.168.22.1 and netmask: 255.255.255.0

However he can't configure it on the unix box (server is an N4000-36 running 11.00) through SAM - I've tried telnet'ing onto the IP but I'm receiving connection refused. (I am able to telnet onto other print servers in this environment so I know telnet is ok). I've got a printout of the config settings from the printer and they all look as they should be - I've had the printer powercycled - I can ping the print server but can't connect to it .... does anyone have any ideas???

Thanks in advance!

[Mel Burslan]

Telnet may not necessarily work on all printers. Try opening a browser and point it to the ip address of the printer to see if it is giving you a page with printer characteristics.

also, when you run the command :

lpstat -t | grep

what output do you see ?

[Annelise Wilken]

I've been able to telnet to the same printer at a different site from this server - so I should be able to telnet to this one as the printer is the same type.

lpstat -t | grep - as I've already mentioned I can't create this printer in the print spooler - because the print spooler can't "connect" to it.

[Mel Burslan]

there are two scenarios that come to mind:

1. the jetdirect interface on the printer is dead. Solution is pretty trivial as you can call for hardware support.

2. printer and the server are in two separate network segments and there is some sort of a firewall between the two segments not letting packets to go through. In which case, I'd talk to the network administrators. Without knowing the physical placement of the server and the printer, it is very hard to make suggestions for troubleshooting, but for starters,

Get a plain dumb hub/switch from a local electronics store if you don't have one already.

connect the printer to this hub

connect a laptop computer to this hub (configure laptop's IP address such that it will be in the same subnet as the printer, for instance 192.168.22.2)

telnet from laptop to the printer.

If this does not work, you can pretty much be sure that, the jet direct interface has problems.

Hope this helps

[Annelise Wilken]

I agree! I've mentioned this to the customer - I'll get him to test this and will let you know how it goes.

Thanks for your prompt reply!

Annelise:)

[Bill Hassell]

The selftest page on the printer will provide some additional details that are often overlooked. The most important is the state of the JetDirect interface. If it is dead or not connected or perhaps has an interface config error like dup arp, you'll see that listed on the page. Check that a ping works although this is far too low of a test to dertermine functionality, it just tests for a physical connection.

It is also important to test the printer locally, that is, connect a PC on the same subnet and telnet to it there. If that works OK, the N4000 may be blocked by the networking administrator from accessing that subnet.