Home

Results 1 to 7 of 7

Thread: New iPrint patch iprntnw65sp6d

  1. #1
    Tom Hafemann NNTP User

    New iPrint patch iprntnw65sp6d

    Hey All,

    I noticed the new FTF patch out there right away this morning. I put it on and my Canon IR 5000 is working. However, it would work for about 2 hours after a reboot anyway so we'll see.

    It also broke, or seem to break, our Dell S2500n printers. I am going to further investigate it. So far, so good, however, for the people that count on the high capacity printers.

    We'll keep you informed.

    Tom

  2. #2
    iprintrox@iprint.novell.com NNTP User

    New iPrint patch iprntnw65sp6d

    I posted this on the other thread, and thought it would be good to post
    here as well.'


    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!!
    > Hey All,
    >
    > I noticed the new FTF patch out there right away this morning. I put it =
    > on and my Canon IR 5000 is working. However, it would work for about 2 =
    > hours after a reboot anyway so we'll see.
    >
    > It also broke, or seem to break, our Dell S2500n printers. I am going to =
    > further investigate it. So far, so good, however, for the people that =
    > count on the high capacity printers.
    >
    > We'll keep you informed.
    >
    > Tom
    >



  3. #3
    terry@nomail.com NNTP User

    New iPrint patch iprntnw65sp6d

    I have a brand new HP LaserJet 4250tn with all the latest firmware on it
    that has LPR problems. Every morning I have to power off this printer for
    30 seconds and turn it back on again. Then I shutdown it's agent and bring
    it back up. It's fine for the rest of the day after that.

    I have other brand new 4250s that don't have any problems. Doesn't this
    kind of blow a hole in the old NIC / new NIC theory?

    > I posted this on the other thread, and thought it would be good to post
    > here as well.'
    >
    >
    > 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!!
    > > Hey All,
    > >
    > > I noticed the new FTF patch out there right away this morning. I put it =
    > > on and my Canon IR 5000 is working. However, it would work for about 2 =
    > > hours after a reboot anyway so we'll see.
    > >
    > > It also broke, or seem to break, our Dell S2500n printers. I am going to =
    > > further investigate it. So far, so good, however, for the people that =
    > > count on the high capacity printers.
    > >
    > > We'll keep you informed.
    > >
    > > Tom
    > >

    >



  4. #4
    iprintrox NNTP User

    Re: New iPrint patch iprntnw65sp6d

    Sure does. However I did say, "Newer model printers don't seem to have as much of a problem. " which would imply some newer models still exhibit the issue. Frustrating thing about print is that there as many different printers as there are customers.. I still believe we have identified a behavior that is valid shortcoming and is being addressed.


    >>> <terry@nomail.com> 2/5/2007 8:35 AM >>>

    I have a brand new HP LaserJet 4250tn with all the latest firmware on it
    that has LPR problems. Every morning I have to power off this printer for
    30 seconds and turn it back on again. Then I shutdown it's agent and bring
    it back up. It's fine for the rest of the day after that.

    I have other brand new 4250s that don't have any problems. Doesn't this
    kind of blow a hole in the old NIC / new NIC theory?


    > I posted this on the other thread, and thought it would be good to post
    > here as well.'
    >
    >
    > 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!!

    > > Hey All,
    > >
    > > I noticed the new FTF patch out there right away this morning. I put it =
    > > on and my Canon IR 5000 is working. However, it would work for about 2 =
    > > hours after a reboot anyway so we'll see.
    > >
    > > It also broke, or seem to break, our Dell S2500n printers. I am going to =
    > > further investigate it. So far, so good, however, for the people that =
    > > count on the high capacity printers.
    > >
    > > We'll keep you informed.
    > >
    > > Tom
    > >

    >

  5. #5
    Tom Hafemann NNTP User

    Re: New iPrint patch iprntnw65sp6d

    Hey there,

    I have been running the new gateway, and it WORKS for me. I deleted the old printers that didn't work and recreated them as LPR. They then started working. The Canon IR printers started working with just the new NDPSGW.

    I like the PING/dns feature in the new gateway. If a printer can not be pinged, we get the error on the screen. Because we use DHCP and DDNS for our printers, it is helpful to see if a problem is with DNS or the printer itself. Most of the times it IS with DDNS not updating.

    Tom


    >>> <iprintrox@iprint.novell.com> 2/3/2007 11:40 PM >>>

    I posted this on the other thread, and thought it would be good to post
    here as well.'


    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!!
    > Hey All,
    >
    > I noticed the new FTF patch out there right away this morning. I put it =
    > on and my Canon IR 5000 is working. However, it would work for about 2 =
    > hours after a reboot anyway so we'll see.
    >
    > It also broke, or seem to break, our Dell S2500n printers. I am going to =
    > further investigate it. So far, so good, however, for the people that =
    > count on the high capacity printers.
    >
    > We'll keep you informed.
    >
    > Tom
    >


  6. #6
    terry@nomail.com NNTP User

    Re: New iPrint patch iprntnw65sp6d

    Sorry. I don't speak machine code.

    > U3VyZSBkb2VzLiAgIEhvd2V2ZXIgSSBkaWQgc2F5LCAgIk5ld2 VyIG1vZGVsIHByaW50ZXJzIGRv
    > bid0IHNlZW0gdG8gaGF2ZSBhcyBtdWNoIG9mIGEgcHJvYmxlbS 4gIiAgIHdoaWNoIHdvdWxkIGlt
    > cGx5IHNvbWUgbmV3ZXIgbW9kZWxzIHN0aWxsIGV4aGliaXQgdG hlIGlzc3VlLiAgIEZydXN0cmF0
    > aW5nIHRoaW5nIGFib3V0IHByaW50IGlzIHRoYXQgdGhlcmUgYX MgbWFueSBkaWZmZXJlbnQgcHJp
    > bnRlcnMgYXMgdGhlcmUgYXJlIGN1c3RvbWVycy4uICBJIHN0aW xsIGJlbGlldmUgd2UgaGF2ZSBp
    > ZGVudGlmaWVkIGEgYmVoYXZpb3IgdGhhdCBpcyB2YWxpZCBzaG 9ydGNvbWluZyBhbmQgaXMgYmVp
    > bmcgYWRkcmVzc2VkLg0KDQo+Pj4gPHRlcnJ5QG5vbWFpbC5jb2 0+IDIvNS8yMDA3IDg6MzUgQU0g
    > Pj4+DQpJIGhhdmUgYSBicmFuZCBuZXcgSFAgTGFzZXJKZXQgND I1MHRuIHdpdGggYWxsIHRoZSBs
    > YXRlc3QgZmlybXdhcmUgb24gaXQNCnRoYXQgaGFzIExQUiBwcm 9ibGVtcy4gRXZlcnkgbW9ybmlu
    > ZyBJIGhhdmUgdG8gcG93ZXIgb2ZmIHRoaXMgcHJpbnRlciBmb3 INCjMwIHNlY29uZHMgYW5kIHR1
    > cm4gaXQgYmFjayBvbiBhZ2Fpbi4gVGhlbiBJIHNodXRkb3duIG l0J3MgYWdlbnQgYW5kIGJyaW5n
    > DQppdCBiYWNrIHVwLiBJdCdzIGZpbmUgZm9yIHRoZSByZXN0IG 9mIHRoZSBkYXkgYWZ0ZXIgdGhh
    > dC4NCg0KSSBoYXZlIG90aGVyIGJyYW5kIG5ldyA0MjUwcyB0aG F0IGRvbid0IGhhdmUgYW55IHBy
    > b2JsZW1zLiBEb2Vzbid0IHRoaXMNCmtpbmQgb2YgYmxvdyBhIG hvbGUgaW4gdGhlIG9sZCBOSUMg
    > LyBuZXcgTklDIHRoZW9yeT8NCg0KPiBJIHBvc3RlZCB0aGlzIG 9uIHRoZSBvdGhlciB0aHJlYWQs
    > IGFuZCB0aG91Z2h0IGl0IHdvdWxkIGJlIGdvb2QgdG8gcG9zdA 0KPiBoZXJlIGFzIHdlbGwuJw0K
    > PiANCj4gDQo+IFdlIGhhdmUgZm91bmQgYSByYXRoZXIgdW51c3 VhbCBiZWhhdmlvciBpbiB2YXJp
    > b3VzIE5JQyBjYXJkcyBpbiB2YXJpb3VzDQo+IHByaW50ZXJzLi AgIE9sZGVyIE5JQyBjYXJkcyBp
    > biBwcmludGVycyBkZWFsaW5nIHdpdGggTFBSIGFyZSByYXRoZX IgcGlja3kNCj4gYWJvdXQgdGhl
    > IHBvcnRzIGFuZCBzb2NrZXRzIGJlaW5nIHVzZWQuICAgTmV3ZX IgbW9kZWwgcHJpbnRlcnMgZG9u
    > J3Qgc2VlbQ0KPiB0byBoYXZlIGFzIG11Y2ggb2YgYSBwcm9ibG VtLiAgDQo+IA0KPiBUaGUgaXNz
    > dWUgaXMgdGhhdCB0aGUgR2F0ZXdheSBjYW4gInBpbmciIHRoZS BwcmludGVyLCB0aGUgR2F0ZXdh
    > eSBjYW4NCj4gInNubXAiIHRoZSBwcmludGVyLCBhbmQgdGhlIE dhdGV3YXkgY2FuIGV2ZW4gb3Bl
    > biBhIHNvY2tldCB0byB0aGUgcHJpbnRlcg0KPiBmb3IgTFBSIG NvbW11bmljYXRpb24uICAgSG93
    > ZXZlciB3aGVuIGRhdGEgaXMgc2VudCB2aWEgdGhlIHBvcnQgYW 5kIHNvY2tldA0KPiBvcGVuZWQs
    > IHRoZSBwcmludGVyIHNlbmRzIGJhY2sgYW4gZXJyb3IgdG8gdG hlIEdhdGV3YXkgdGhhdCBwcm9o
    > aWJpdHMgdGhlDQo+IEdhdGV3YXkgZnJvbSBzZW5kaW5nIG1vcm UgZGF0YSwgYW5kIGhlbmNlIHRo
    > ZSBMUFIgY29tbXVuaWNhdGlvbiBmYWlsdXJlLiANCj4gV2UgaG F2ZSBkdXBsaWNhdGVkIHRoaXMg
    > YmVoYXZpb3IgaW4gb2xkZXIgSmV0RGlyZWN0IGNhcmRzIGluIE hQIDUwMDANCnByaW50ZXJzLg0K
    > PiANCj4gQXMgZmFyIGFzIHdlIGtub3csIHJ1bm5pbmcgUkFXIG luc3RlYWQgb2YgTFBSIHNlZW1z
    > IHRvIHdvcmsuICBSQVcgZG9lcyBub3QNCj4gaGF2ZSB0aGlzIG xpbWl0aW5nIGJlaGF2aW9yIHRo
    > YXQgd2Ugc2VlIHdpdGggTFBSLiAgU28sIGluIGNhc2VzIHRoYX QgYWxsb3cNCj4gdGhlIGNoYW5n
    > ZSBvZiBwcm90b2NvbCBmcm9tIExQUiB0byBSQVcsIHBsZWFzZS B0cnkgUkFXIGFuZCBzZWUgd2hh
    > dA0KPiBoYXBwZW5zLiAgIFdlIGhhdmUgd29ya2VkIG9uIGEgZm l4IGZvciB0aGUgYW5kIGhvcGVm
    > dWxseSB3aWxsIGhhdmUgaXQgb3V0DQo+IHF1aWNrLiAgICANCj 4gDQo+IENoYW5naW5nIHRoZSBw
    > cm90b2NvbCBmcm9tIExQUiB0byBSQVcgcmVxdWlyZXMgdGhhdC B0aGUgZ2F0ZXdheSBsb2FkIHN0
    > cmluZw0KPiBiZSBtb2RpZmllZC4gICBUaGUgZWFzaWVzdCB3YX kgdG8gZG8gdGhpcyBpcyB0byBj
    > cmVhdGUgYSAiZHVtbXkgcHJpbnRlciINCj4gdXNpbmcgdGhlIF JBVyBwcm90b2NvbCBpbnN0ZWFk
    > IG9mIHRoZSBMUFIgcHJvdG9jb2wuICAgTG9vayBhdCB0aGUgZ2 F0ZXdheQ0KPiBsb2FkIHN0cmlu
    > ZyBhbmQgY29tcGFyZSB0aGlzIGFnYWluc3QgYW4gZXhpc3Rpbm cgTFBSIGNvbmZpZ3VyZWQgcHJp
    > bnRlciwNCj4gdGhlbiBtYWtlIHRoZSBhcHByb3ByaWF0ZSBjaG FuZ2VzLiAgIFJlbWVtYmVyIHRo
    > YXQgb25jZSB5b3UgY2hhbmdlIHRoZQ0KPiBnYXRld2F5IGxvYW Qgc3RyaW5nLCB0aGUgcHJpbnRl
    > ciBhZ2VudCBtdXN0IGJlIHJlc3RhcnRlZCB0byB0YWtlIGVmZm VjdC4gIA0KPiBTaHV0ZG93biB0
    > aGUgcHJpbnRlciBhZ2VudCBhbmQgc3RhcnQgaXQgYmFjayB1cC 4NCj4gDQo+IFBsZWFzZSBjb250
    > aW51ZSB0aGUgZmVlZGJhY2sgYXMgdG8gd2hldGhlciB0aGlzIG hlbHBzLg0KPiANCj4gVGhhbmsg
    > eW91ISEgDQo+ID4gSGV5IEFsbCwNCj4gPiANCj4gPiBJIG5vdG ljZWQgdGhlIG5ldyBGVEYgcGF0
    > Y2ggb3V0IHRoZXJlIHJpZ2h0IGF3YXkgdGhpcyBtb3JuaW5nLi AgSSBwdXQgaXQgPQ0KPiA+IG9u
    > IGFuZCBteSBDYW5vbiBJUiA1MDAwIGlzIHdvcmtpbmcuICBIb3 dldmVyLCBpdCB3b3VsZCB3b3Jr
    > IGZvciBhYm91dCAyID0NCj4gPiBob3VycyBhZnRlciBhIHJlYm 9vdCBhbnl3YXkgc28gd2UnbGwg
    > c2VlLg0KPiA+IA0KPiA+IEl0IGFsc28gYnJva2UsIG9yIHNlZW 0gdG8gYnJlYWssIG91ciBEZWxs
    > IFMyNTAwbiBwcmludGVycy4gIEkgYW0gZ29pbmcgdG8gPQ0KPi A+IGZ1cnRoZXIgaW52ZXN0aWdh
    > dGUgaXQuICBTbyBmYXIsIHNvIGdvb2QsIGhvd2V2ZXIsIGZvci B0aGUgcGVvcGxlIHRoYXQgPQ0K
    > PiA+IGNvdW50IG9uIHRoZSBoaWdoIGNhcGFjaXR5IHByaW50ZX JzLg0KPiA+IA0KPiA+IFdlJ2xs
    > IGtlZXAgeW91IGluZm9ybWVkLg0KPiA+IA0KPiA+IFRvbQ0KPi A+IA0KPiA=
    >



  7. #7
    Joseph Marton NNTP User

    Re: New iPrint patch iprntnw65sp6d

    On Mon, 05 Feb 2007 20:24:46 +0000, terry wrote:

    > Sorry. I don't speak machine code.


    Here is what he said:

    Sure does. However I did say, "Newer model printers don't seem to have
    as much of a problem. " which would imply some newer models still
    exhibit the issue. Frustrating thing about print is that there as many
    different printers as there are customers.. I still believe we have
    identified a behavior that is valid shortcoming and is being addressed.

    --
    Joe Marton
    Novell Support Forum SysOp
    Novell does not officially monitor these forums!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •