Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2006-12-29
02:07
1290 views
Ongoing NW 6.5 SP6 Print issues
Hello,
I recently upgraded a NetWare 6.5 server to Support Pack 6 and I've followed
the threads here on all the iprint issues. I applied the post SP6 NDPS
patches since we were seeing some of issues outlined in the TIDs/Wiki.
I'm currently running NDPSM.NLM 3.02 dated 11/30/2006 and NDPSGW.NLM 4.00.05
dated 11/16/2006. I have approximately 100 printers attached, mostly Jet
Directs and Dell (Lexmark) using LPR. We are seeing frequent
LPR communication failures with these printers now requiring a
shutdown/restart of the printer. It seems to happen mostly with the
standalone Jet Direct boxes that have dot matrix (Okidata) printers attached
to them. I tried switching one of them to the RAW (9100) mode, but I am
still getting reports of the problem. This particular issues does not seem
to be addressed by any of the TIDs/patches.
Has anyone else seen this? Any other ideas on how to work around it? I'm
starting to regret loading SP6! ugh!
Thanks!
13 Replies
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2006-12-29
08:31
Are the communication failures new to SP6? If so, just revert the
NDPSGW.NLM to the SP5 version. This file is relatively indpendent on the
other NDPS files and can be backreved without reverse effect.
--
Marcel Cox
http://support.novell.com/forums
NDPSGW.NLM to the SP5 version. This file is relatively indpendent on the
other NDPS files and can be backreved without reverse effect.
--
Marcel Cox
http://support.novell.com/forums
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2006-12-29
16:55
Yep, printing was perfect before applying SP6. SP6 has created a total
printing nightmare.
I did try back reving both ndpsm and ndpsgw and that crashed the server. So
I will try just back-revving to the SP5 version of NDPSGW and see if that
works.
>>> On 12/29/2006 at 3:31 AM, in message <en2jh5$i12$1@linux.cie.etat.lu>,
Marcel Cox<cimetmc@myrealbox.com> wrote:
> Are the communication failures new to SP6? If so, just revert the
> NDPSGW.NLM to the SP5 version. This file is relatively indpendent on the
>
> other NDPS files and can be backreved without reverse effect.
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-02
13:11
We have the same problem with dot matrix printer.
Do you have found any fix?
Regards
Andreas
UVEX Safety Group
Do you have found any fix?
Regards
Andreas
UVEX Safety Group
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-02
14:45
We tried back-reving NDPSGW to the SP5 version, but I'm still getting
reports of problems with the dot matrix printers.
I'm not sure what else to try at this point either!
>>> On Tue, Jan 2, 2007 at 8:11 AM, in message
<4Ssmh.22516$jS4.2416@prv-forum2.provo.novell.com>, Andreas
Ebert<A.Ebert@uvex-no-spam.de> wrote:
> We have the same problem with dot matrix printer.
>
> Do you have found any fix?
>
> Regards
> Andreas
> UVEX Safety Group
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-02
14:55
Matt Weisberg wrote:
>but I'm still getting
>reports of problems with the dot matrix printers.
still LPR communication issues or something else?
--
Marcel Cox
http://support.novell.com/forums
>but I'm still getting
>reports of problems with the dot matrix printers.
still LPR communication issues or something else?
--
Marcel Cox
http://support.novell.com/forums
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-02
20:45
I thought it was, but upon further investigation, I'm finding that
additional problems are being blamed on this
(typical, eh?). So far, I think back revving the NDPSGW.NLM has solved the
LPR comm. problems for the Dot Matrix printers. I'll keep watching it and
let you know if it does not.
>>> On Tue, Jan 2, 2007 at 9:55 AM, in message
<endric$c4d$4@linux.cie.etat.lu>, Marcel Cox<cimetmc@myrealbox.com>
wrote:
> Matt Weisberg wrote:
>
>>but I'm still getting
>>reports of problems with the dot matrix printers.
>
> still LPR communication issues or something else?
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-03
11:10
back revving the NDPSGW.NLM has solved the
LPR comm. problems for us.
But we have still problems, if our AS/400 prints a job with copies over LPR to our NDPS Manager. Then after SP6 the jobs never ends. The job will be transmitted again and again. It seems that the new NDPS manager does not feed back to the AS/400, that the LPR job is already transmitted. This did not happen with the SP5 NDPS manager.
I am going to open an incident .....
Regards
Andreas
LPR comm. problems for us.
But we have still problems, if our AS/400 prints a job with copies over LPR to our NDPS Manager. Then after SP6 the jobs never ends. The job will be transmitted again and again. It seems that the new NDPS manager does not feed back to the AS/400, that the LPR job is already transmitted. This did not happen with the SP5 NDPS manager.
I am going to open an incident .....
Regards
Andreas
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-04
03:00
I have had a long ongoing incident open with Novell on this very issue. I
have this problem with the external USB 175x JetDirects and the small cheap
internal directs that came with the 1200 and 1300's. I never had the issue
with the more expensive 6xx internal jet directs. I sent them a printer and
after a month they were finally able to replicate the issue. For some reason
the external 170x parallel's work fine. I was beta testing several ndpsgw
modules all the way up to just before SP6 was released. The last one they
gave me made matters much worse. I was even getting the LPR issues with the
6xx cards that never had a problem. But before I could work with support on
it they released it. Now they have the debacle with that version. They are
working on a beta for me to try but have not yet gotten it to me. They are
well aware of the problems with the new gateway. You may have noticed that
when the gateway gives a communication error you can still ping the printer
from the server prompt. I have rolled back the ndpsgw with out any server
abend issues. I will keep this thread posted. Just a side note, the HP
gateway has no such issues. I have converted printers that were having
issues as a test and they work fine. To bad it is not around anymore.
"Matt Weisberg" <mweisberg@myrealbox.com> wrote in message
news:45943215.0F97.0099.0@myrealbox.com...
>
>
>
> Hello,
> I recently upgraded a NetWare 6.5 server to Support Pack 6 and I've
> followed
> the threads here on all the iprint issues. I applied the post SP6 NDPS
> patches since we were seeing some of issues outlined in the TIDs/Wiki.
>
> I'm currently running NDPSM.NLM 3.02 dated 11/30/2006 and NDPSGW.NLM
> 4.00.05
> dated 11/16/2006. I have approximately 100 printers attached, mostly Jet
> Directs and Dell (Lexmark) using LPR. We are seeing frequent
> LPR communication failures with these printers now requiring a
> shutdown/restart of the printer. It seems to happen mostly with the
> standalone Jet Direct boxes that have dot matrix (Okidata) printers
> attached
> to them. I tried switching one of them to the RAW (9100) mode, but I am
> still getting reports of the problem. This particular issues does not
> seem
> to be addressed by any of the TIDs/patches.
>
> Has anyone else seen this? Any other ideas on how to work around it? I'm
> starting to regret loading SP6! ugh!
>
> Thanks!
>
>
have this problem with the external USB 175x JetDirects and the small cheap
internal directs that came with the 1200 and 1300's. I never had the issue
with the more expensive 6xx internal jet directs. I sent them a printer and
after a month they were finally able to replicate the issue. For some reason
the external 170x parallel's work fine. I was beta testing several ndpsgw
modules all the way up to just before SP6 was released. The last one they
gave me made matters much worse. I was even getting the LPR issues with the
6xx cards that never had a problem. But before I could work with support on
it they released it. Now they have the debacle with that version. They are
working on a beta for me to try but have not yet gotten it to me. They are
well aware of the problems with the new gateway. You may have noticed that
when the gateway gives a communication error you can still ping the printer
from the server prompt. I have rolled back the ndpsgw with out any server
abend issues. I will keep this thread posted. Just a side note, the HP
gateway has no such issues. I have converted printers that were having
issues as a test and they work fine. To bad it is not around anymore.
"Matt Weisberg" <mweisberg@myrealbox.com> wrote in message
news:45943215.0F97.0099.0@myrealbox.com...
>
>
>
> Hello,
> I recently upgraded a NetWare 6.5 server to Support Pack 6 and I've
> followed
> the threads here on all the iprint issues. I applied the post SP6 NDPS
> patches since we were seeing some of issues outlined in the TIDs/Wiki.
>
> I'm currently running NDPSM.NLM 3.02 dated 11/30/2006 and NDPSGW.NLM
> 4.00.05
> dated 11/16/2006. I have approximately 100 printers attached, mostly Jet
> Directs and Dell (Lexmark) using LPR. We are seeing frequent
> LPR communication failures with these printers now requiring a
> shutdown/restart of the printer. It seems to happen mostly with the
> standalone Jet Direct boxes that have dot matrix (Okidata) printers
> attached
> to them. I tried switching one of them to the RAW (9100) mode, but I am
> still getting reports of the problem. This particular issues does not
> seem
> to be addressed by any of the TIDs/patches.
>
> Has anyone else seen this? Any other ideas on how to work around it? I'm
> starting to regret loading SP6! ugh!
>
> Thanks!
>
>
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-05
11:56
There is now a patch for the LPR communication issues:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2974964.htm
--
Marcel Cox
http://support.novell.com/forums
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2974964.htm
--
Marcel Cox
http://support.novell.com/forums
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-10
12:44
Thanks but it does still not fix our LPR problem.
Regards
Andreas
Regards
Andreas
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2007-01-11
07:40
Ditto, doesn't fix our LPR problems either. Will try the SP5 gw.
> There is now a patch for the LPR communication issues:
>
> http://support.novell.com/cgi-bin/search/searchtid.cgi?/2974964.htm
>
> --
> Marcel Cox
> http://support.novell.com/forums
> There is now a patch for the LPR communication issues:
>
> http://support.novell.com/cgi-bin/search/searchtid.cgi?/2974964.htm
>
> --
> Marcel Cox
> http://support.novell.com/forums