Netware Printer Question 2

[wardog25]

We had a printer just stop working today. Stuff would just pile up in the print queue. The printer is fine and is still attached to the network. The printer is actually hooked to an HP Jetdirect 170X.

Anyway, i checked the Netware 5 server which has the print server on it and it had the print server loaded, but says the printer is not connected. Now I KNOW that the printer is connected because I can see the network connection light flashing on both the jetdirect and on the hub where the jetdirect is connected.

Now, just to try, I recreated the printer, the print server, and the print queue in NWadmin, and then reloaded it using the command PSERVER on the Netware server. It loads it all fine, but still says it isn't connected. What's more, on every other printer that is loaded on the server, it has the Network address listed. but on this one (neither the old or the new one i created) there is no network address listed, it says address unknown.

Now.....being the Netware newbie that I am, I have no idea how to put in the Network address. I know the IPX address of that Jetdirect, but that is the ONLY value that NWadmin won't let me change. So how do I change it so that it knows the address of the jetdirect that the print queue points to? It won't let me change it in NWadmin, and none of the utilities I know on the Netware server allow me to enter it either.

 

[terry712]

if it's a jetdirect box then you dont need pserver running on the server - thats what the jetdirect box is for

best way except swiching to ndps is
delete you printer /q and ps server object
reset jetd to factory defaults

then in nwadmin to quick setup and create the 3 objects
open the hpjetadmin stuff - find new device and assoc to nds objects

and hey presto

but seriously look at ndps and ip - soooo much easier

 

[wardog25]

Thanks, I'll give that a try. (on monday, since i won't be at work this weekend)

I did notice that the jetadmin stuff seems pretty ancient. The version we have is like 4 years old and the software is old enough that HP doesn't keep it on their website anymore. Once again, being a netware newbie, i don't know the alternatives. How difficult is it to set up ndps and ip?

 

[terry712]

simple

which version of netware 5 or 5.1.

basically all you do for ndps is - install through nwconfig (may be on already)
there are lots of tids on it but it means you can make them ipp as well so just give people a web page and they can download or pick a printer or you can force it down to them or take them away - it does all the drivers as well

so if you have a guy that strolls about and uses a 98 one minute then an nt the next or a w2k - it doesnt matter it just squirts the relevant printer and driver to him

no more q's etc - all you do on the jetd side is give it an address

 

[marvhuffaker]

While NDPS is much easier to manage, I don't agree that it's simple to install. At least not on NW 5.x. With all the patching and drivers you have to put on there, and then setting up the drivers, etc... it can be a hairy process for someone that doesn't have experience with it. For someone with Queue based printing experience only, it could be overwhelming trying to understand the concepts and processes necessary for a successful implementation.

For NW 5, you also have to make sure you have installed the latest NetWare service pack, and apply all Novell NDPS patches.

Additionaly, if you want to use the HP gateway, you need to install the latest version from HP. Otherwise you won't be able to use IP. The HP gateway that ships with NW 5.0 only supports IPX.

If you do undertake the process, take your time and do it on the weekend when nobody is around.

Here is a simplfied step by step of what needs to be done:

1) Install NDPS on server(If not already installed)
1) Patch server with latest NetWare SP
2) Patch server with Latest NDPS patch
3) Update BIOS on all printers, and configure with IP, if not already done.
4) Install necessary 3rd party gateways.
5) Create NDPS Broker in NDS, load on server
6) Create NDPS Manager in NDS, load on server
7) Check for printer drivers in broker and add as required.
8) Create NDPS Printers in NDS and configure drivers
9) Configure containers (NDS Context's) for automated deployment of printers.

10)Then you have to consider.. do you need to support legacy print queues? or can you dump them all and use straight NDPS. Associate printers with Legacy queues, if necessary. (I'd recommend that you don't do this, unless you have applications that specifically require a queue.)

11) Install NDPS component of Novell client on workstations. Troubleshoot lockups on workstation (in some cases).
12) Test/Troubleshoot problems/retest.

After all said and done..

- Remove Queues from NDS if you aren't using them in compatibilty mode
- Remove print server / legacy printers from NDS
- Remove IPX info from Printer configuration pages (in printer bios)
- Remove Queue based printers from workstations.

Not trying to scare you, but you've got to be realistic. It doesn't just happen by magic.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[dsimpaired]

Nice reply Mr. Huffaker, that is one of the most complete and concise posts I have seen in the forums yet. Good info!

 

[wardog25]

Ok, this is annoying. I did what you said with recreating the objects in nwadmin and all that, but jetadmin isn't working right. It sees the jetdirect, and lets me try to create a new printer object with it, but when i do and I refresh, it is never there. Instead the IPX address of that jetdirect just reappears in the "create new object" list.

So basically i have a print server object in NWadmin that is tied to nothing. Is there any way to tell it the IPX address to print to through Novell?

 

[wardog25]

wait, never mind. Jetadmins settings were just hosed up for some reason. I got it to work finally.

Thanks for the help. I'll think about the ndps thing. Not sure if I'm ready to mess with that yet though. =)

 

[terry712]

glad to here

jetadmin is funny - once it works you never have to go near it again
the bad news is the new version (web) of jet admin is worse

ndps is definately the way to go

i'm totally netware 6 thoughj and ndps is alot better with this

 

[TheLad]

If you are using NDPS, you don't have to bother with JetAdmin. Providing your JetDirect card has a DHCP address initially, you can access the JetDirect card via the Internet Browser and then set a static IP address as required. There are no need for Printer Print Queue and Print Server NDS objects so effectively you are cutting the number of printer objects from 3 to one (excluding NDPS Manager and Broker).

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[nblinstrub]

amen to TheLad: WebJetadmin for firmware updates only. A telnet session to the DHCP address and following the menus is another quick way to configure JetDirects.