jetdirect?

[pinhead]

2003SBS server just put on the network. Laserjet 5m with a 2552b jetdirect card that worked fine with the old 2000sbs server. Can run webjetadmin and it sees the printer, can run download manager and it saw the printer and uploaded the firmware. BUT, the install network printer wizard cannot find this printer to install it. Any ideas? I've even tried to use add a tcp/ip port ofr it and it doesn't work..... any help is gladly taken

 

[EatSpam]

First of all, don't use HP's jetdirect software.

Second, you are using DHCP, right? Create a DHCP reservation using the MAC address of the print server so that the print server gets an static IP. Assign a DNS name if you like. Otherwise, you'll have to find some way of assigning the print server a static IP.

Third, use the standard "Add printer wizard" on the server. Tell it that its a local printer and uncheck "Detect printer" or whatever. On the next screen, create a new TCP/IP port. Give it the static IP or DNS name you created in step two. Leave the port name alone or give it a descriptive name. On the next screen, pick the printer or install drivers like normal. Print a test page.

Done.

 

[pinhead]

It has a static ip, it is reserved on the router, and my last statement was what you just mentioned. I tried the tcp/ip add a port from the local add a printer and it still wouldn't take. But I can still print from the old sbs server to it, so I know it is working fine. It's just plain strange.

 

[EatSpam]

Can you ping the Jetdirect card from the new server?

 

[pinhead]

Won't ping from the server, and the firewall/ics isn't installed so that isn't blocking it. One thing I haven't tried is to do the add a printer from a workstation to see if it works with the ip it has. I don't want to run it from a workstation, but I do want to verify I can at least get it working.

 

[EatSpam]

Originally posted by: pinhead
Won't ping from the server, and the firewall/ics isn't installed so that isn't blocking it. One thing I haven't tried is to do the add a printer from a workstation to see if it works with the ip it has. I don't want to run it from a workstation, but I do want to verify I can at least get it working.

There's the problem. Can the new server ping the old server or any of the workstations?

 

[pinhead]

Yep, all the workstations are attached to the new server which is running as an app, exchange and file server.

 

[EatSpam]

Can you ping the print server from the workstations?

What is the IP address and subnet of the print server? the new SBS server? the old SBS server?

 

[cmetz]

pinhead, telnet to the jetdirect card and use the cheezy text interface to configure it, and use it as a raw TCP/IP printer. HP's software sucks.

(would IPP work better these days? I don't do Windows, so I really don't know... I've always used raw and PostScript...)

 

[nweaver]

webjetadmin is good s/w (somewhat buggy, but most s/w is, lol). Try to manage a couple hundred printers some time, and you will find a tool like WebJetAdmin to be very helpfull. It's like a domain controller for HP Printers

also, if you can't ping, you can't print, that makes sense. Troubleshoot this as a TCP/IP problem. I would check the broadcast address for both. If you are running on a subneted network (non 255 in the subnet mask) it can wreak havoc on arps. I just had this problem with BSD and a Netapps NAS

 

[EatSpam]

Originally posted by: cmetz
pinhead, telnet to the jetdirect card and use the cheezy text interface to configure it, and use it as a raw TCP/IP printer. HP's software sucks.

(would IPP work better these days? I don't do Windows, so I really don't know... I've always used raw and PostScript...)

Won't help... his problem is a TCP/IP networking problem. The printing issue is just a symptom.

 

[pinhead]

when I got in this morning I wiped the ip from the jetdirect card and put a new one in it, the old one was 192.168.100.10, and the new one I just made 192.168.100.20 and after that it worked going through the add a printer wizard and using the add a tcp/ip port. the old ip was valid and some of the hp software was seeing it, just didn't work for some reason. Thanks for all the help, still not sure what was wrong though....