Anonymous_User Absent Member.
Absent Member.
11394 views

LPR Communication Failed error: 36

We have an HP 5550 that is showing the following error:

LPR Communication Failed: Initial connection test at bind time failed,
error: 36
Can Not Ping Printer: Last good ping: never
SNMP Communication Failed:

The printer seems to work fine. Nonetheless, I would like to try resolving
this issue in case it is a symptom of an as yet undiscovered problem.
Unfortunately, I have not been able to find anything on this error. I've
solved other "LPR Communication Failed" errors in the past, but I've never
seen this particular error.

Any help that you can offer will be greatly appreciated.

--Tom


0 Likes
7 Replies
Marcel_Cox Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

The message claims that the server can't ping the printer. Have you tried
manually pinging the printer from the server?

--
Marcel Cox
Discover the new Novell forums at http://forums.novell.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

I don't have access to the server. The server-side stuff is handled by
another group so I will need to work with one of them to see if it can be
pinged from the server. I am able to ping the IP address of the printer
from my workstation.

--Tom

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:fobnp9$pfg$1@linux.cie.etat.lu...
> The message claims that the server can't ping the printer. Have you tried
> manually pinging the printer from the server?
>
> --
> Marcel Cox
> Discover the new Novell forums at http://forums.novell.com



0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

Thomas M. wrote:

>The server-side stuff is handled by another group


Well, in that case, troubleshooting a communication error between the
server and the printer is kind of hard. You really need to work together
with the server people to fix this problem.

--
Marcel Cox (Sysop)
Discover the new Novell forums at http://forums.novell.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

Which is what I said in my last message. 😉

I talked to one of the server guys and they are unable to ping the printer
from any server. There is no special security setup on the printer in
iPrint.

The printer is currently using the HP 5550 PCL 6 driver. We have found that
in general the "50 series" drivers are less reliable than the "00 series"
drivers. For example, we have more problems with 5550 drivers than with
5500 drivers, and the same holds true for 4250 vs. 4200, 4050 vs. 4000, etc.
We have also found that the PCL 6 drivers seems to be more problematic than
the PCL 5e drivers. So maybe a change in drivers will solve the problem.

At any rate, I do have server guy look at it now. If he can't find the
problem, maybe we'll just blow away the printer in iPrint and rebuild it
from scratch.

--Tom

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:7znqj.30394$k06.30219@kovat.provo.novell.com...
> Thomas M. wrote:
>
>>The server-side stuff is handled by another group

>
> Well, in that case, troubleshooting a communication error between the
> server and the printer is kind of hard. You really need to work together
> with the server people to fix this problem.
>
> --
> Marcel Cox (Sysop)
> Discover the new Novell forums at http://forums.novell.com



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

Okay, seconds after hitting the Send button on the last message, it occurred
to me that drivers are probably not the issue when it comes to
communications problems with the server, but I'm not really sure how that
all works in iPrint so I guess it's something that I can check out with our
server guys.

I am also thinking that maybe a needed communications protocol on the
printer got turned off when the printer was initially setup. I'm going to
check out that possibility as well. I'm also going to check the printer
firmware because outdated firmware has bitten us in the back side in the
past.

--Tom

"Thomas M." <NoEmailReplies@Please.com> wrote in message
news:xXqqj.30577$k06.6630@kovat.provo.novell.com...
> Which is what I said in my last message. 😉
>
> I talked to one of the server guys and they are unable to ping the printer
> from any server. There is no special security setup on the printer in
> iPrint.
>
> The printer is currently using the HP 5550 PCL 6 driver. We have found
> that in general the "50 series" drivers are less reliable than the "00
> series" drivers. For example, we have more problems with 5550 drivers
> than with 5500 drivers, and the same holds true for 4250 vs. 4200, 4050
> vs. 4000, etc. We have also found that the PCL 6 drivers seems to be more
> problematic than the PCL 5e drivers. So maybe a change in drivers will
> solve the problem.
>
> At any rate, I do have server guy look at it now. If he can't find the
> problem, maybe we'll just blow away the printer in iPrint and rebuild it
> from scratch.
>
> --Tom
>
> "Marcel Cox" <cimetmc@myrealbox.com> wrote in message
> news:7znqj.30394$k06.30219@kovat.provo.novell.com...
>> Thomas M. wrote:
>>
>>>The server-side stuff is handled by another group

>>
>> Well, in that case, troubleshooting a communication error between the
>> server and the printer is kind of hard. You really need to work together
>> with the server people to fix this problem.
>>
>> --
>> Marcel Cox (Sysop)
>> Discover the new Novell forums at http://forums.novell.com

>
>



0 Likes
wdlarg01 Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

You're correct thinking that the drivers are not the immediate problem. The print manager, ndpsm, needs to be able to talk to the printer, I believe using regular LPR comms. If you can't even ping it, something pretty fundamental is wrong. Wrong IP, bad jack, firewall settings, wrong VLAN, bad NIC in printer, DHCP entries. Lots of things.
Once that's fixed, then you can worry about the driver getting delivered to the workstation, and it's ability to present a properly defined data stream to the printer that puts the ink in the right spots.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LPR Communication Failed error: 36

I did do the firmware update and I checked the communication protocols on
the printer to make sure that the right ones are enabled, but as I suspected
that did not fix the problem. I also checked the NIC and it is set to run
at 100 full.

I am now thinking more along the lines of a possible problem with the
physical printer hardware. Although the printer is currently working, the
more I have dug into this issue the more I've learned from the users that
there have always been issues with the printer--it's slow, it will only
print one copy at a time, etc. That kind of points to maybe the NIC
operating intermittently, or maybe the network jack is having a problem.

--Tom

"wdlarg01" <wdlarg01@no-mx.forums.novell.com> wrote in message
news:wdlarg01.34euq0@no-mx.forums.novell.com...
>
> You're correct thinking that the drivers are not the immediate problem.
> The print manager, ndpsm, needs to be able to talk to the printer, I
> believe using regular LPR comms. If you can't even ping it, something
> pretty fundamental is wrong. Wrong IP, bad jack, firewall settings,
> wrong VLAN, bad NIC in printer, DHCP entries. Lots of things.
> Once that's fixed, then you can worry about the driver getting
> delivered to the workstation, and it's ability to present a properly
> defined data stream to the printer that puts the ink in the right
> spots.
>
>
> --
> wdlarg01
> ------------------------------------------------------------------------
> wdlarg01's Profile: http://forums.novell.com/member.php?userid=4180
> View this thread: http://forums.novell.com/showthread.php?t=310782
>



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.