Anonymous_User Absent Member.
Absent Member.

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

Tom Hafemann wrote:

>So, help me understand this. I have to open a $650 incident to tell Novell
>that printing doesn't work?


Well, if it proves to be a defect, then Novell will reverse your charge.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

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

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!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Our problems are occuring on selected printers:
Canon ir5000, hp laserjet 4, hp lasterjet 5, and older external jetdirects.
We have about 13 Canon imagerunner printers most of them still work. There
are even some ir5000's that still work.

>>> On 1/31/2007 at 2:41 AM, in message

<BvZvh.11833$Sz4.8199@prv-forum2.provo.novell.com>,
<alan.coutts@nospam.miller.co.uk> wrote:
> It's interesting that you have this problem with heavy duty Canon
> printers. Out of the 50 printers that our manager services, the 2 that
> don't work are Canon (iR500 & 2800). Should we be trying to compile a
> list of printers that don't work to see if there is any pattern? Would
> this be helpfull for Novell?
>
> I'm unable to go back to the SP5 module as our iPrint is clustered.
> I've
> service packed 2 of our 4 nodes and if I try and run iPrint on an SP5
> node
> now, it won't load. I presume the upgrade has modified the ndps
> database
> in some way and there is no going back.
>
> For the time being, I thinnk I'll create another manager on a SP5 server
>
> to service these two broken printers. I have an SR open with Novell and
>
> our PSE is doing all he can to find any internal updates.
>
>
>> In jest,
>>
>> Meanwhile, whilst we wait for the fix, what do I do with the 40 pairs of


>
> =
>> shoes stuck up in my nether regions put there by my end users? 🙂 I

> have =
>> been going home with icepacks tied around my bum. 🙂
>>
>> Seriously though, it has been painful through this. I built a

> completely =
>> new server and installed iPrint on it, sp5, to handle the printers that

> do =
>> not work. I have only 6 of them, but they were our high duty Canon and

> =
>> newer HP printers.
>>
>> Sincerely,
>>
>> Tom
>>
>>
>> >>> Marcel Cox<cimetmc@myrealbox.com> 1/30/2007 2:31 PM >>>

>> terry@nomail.com wrote:
>>
>> >Is there any way to be emailed when the new Gateway is ready AND

> working?
>>
>> Well, what you can do is the following:
>>
>> Add the following wiki page on your watch list (you need to login with =
>> a=20
>> Novell web account to put the article on your watch list):
>>
>> http://wiki.novell.com/index.php/Nw65sp6
>>
>> Then configure your user to be sent an email when the article changes.
>>
>> I will promise I will do my best to update the page as soon as there

> is=20
>> new information.
>> Of course, you will also get emails for other updates on that page

> not=20
>> related to iPrint.
>>
>> --=20
>> Marcel Cox (using XanaNews 1.18.1.6)
>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

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

Hey There,

SAME HERE. Our Canon IR 5000 no workie. A few HP4's not working. Canon IR 5800 color, no workie.

I have found that rebooting the server will let them work for about 2 hours, and then die.

Tom


>>> Doyle collings<dcollings@loganutah.org> 1/31/2007 12:21 PM >>>

Our problems are occuring on selected printers:
Canon ir5000, hp laserjet 4, hp lasterjet 5, and older external jetdirects.
We have about 13 Canon imagerunner printers most of them still work. There
are even some ir5000's that still work.

>>> On 1/31/2007 at 2:41 AM, in message

<BvZvh.11833$Sz4.8199@prv-forum2.provo.novell.com>,
<alan.coutts@nospam.miller.co.uk> wrote:
> It's interesting that you have this problem with heavy duty Canon
> printers. Out of the 50 printers that our manager services, the 2 that
> don't work are Canon (iR500 & 2800). Should we be trying to compile a
> list of printers that don't work to see if there is any pattern? Would
> this be helpfull for Novell?
>
> I'm unable to go back to the SP5 module as our iPrint is clustered.
> I've
> service packed 2 of our 4 nodes and if I try and run iPrint on an SP5
> node
> now, it won't load. I presume the upgrade has modified the ndps
> database
> in some way and there is no going back.
>
> For the time being, I thinnk I'll create another manager on a SP5 server
>
> to service these two broken printers. I have an SR open with Novell and
>
> our PSE is doing all he can to find any internal updates.
>
>
>> In jest,
>>
>> Meanwhile, whilst we wait for the fix, what do I do with the 40 pairs of


>
> =
>> shoes stuck up in my nether regions put there by my end users? 🙂 I

> have =
>> been going home with icepacks tied around my bum. 🙂
>>
>> Seriously though, it has been painful through this. I built a

> completely =
>> new server and installed iPrint on it, sp5, to handle the printers that

> do =
>> not work. I have only 6 of them, but they were our high duty Canon and

> =
>> newer HP printers.
>>
>> Sincerely,
>>
>> Tom
>>
>>
>> >>> Marcel Cox<cimetmc@myrealbox.com> 1/30/2007 2:31 PM >>>

>> terry@nomail.com wrote:
>>
>> >Is there any way to be emailed when the new Gateway is ready AND

> working?
>>
>> Well, what you can do is the following:
>>
>> Add the following wiki page on your watch list (you need to login with =
>> a=20
>> Novell web account to put the article on your watch list):
>>
>> http://wiki.novell.com/index.php/Nw65sp6
>>
>> Then configure your user to be sent an email when the article changes.
>>
>> I will promise I will do my best to update the page as soon as there

> is=20
>> new information.
>> Of course, you will also get emails for other updates on that page

> not=20
>> related to iPrint.
>>
>> --=20
>> Marcel Cox (using XanaNews 1.18.1.6)
>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

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

Looks like novell just posted the update at 2:28 PM MST.

>>> On 1/30/2007 at 8:54 AM, in message

<9TJvh.11005$Sz4.1387@prv-forum2.provo.novell.com>, <terry@nomail.com>
wrote:
> 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.

novpatch3761.zip does not work

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.

>>> On 1/31/2007 at 10:24 AM, in message

<5h4wh.13$pG6.2@janeway.provo.novell.com>, <iprintrox@iprint.novell.com>
wrote:
> 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.

novpatch3761.zip does not work

This patch does nothing for my printing either. "LPR Communication failure"
is still the issue.


> 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.
>
> >>> On 1/31/2007 at 10:24 AM, in message

> <5h4wh.13$pG6.2@janeway.provo.novell.com>, <iprintrox@iprint.novell.com>
> wrote:
> > 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: novpatch3761.zip does not work

Have you used the patchfeedback email address from the readme to report
your findings?

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

tony.hill@scu wrote:

>This patch does nothing for my printing either. "LPR Communication failure"
>is still the issue.


Read the following TID:

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&sliceId=SAL_Public&externalId=3233501

and make sure you provide the feedback as requested by this TID. That's
alas all I can suggest.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

I followed the instructions in the TID by unplugging the printer for one
minute. After printer bootup I was able to telnet to both lpr port 515 and
RAW port 9100. I shutdown and restarted the printer agent. The status of
the printer agent showed PRINTING. Nothing came out of the printer. After
about 2 minutes the status show lpr communication failed. Afterwards I was
able to telnet to port 9100 but not 515.
>>> On 2/1/2007 at 1:09 AM, in message <eps6tk$aon$4@linux.cie.etat.lu>,

Marcel
Cox<cimetmc@myrealbox.com> wrote:
> Have you used the patchfeedback email address from the readme to report
> your findings?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

Doyle collings wrote:

>I followed the instructions in the TID by unplugging the printer for one
>minute. After printer bootup I was able to telnet to both lpr port 515 and
>RAW port 9100. I shutdown and restarted the printer agent. The status of
>the printer agent showed PRINTING. Nothing came out of the printer. After
>about 2 minutes the status show lpr communication failed. Afterwards I was
>able to telnet to port 9100 but not 515.


I got the following new instructions from Novell:

<<<<<<<<<<<<<<<<<<<
Can you post this in the thread:

Thank you for your feedback. Because we cannot duplicate these
scenarios, we rely on your feedback to get this right. Novell would
appreciate it if you could help us understand the reason your printers
are not working our gateway so we can change our code. Will you send the
following information to patchfeedback@novell.com with the subject of
"LPR Communication Failed with Patch D"?



1. Send me screenshot of printer statistics.

a. Go to NetWare Remote Manager

[url]https://[IPAddressOfServer]:8009/[/url]

b. Click the "NDPS Manager Health" link

c. Click the Printer Agent in the LPR Communication Failed
state.

d. Send me a screenshot of this page.

e. Click the "Job List" link.

f. Send me a screenshot of this page.



2. Send me screenshot of printer statistics.

a. Go to NetWare Remote Manager

[url]https://[IPAddressOfServer]:8009/[/url]

b. Click the "NDPS Gateway Health" link

c. Click the Printer Agent in the LPR Communication Failed
state.

d. Send me a screenshot of this page.



3. Send a Config.txt of the server

a. At the server console, type:

LOAD CONFIG

b. Send me the sys:system\config.txt



4. Capture a network trace while the printer is in this state:

a. Download PKTSCAN from Novell's Support Site:

http://support.novell.com/cgi-
bin/search/searchtid.cgi?/2967287.htm

b. Extract the downloaded EXE

c. Copy PKTSCAN.NLM to your server's SYS:\SYSTEM directory

d. At the server console, type

PKTSCAN

e. From a web browser, go to:

[url]http://[IPAddressOfServer]:8008/packetscan[/url]

f. Click the CONFIGURE button

g. Click the CONFIGURE PROFILES link

h. Create a new profile with an 80 MB buffer.

i. Click the radio button for the new profile that you just
created.

j. Click the Done button.

k. Unload PCKTScan (hit ESC twice at the server console)

l. Load PCKTScan

m. Go back to the web interface and click the START CAPTURE
button.

n. Let this run for 10 minutes. (Be sure that the printer is
in the LPR Communication Failed state.)

o. Click Stop Capture

p. Click Retrieve Packets

q. Zip up the trace file

r. Upload the ZIP file to ftp.novell.com/incoming

s. Send me an email with the name of the ZIP file and the
IP Address(s) of the printer(s) in the LPR error state.



Thank you,
>>>>>>>>>>>>>>>>>>


--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

tony.hill@scu wrote:

>This patch does nothing for my printing either. "LPR Communication failure"
>is still the issue.


I got the following instructions from Novell:

<<<<<<<<<<<<<<<<<<<<<
Can you post this in the thread:

Thank you for your feedback. Because we cannot duplicate these
scenarios, we rely on your feedback to get this right. Novell would
appreciate it if you could help us understand the reason your printers
are not working our gateway so we can change our code. Will you send the
following information to patchfeedback@novell.com with the subject of
"LPR Communication Failed with Patch D"?



1. Send me screenshot of printer statistics.

a. Go to NetWare Remote Manager

[url]https://[IPAddressOfServer]:8009/[/url]

b. Click the "NDPS Manager Health" link

c. Click the Printer Agent in the LPR Communication Failed
state.

d. Send me a screenshot of this page.

e. Click the "Job List" link.

f. Send me a screenshot of this page.



2. Send me screenshot of printer statistics.

a. Go to NetWare Remote Manager

[url]https://[IPAddressOfServer]:8009/[/url]

b. Click the "NDPS Gateway Health" link

c. Click the Printer Agent in the LPR Communication Failed
state.

d. Send me a screenshot of this page.



3. Send a Config.txt of the server

a. At the server console, type:

LOAD CONFIG

b. Send me the sys:system\config.txt



4. Capture a network trace while the printer is in this state:

a. Download PKTSCAN from Novell's Support Site:

http://support.novell.com/cgi-
bin/search/searchtid.cgi?/2967287.htm

b. Extract the downloaded EXE

c. Copy PKTSCAN.NLM to your server's SYS:\SYSTEM directory

d. At the server console, type

PKTSCAN

e. From a web browser, go to:

[url]http://[IPAddressOfServer]:8008/packetscan[/url]

f. Click the CONFIGURE button

g. Click the CONFIGURE PROFILES link

h. Create a new profile with an 80 MB buffer.

i. Click the radio button for the new profile that you just
created.

j. Click the Done button.

k. Unload PCKTScan (hit ESC twice at the server console)

l. Load PCKTScan

m. Go back to the web interface and click the START CAPTURE
button.

n. Let this run for 10 minutes. (Be sure that the printer is
in the LPR Communication Failed state.)

o. Click Stop Capture

p. Click Retrieve Packets

q. Zip up the trace file

r. Upload the ZIP file to ftp.novell.com/incoming

s. Send me an email with the name of the ZIP file and the
IP Address(s) of the printer(s) in the LPR error state.



Thank you,

>>>>>>>>>>>>>>>>>>>>


--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: novpatch3761.zip does not work

Ok Marcel,thanks, will do.

> tony.hill@scu wrote:
>
> >This patch does nothing for my printing either. "LPR Communication failure"
> >is still the issue.

>
> I got the following instructions from Novell:
>
> <<<<<<<<<<<<<<<<<<<<<
> Can you post this in the thread:
>
> Thank you for your feedback. Because we cannot duplicate these
> scenarios, we rely on your feedback to get this right. Novell would
> appreciate it if you could help us understand the reason your printers
> are not working our gateway so we can change our code. Will you send the
> following information to patchfeedback@novell.com with the subject of
> "LPR Communication Failed with Patch D"?
>
>
>
> 1. Send me screenshot of printer statistics.
>
> a. Go to NetWare Remote Manager
>
> [url]https://[IPAddressOfServer]:8009/[/url]
>
> b. Click the "NDPS Manager Health" link
>
> c. Click the Printer Agent in the LPR Communication Failed
> state.
>
> d. Send me a screenshot of this page.
>
> e. Click the "Job List" link.
>
> f. Send me a screenshot of this page.
>
>
>
> 2. Send me screenshot of printer statistics.
>
> a. Go to NetWare Remote Manager
>
> [url]https://[IPAddressOfServer]:8009/[/url]
>
> b. Click the "NDPS Gateway Health" link
>
> c. Click the Printer Agent in the LPR Communication Failed
> state.
>
> d. Send me a screenshot of this page.
>
>
>
> 3. Send a Config.txt of the server
>
> a. At the server console, type:
>
> LOAD CONFIG
>
> b. Send me the sys:system\config.txt
>
>
>
> 4. Capture a network trace while the printer is in this state:
>
> a. Download PKTSCAN from Novell's Support Site:
>
> http://support.novell.com/cgi-
> bin/search/searchtid.cgi?/2967287.htm
>
> b. Extract the downloaded EXE
>
> c. Copy PKTSCAN.NLM to your server's SYS:\SYSTEM directory
>
> d. At the server console, type
>
> PKTSCAN
>
> e. From a web browser, go to:
>
> [url]http://[IPAddressOfServer]:8008/packetscan[/url]
>
> f. Click the CONFIGURE button
>
> g. Click the CONFIGURE PROFILES link
>
> h. Create a new profile with an 80 MB buffer.
>
> i. Click the radio button for the new profile that you just
> created.
>
> j. Click the Done button.
>
> k. Unload PCKTScan (hit ESC twice at the server console)
>
> l. Load PCKTScan
>
> m. Go back to the web interface and click the START CAPTURE
> button.
>
> n. Let this run for 10 minutes. (Be sure that the printer is
> in the LPR Communication Failed state.)
>
> o. Click Stop Capture
>
> p. Click Retrieve Packets
>
> q. Zip up the trace file
>
> r. Upload the ZIP file to ftp.novell.com/incoming
>
> s. Send me an email with the name of the ZIP file and the
> IP Address(s) of the printer(s) in the LPR error state.
>
>
>
> Thank you,
>
> >>>>>>>>>>>>>>>>>>>>

>
> --
> Marcel Cox (using XanaNews 1.18.1.6)


0 Likes
Anonymous_User Absent Member.
Absent Member.

novpatch3761.zip does not work

This new patch doesn't work for me either. I have a few older LaserJet4
printers that won't come up. I guess I'll spend the next hour or two
gathering all this diagnostic data that Novell wants and send it to that
email address.

It would be easier if they just backed out this new "functionality" until
they had a chance to test it better.

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?

> 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.
>
> >>> On 1/31/2007 at 10:24 AM, in message

> <5h4wh.13$pG6.2@janeway.provo.novell.com>, <iprintrox@iprint.novell.com>
> wrote:
> > 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: novpatch3761.zip does not work

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
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.