Pathworks printer shares

[Paul Jerrom]

Howdy,

Me again.

We have had several problems with setting up a printer share. We define the TCP port using Multinet, create the printer, then define the share in Advanced Server. When we try to map to it from a Windows print server (which we have done successfully about 100 times for other printers) the Pathworks License manager process starts to eat cpu, about 50%, and the queue manager eats another 25%. This usage continues until we stop the attempt to map the printer share. When we change the name of the printer, with all other parameters the same, the share maps no problems.
We have a second printer which we have set up, when we try to map we get the error : "Could not connect to the printer. You either entered a printer name that is incorrect or specified a printer no longer connected to the server" - despite having browsed to select the printer. When we change the printer name, we get the cpu loop error described above.
Has anyone seen/solved similar problems?
Versions are VMS 7.3-2, AS 7.3eco4, printservers are W2000 sp4.

Have fun
PJ

[Doug Phillips]

Hi Paul,

Maybe a bit more information would help. How is the printer attached and how is it available to the network? JetDirect (or equiv)? Local on the Alpha or W2K? TELNET? LPD?

If by "define the TCP port using Multinet"? you mean via MULTINET CONFIG/PRINTER, what does PRINTER-CONFIG>SHOW say?

In Pathworks (AdvServer) the printer share name should be the same as the queue name. Are they?

What printer "names" do you change to make things work or fail and where do you change them?

Do you see the Alpha and the printer share from Windows when you browse the network? Can you open other shares on the Alpha from Windows?

Why do you say "printservers are W2000"? Are these Windows2000 servers or "printservers"?

Will the printer be used by both VMS and Windows applications? Can you print to the printer from VMS?

How do you "map" the printers from Windows?
If you're using a JetDirect type of printer, can you add the printer to windows directly (local printer, TCP/IP port) rather than "mapping" the PW share?

Do you have any other printers that are working that you can compare their setup to this one?

[Paul Jerrom]

Howdy, and thanks for answering, Doug.

>>How is the printer attached and how is it available to the network? JetDirect (or equiv)? Local on the Alpha or W2K? TELNET? LPD?
In this case it is an IP printer in a remote office. It is an Office Jet k550.

>>If by "define the TCP port using Multinet"? you mean via MULTINET CONFIG/PRINTER, what does PRINTER-CONFIG>SHOW say?

PRINTER-CONFIG>show nnparts
Queue Name Destination Remote Queue Name
---------- --------------- -----------------
NNPARTS xx.xx.68.20 TCP port 9100
Queue Owner = System
Queue Description = Office Jet k550
Burst Page Option is set to NONE
Trailer Page Option is set to NONE
Telnet Options Processing will be suppressed

>>In Pathworks (AdvServer) the printer share name should be the same as the queue name. Are they?
Yes.

>>What printer "names" do you change to make things work or fail and where do you change them?
NNPC gives the cpu loop, NNPARTS works.

>>Do you see the Alpha and the printer share from Windows when you browse the network?
Yes

>>Can you open other shares on the Alpha from Windows?
Yes. About 100 of them.

>>Why do you say "printservers are W2000"? Are these Windows2000 servers or "printservers"?
Windows 2000 servers

>>Will the printer be used by both VMS and Windows applications?
Yes.

>>Can you print to the printer from VMS?
Yes.

>>How do you "map" the printers from Windows?
Browse to it, then select it.

>>If you're using a JetDirect type of printer, can you add the printer to windows directly (local printer, TCP/IP port) rather than "mapping" the PW share?
Yes.

>>Do you have any other printers that are working that you can compare their setup to this one?
Yes, about 100.

Cheers,
PJ

[Doug Phillips]

If you can print to the printer from VMS and can add the printer in windows and print to it, I don't understand the problem.

You might have a permission problem with mapping to the PW share (on the share or the queue). Or, maybe the "bad" name was previously used on the network. It does sounds like a name conflict someplace.

I also don't see how License Manager gets involved, unless you mean PWRK$LICENSE_R or one of the PWRK$LM... processes where the LM stands for Lan Manager.

I presume you've looked at the windows and PW event logs?

Maybe if we keep kicking the post up to the top, one of the HP PW gurus will jump in.

[Paul Jerrom]

Thanks Doug, I'll check for name clashes, although generally the first two letters (in this case NN) denote the office or location, and this is for a new location that has opened.

My apologies, I meant the LM process rather than license manager.

I'll hold my breath for a Pathworks guru - I've had an open call out with HP for nearly 2 weeks now - although i suspect all the exprtise is in AT&T.

Have fun,
PJ