Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

Terry,

> Could this have something to do with packet size? I've noticed that some of
> my older JetDirect devices can't handle a packet size of 1500 bytes. Does
> iPrint ever try to send packets of that size?
>


Engineering is still investigating the issue. If you have a printer for
which you can give us a public IP address there isn't a need to go through
these traces. Email the IP address to me directly at probello@novell.com and
I will get with the engineer. He will do the traces himself and print a
couple of test pages to see if he can debug this issue.

Pam


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

Unfortunately, we don't publish our printers. They're all 10.x.x.x
addresses and I don't have any free public addresses to map to one of them.

> Terry,
>
> > Could this have something to do with packet size? I've noticed that some of
> > my older JetDirect devices can't handle a packet size of 1500 bytes. Does
> > iPrint ever try to send packets of that size?
> >

>
> Engineering is still investigating the issue. If you have a printer for
> which you can give us a public IP address there isn't a need to go through
> these traces. Email the IP address to me directly at probello@novell.com

and
> I will get with the engineer. He will do the traces himself and print a
> couple of test pages to see if he can debug this issue.
>
> Pam
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

None of our old LaserJet 4's will work. And I have one LaserJet 4250TN (out
of many) that goes into LPR Com Fail at least once a day. I have not been
able to find any firmware updates for the LaserJet 4's but I did update the
4250 to the latest everthing (printer and jd) and still have the problem.

> On Jan 31, 10:38 pm, "Doyle collings" <dcolli...@loganutah.org> wrote:
>
> > The new patch does not work. I still have two Canon iR5000, two hp

laserjet
> > 4, three hp laserjet 5M, three hp laserjet 4000, and two external

jetdirects
> > that have lpr communication failing.

>
>
> Just curious. Do you have any HP LJ4s working? Likewise do you have
> LJ5Ms working?
>
> I can guarantee you that I did.....with no problems specific to that
> model. We have over 800 printers on campus and quite a number of
> those models. If some work and some don't have you check what levels
> of firmware the jetdirect cards are running?
>
> Just a thought.
>
> Regards
> IanB
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

We have found a rather unusual behavior in various NIC cards in various
printers. Older NIC cards in printers dealing with LPR are rather picky
about the ports and sockets being used. Newer model printers don't seem
to have as much of a problem.

The issue is that the Gateway can "ping" the printer, the Gateway can
"snmp" the printer, and the Gateway can even open a socket to the printer
for LPR communication. However when data is sent via the port and socket
opened, the printer sends back an error to the Gateway that prohibits the
Gateway from sending more data, and hence the LPR communication failure.
We have duplicated this behavior in older JetDirect cards in HP 5000 printers.

As far as we know, running RAW instead of LPR seems to work. RAW does not
have this limiting behavior that we see with LPR. So, in cases that allow
the change of protocol from LPR to RAW, please try RAW and see what
happens. We have worked on a fix for the and hopefully will have it out
quick.

Changing the protocol from LPR to RAW requires that the gateway load string
be modified. The easiest way to do this is to create a "dummy printer"
using the RAW protocol instead of the LPR protocol. Look at the gateway
load string and compare this against an existing LPR configured printer,
then make the appropriate changes. Remember that once you change the
gateway load string, the printer agent must be restarted to take effect.
Shutdown the printer agent and start it back up.

Please continue the feedback as to whether this helps.

Thank you!!


> We understand this has been an extremely rough update, and could attempt
> to explain the reasons for the changes, however, customers just want it
> to work. Currently NTS has a new gateway that has been tested and does
> work (a lot better). This should be distributed via the support download
> very soon.
> > What the hell has Novell done to iPrint in SP6 for NW6.5?!
> >
> > Ever since I installed SP6 on my file/print server I have been having
> > nothing but problems with my printers. I keep getting random printers

> that
> > stop printing and when I check the iPrint Manager health it says LPR
> > Communications Failure.
> >
> > I did some searching in the knowledge base and found IPRNTNW65SP6C.EXE

> but
> > that hasn't helped either.
> >
> > You would think that something this disruptive would have come out in

> beta.
> >

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Don't know if this helps any, but the patch helped me, along with a DS 8379 ftf and a winsock beta. My IR 5000 working but my HP4's still have issues.

I did some troubleshooting on my network because of someone saying that the packet segment may be too large. I set in my cisco routers, ip tcp mss=1436 to see if there are issues crossing vlan's and routers. Call it dumb luck but one printer started working again. I backed off the setting and it stopped working.

Tom


>>> <iprintrox@iprint.novell.com> 1/31/2007 11:24 AM >>>

We understand this has been an extremely rough update, and could attempt
to explain the reasons for the changes, however, customers just want it
to work. Currently NTS has a new gateway that has been tested and does
work (a lot better). This should be distributed via the support download
very soon.
> What the hell has Novell done to iPrint in SP6 for NW6.5?!
>
> Ever since I installed SP6 on my file/print server I have been having
> nothing but problems with my printers. I keep getting random printers

that
> stop printing and when I check the iPrint Manager health it says LPR
> Communications Failure.
>
> I did some searching in the knowledge base and found IPRNTNW65SP6C.EXE

but
> that hasn't helped either.
>
> You would think that something this disruptive would have come out in

beta.
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Changing from LPR to RAW does not help (please see our open Incident SR # 10313864243).

Why does NDPSGW.NLM v 3.xx not have these problems?

Why does LPR2NDPS.NLM v 3.xx not have these LPR problems (if you print LPR jobs with copies > 1).

What did do change in version 4.x ?


Regards
UVEX Safetygroup
Andreas Ebert
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


I came up with an interim resolution for this issue. I recreated the
printer object and chose the HP Printer Gateway. Since the
"hard-impact" Epson printer was attached to an external HP JetDirect, I
elected to go this route. The printer was originally created by using
the Novell Printer Gateway services.

The HP Gateway Printer Gateway service on the server has more
granularity by allowing you to define a gateway time-out. In order for
this customer to print a 325 page statement report, I had to define the
time-out parameter from a setting of 3 to 1800.

They have been good-to-go ever since.


--
Tebos
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.