Problem installing new HP printer Driver

[LD71]

Hi,

I just purchased an HP9800 printer. When I go to add the printer drivers to the broker I get the following error: "NWADMN32.exe has generated errors and will be closed by windows. You will need to restart the program. An error log is being genereted."

I have no other problems adding other printers drivers...just this one. I contacted HP and was told they only supported windows based problems and wished me luck trying to find a driver that worked. (thanks for nothing!)

So, to get around the problem I decided to print the old way with a print server, que and printer...however, I can't find where to tell the jet direct printer what que to use or where to tell nwadmin what IP address to use. I have HPJetAdmin software, but it will not let me modify the changes to pick a que. I also have HPWebAdmin, but it will not pull up that printer.

I'm Striking out on all ends...does anyone have any suggestions for me?

Thanks!
Lori

 

[marvhuffaker]

Queue based printing doesn't use IP. Only IPX.

You might have better luck setting up the driver with NDPS using iManager. NWADMIN isn't very stable when adding print drivers, and iManager will give you better control of XP drivers anyway. Assumming you're using iManager 2.0x (NetWare 6.5).

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LD71]

Thanks for your quick response. We don't currenlty use iManager. I have a CNE that we hired to come in and he has not set up iManager for us...he has only shown me Console1 and NWAdmin...

Is this something I can set up fairly easily or is there a file I can go find to launch iManager?

Also, we are running Novell 6.

Thanks again,
Lori

 

[marvhuffaker]

Ok, iManager in Netware 6.0 is pretty much useless anyway. But I'm confused as to how you are connecting this server to your network anyway.

How do you have the HP9800 printer attached to the network? I looked at the specs and it only has a USB and LPT port, no RJ-45. Also what version of Windows are your workstations running and what version of the Novell client do you have installed?



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LD71]

We have an external HP Jet Direct card on it. It is a Jet Direct EXPlus. I know it's an old one...but we are using a few others here of the same age and NDPS doesn't seem to care.

Our workstations are mostly windows '98 running 3.32 and XP running 4.91.

The only thing me and my network guy saw that could be a problem is that the driver for this is a PCL3.

Thanks,
Lori

 

[marvhuffaker]

Is it the Win98 or the WinXP driver that crashes NWADMIN? I just used NWADMIN to install the XP driver into the broker and it went just fine. I don't think the problem is PCL3.. a problem stemming from that would most likely surface elsewhere.

However, you should know that to get full support and control of XP drivers, you need iManager 2.0.x. NWADMIN doesn't differentiate between w2K and XP, and it can cause some confusion. Also, the Novell client 4.9x and higher will attempt to download the OS specific drivers whereas earlier versions of the client only knew about W2K drivers.

I would also recommend running NWADMN32.EXE with the /DisableTLSMGR switch. It's actually used to fix a different problem when adding drivers to the broker, but it won't hurt anything to use it in your case.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LawnBoy]

Personally I prefer NWADMIN over iManager for configuring NDPS. Are you starting NWAdmin with the '/disabletlsmgr' switch? I.E.

\\mylovelyserver\sys:\PUBLIC\WIN32\nwadmn32.exe /disabletlsmgr

 

[LawnBoy]

Marvin beat me to the punch.

 

[LD71]

Thank you everyone for replying. It crashes out when installing both the 98 & XP drivers. My shortcut for NWAdmins is \\Jobs_plus\SYS\Public\Win32\nwadmn32.exe...so i will try running it with the switch and see what happens.

I will repost with my findings once I have tried it.

Thanks again,
Lori

 

[marvhuffaker]

Just another thought... You might also have better luck is your shortcut is referencing a specific drive letter instead of a UNC path. NWADMIN was developed before UNC was widely adopted.

So map F: to JOBS_PLUS\SYS and make the shortcut F:\PUBLIC\WIN32\NWADMN32.EXE /DISABLETLSMGR

Marvin



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LD71]

Well...I maped a drive and created the shortcut with the switch...tried to load the printer drivers in the broker and got the same error message.

Am I on the most current version of NWAdmin?

Version 5.1.9f Requestor version: 4.83.0

Thanks...

Lori

 

[terry712]

what version are you using - in terms of netware?

i'm not a great imanage fan but when it comes to printing with xp then it's a must

the newer hp's are getting quite fussy about differentiate between w2K and XP - i notice th pcl3 appearing on a few

 

[marvhuffaker]

The 4.83.0 requester version you mention is the Novell Client version. You may want to try to do it on a workstation with Client 4.91.

Your NWadmin version is the most recent. But check your snapins.. The file at \public\win32\snapins\NDPSW32.DLL should be dated 8/23/2002.

Grasping at straws here, it should work. But you may have to try it on a couple different workstations until you find one that works. You also may want to run it from a different server to avoid any bulk from other snapins. Or you could install the standalone version to your workstation and run a completely clean copy.

Also.. There is a file called NDPS.INI under WIN32\SNAPINS\INI... You may want to use this configuration if yours is different. Maybe you are loading extra snapins that are causing problems. This is what mine looks like:

[Snapin Configuration]
NDPS=Ndpsw32.dll,Xvwnds32.dll,Epsnapin.dll








Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LD71]

I got it! Thanks for all your help. I am running a windows 2000 machine...and realized that I had not updated mine to the 4.91 client...as soon as I did that it worked fine.

Thanks you so much for all your help. It's nice to know that there are stiill people out there who use Novell...

Lori