Enchantermon on 31/8/2009 at 15:50
Quote Posted by baeuchlein
Concerning finding the manual, I was lucky when entering search terms in Google. I did not even check the HP homepage for anything.
That's the thing...I've been to the HP website several times looking for drivers and such...never even noticed the manual.
Quote Posted by baeuchlein
It's on page 63 ("5-63", meaning chapter 5, page 63) of "HP Jetdirect Print Server 170X Installation and Configuration". They call it "Selecting a Configuration page PDL". It is hidden very well in the Troubleshooting chapter. I guess it's seeing a completely dark visibility gem from where it is located.:cheeky:
Nice. :thumb:
I see it now, thanks.
I'll check this out on Tuesday (I'm only there Tuesdays and Thursdays, btw) and see if I can do anything with the port. The Jetdirect software was dumped by HP a while ago, which is a bummer.
I have not tried going through a web browser; never occurred to me to be honest, but I'll try that as well as seeing what happens when I sever the connection with the printer. Thanks again for your help.
Quote Posted by baeuchlein
This possibly refers to two printers and one CUPS software.
Yeah, I know about CUPS (configured it once on a Fedora VM). I also know (
http://en.wikipedia.org/wiki/Two_girls_one_cup) what TBE was attempting to get at. :nono:
Enchantermon on 1/9/2009 at 17:55
Okay...there was no way either through telnet or through the web interface to configure the parallel port. No option even mentioned it. Running the installer with the parallel cable disconnected only produced an "Unknown" device (usually instead of "Unknown" it shows the printer's name), no extra configuration of any sort. I disabled IPX/SPX. DLC/LLC is enabled. No raw ports are configured but I imagine it wouldn't need them. No access list is in use. The IP address is in the proper network.
I also tried the process in the manual of changing the configuration page's PDL, but the process they list doesn't work. It says I should hold down the test button and the lights will turn solid, but they don't. I know the test button works, though, because I used it to reset the print server to its default settings.
Also, I was going to test with my printer, but it doesn't have a parallel port, so I can't until my dad comes up at the end of the week with our parallel-to-USB adapter. The only other available printer is the exact same model, so it's likely to have the same problem.
I don't get it. I'm on the verge of recommending they find a different print server; something more modern, at least something that can run USB. The only problem with that is that it may not arrive in time for me to install it.
Any more thoughts? I greatly appreciate all of the help you guys have provided.
baeuchlein on 3/9/2009 at 14:20
Well, after thinking for about two days about this problem, I must say I don't have many ideas left.
The main problem at this time is this automatic installation program (I think), which basically tells you, "hey, I can do this all alone, you don't have to think or even know about all this stuff", yet not only does a lousy job, but does not give you any information about what's wrong here either. That's why I hate automatic things that can neither be turned off nor talk about what's wrong anyway.:mad:
Latest idea: Install the server with a disconnected printer again, and when all is done, connect the printer again and then try to print a test/configuration page again. If you're lucky, the print server has been set to "unknown printer" and "ASCII text output only", and can finally print out what has been detected and/or configured.
If this does not work, wait for this parallel-to-USB adapter, sent a prayer to whatever god you may believe in, and try another printer with this adapter. Unless we get more information about what the heck is going on (and configured) inside the print server, I don't think anything else can be done.
If this all takes too long for the printing community out there, you could - at least as a temporary solution - connect the printer to one of the computers directly and let them all print to this network share (or whatever Windows calls it in English). This computer would have to be on all the time, then, but it may be acceptable as a temporary solution.
It is possible, by the way, that the print server acts different than what you find in the manual. I'm thinking about the test button, which apparently neither prints a test/configuration page nor lets you choose the "printer language". This could be a result of an older firmware inside the print server. The HP internet pages at least mentioned that you could download another firmware, so maybe the print server which bothers you has a very old firmware revision that is not covered in this manual.
All you have to do to find out is print that configuration page...:ebil:
Maybe this web interface mentions the firmware somewhere.
mudi on 3/9/2009 at 17:18
I think the old JetDirects used a lpr-style IP printing... have you tried adding the printer as a "Local Printer" using a New Port, set the IP address to the IP address of the print server and select a driver manually?
Far shot and probably already tried... sorry...
Enchantermon on 4/9/2009 at 04:12
Well, I didn't work with the print server today because I have other tasks I need to get done, so I want to make sure I have enough time to complete them. If I end up with spare time later on, I will try the latest suggestions.
Mudi, can you be more specific? I'm not sure I quite understand what you're saying.
Although it may not matter, because I cannot set an IP address on the printer.
mudi on 4/9/2009 at 05:14
Oh OK then. If you had an IP address for sure, you can manually set it up in Windows XP by choosing Local Printer instead of Network printer (I know I know, just stay with me...), when it asks you what port it is connected to you pick "New Port", create an IP Printer port and specify the IP address.
But if you don't have an IP, then that's not gonna get you very far...
baeuchlein on 8/9/2009 at 09:54
But the print server has an IP address. Would it not make sense to use that address for the "printer"? At least it's worth a try, I guess.
Enchantermon on 9/9/2009 at 02:46
Erm...well, I suppose I could give that a shot.
I actually have the print server with me now; I'm taking it to the techs at school tomorrow to see if they can do anything with it. I was going to test it at home using my printer, but of course the parallel-to-USB adapter I was brought is for the opposite end of the connection than what I thought it was for, and since I don't have a parallel cable handy, I can't use it. But I'll take it in tomorrow and see if I can get some answers.
One thing, though: the print server is connected to the rest of the computers over a switch. I would think creating a Local Printer wouldn't work because the connection is over a network. Or am I wrong?
mudi on 9/9/2009 at 04:50
Though the terminology is all wrong, it's just the way it is in Windows XP.
You aren't really creating a Local Printer, you're creating a Network Port printer that Windows XP for some reason beyond logic made only accessible behind the "Local Printer" option.
Trust me, as illogical as it sounds, I've kickstarted a few old print servers into working this way.
Enchantermon on 9/9/2009 at 08:38
:weird:
Well, it is Microsoft...I'll give it a shot. Thanks.
