HP Laserjet 4MV Networking

[Carp1812]

I recently bought a used HP Laserjet 4MV printer. It has the Jetdirect J2552B 10 Mbps network card in it (Firmware Revision A.05.05). The printer works fine with the parallel port, but I want to set it up to use the network interface because I send large CAD files fairly regularly. I have been unsuccessful in setting up the card. I performed a cold reset of the printer and got it to revert to the default IP of 192.0.0.192. I am unable to telnet into it though. Supposedly, I can telnet and change the IP address, etc. to configure it to my network. I believe that the card is working, because if I leave it connected to my network and reset it, the DHCP server assigns it an IP (although I still can't telnet to it). I can print the test page that displays the IP address, so I know that I'm using the correct IP address when I attempt to telnet. I'm trying to connect to the printer using a laptop (XP Pro) and a crossover cable. I know the cable is good because I took it out of my existing network where it was working. I know the network card on the laptop is working also. I configured the laptop to use IP 192.0.0.191 on the same 255.255.255.0 subnet as the printer. I also tried removing the Jetdirect card from the printer, resetting the printer, reinstalling the card, and resetting the printer again. Still no luck. Any suggestions for me to try? Do you think I have a bad Jetdirect card? Thanks for your tips.

 

[Carp1812]

Also:
I can ping the printer successfully.

 

[Smilin]

Goto HP's website and download JetAdmin software. There are a bunch of flavors, but the web based on seems to work the best. Fire up JetAdmin and use it to find your jet direct that you've got on your local network. It will allow you to make changes and set it up properly - after that telnet is typically better.

 

[kpb]

The other option should be to configure it threw the front panel on the printer it's self. Any of the printers with an LCD should be able to configure most options threw the front panel. The best option tho is the jet admin util or hp lj utility on the mac side =)

 

[redbeard1]

The link below shows the operating systems that the card will work on. The important thing is that tcp/ip is not supported in a windows enviroment, only in a unix server network. I had a similar card to test for a friend, and had to add the DLC/LLC network protocol to a windows 2000 system. Then it could be added to that system as a printer.

What he did with it, was he installed DLC/LLC on his win2k server. Had the server add it as a printer, then had the clients grab the server printer share.

HP

 

[Arcanedeath]

You can configure the Jet direct card via the front pannel on the printer (I belive it's the MIO menu on that model) and then just print to an IP and it works just fine at least under Xp/2k. Hope this helps....

 

[Carp1812]

Red Beard,
Can you give me any more information on DLC/LLC as I am not familiar with it. I would appreciate any resources that you can point me to. I have a win2k server machine on my network, so I'll likely go the route you mentioned in your previous post. Thanks.

 

[redbeard1]

It's been a while since I did this, so I don't remember all the exact details. I did call my friend and ask him if he had anything specific to add and he did not.

See note at bottom for an update.

DLC is a network protocol that you have to add in the network properties. If you have two network cards, you would want to add it to the card that handles your internal network. From what I remember, I just added the protocol to my win2k system, not a server. I think I then went to "add printers" and added it as a network printer. There may have been a choice when I was installing the printer to choose a port or protocol, I don't remember for sure. However it went, I was able to print from that system, and when I shared the printer through that computer, other systems were able to print to it.

When I talked with my friend he basically said the same thing, except he did it on his server at work. He added the protocol, was then able to find the printer on the network, and then pulled the printer share from the server to the clients, so they could print to it.

Additional note...I went to my server and went to the start menu, then help. In the help menu, I clicked the index tab, and typed in DLC in the keyword. It talks about what the protocol is, and also explains how to add an hp network port for printing using DLC. It also says that you need to have the protocol installed before you can add the printer port using DLC.

Hope this helps.

 

[thermite88]

Did you try the HP SUPPORT PAGE yet?

Also check Install Network Printer Wizard.

 

[Viper GTS]

Configure the IP via the control panel (MIO Menu).

To telnet into it you need to use port 9100.

If you can ping the printer it's extremely unlikely that the jetdirect is bad.

If you're running XP or 2K just add a standard TCP/IP port pointing to the IP & it should work fine.

BTW, redbeard, I have a 4+ here running basically the same card, & it prints fine via TCP/IP from windows.

If you still need step by step help, PM me with your phone number. I walk people through this stuff all the time, I can do it in my sleep.

Viper GTS

 

[redbeard1]

The important thing is that tcp/ip is not supported in a windows enviroment, only in a unix server network.

You can set the ip, and you can ping it all day, but you won't get it to print. The link I supplied earlier to HP shows what network protocols that particular model jetdirect supports, and it only works with DLC in an NT based system.

 

[Viper GTS]

Originally posted by: redbeard1

The important thing is that tcp/ip is not supported in a windows enviroment, only in a unix server network.

You can set the ip, and you can ping it all day, but you won't get it to print. The link I supplied earlier to HP shows what network protocols that particular model jetdirect supports, and it only works with DLC in an NT based system.

While I don't specifically support jetdirect devices (I support the printer itself), the card I have & the card he has are in the same product line. They likely have the same firmware (I'm looking for verification on that). Most likely it will work, from what he's described so far he hasn't actually tried to print to it - He hasn't een successfully installed it (which has nothing to do with it's compatibility).

For example, look here.

I'm searching internal HP documentation right now for more info.

I just found this document for my card (J2556B) that also only lists DLC/LLC for NT based OS's. The document(s) is obviously outdated.

Viper GTS

 

[redbeard1]

How did it go?

 

[Carp1812]

Finally found time to mess with it last night. I tried installing the DLC/LLC protocol first- discovered it's not included in WinXP. I found a download from Micro$oft that isn't officially supported and installed that protocol. No luck with the printer. It wouldn't allow me to use the protocol even after rebooting. I installed the DLC/LLC protocol on my Win2k server box and rebooted and it wouldn't use the protocol either. I was able to successfully telnet into the printer though and set up a static IP. After that, I added a standard tcp/ip printer port, specified the model of the printer and used the default drivers in Win2k server and WinXP. Works like a champ! Thanks all for your help.

 

[kpb]

Originally posted by: redbeard1

The important thing is that tcp/ip is not supported in a windows enviroment, only in a unix server network.

You can set the ip, and you can ping it all day, but you won't get it to print. The link I supplied earlier to HP shows what network protocols that particular model jetdirect supports, and it only works with DLC in an NT based system.

Well I can't really speak for the windows side of things but I did mac support for these printers at one point and tcpip printing most definitely did work from the macs and I'd be extremely suprised if the windows side of things didn't support it too.