I bought a used HP 4Si and added an old HP Jetdirect card that I had.
Cold reset the jetdirect card. Added the printer thru NWAdmin. Using
HP Web Jetadmin to administer the printer. Selected the rprinter vs.
bindery selection in the Web Jetadmin configuration. The Web admin
shows the printer online, but the pserver screen on the server says
the printer is not connected. A Self Test page printout shows "Novell
Status:Not configured". This one is driving me nuts. Any ideas? |
Request for Question Clarification by
hibiscus-ga
on
05 Dec 2002 15:50 PST
An easy question for you. Have you downed and restarted the Novell
print server service? As I recall you can install the JetDirect and
view it under NWAdmin and connect to it through JetAdmin, and it still
won't be connected to the Novell tree properly until you restart the
print server.
This used to drive me nuts when I installed printers at a large
organization I worked for because the client would get the new printer
on their desk and they wouldn't be able to use it until the next day
because the print server couldn't be restarted during the day.
Let me know if that doesn't work. We'll try other things from there.
|
Clarification of Question by
rcwally-ga
on
06 Dec 2002 07:19 PST
Yes, I have downed the print server many times. Unfortunately for me,
I am so used to adding the new printers, which just load as their own
print servers, that I forget what to do when I have to add one this
way. I went into NWAdmin first and created the printer, print queue
and added it to the correct print server. Then I Cold Reset the
Jetdirect card. I then went into Web JetAdmin to change the
configuration and add the IP address, Netmask and Gateway. Jet Admin
sees the printer and says it is online, but Pserver on my server says
the printer is not connected. I have even changed the printer number
to several different numbers. I know I am missing something little,
but I just can't think of what it is. Thanks!
|
Request for Question Clarification by
hibiscus-ga
on
07 Dec 2002 09:38 PST
Hmm.. Okay. Another question for you. In NWAdmin, have you assigned
the print server context? Select the printer, click configure, click
Netware Directory Services and select the tree name in the Tree Name
box. Then type in the NDS context in the Print Server Context box.
JetAdmin also needs to know which queues are being serviced, so click
Queues and then see if it's connected to the right queue. If not,
click Change and select a queue. You could also try creating the
queue right from within JetAdmin and see if that makes your server
happier.
I'm just going through the basic steps to this, so you may very well
have already done this a thousand times, in which case I appologize.
But it's often some little thing that gets overlooked that causes all
the problems.
|
