Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
2122 views

Xerox 255ST and Novell gateway

Printer: Xerox 255ST
Port9100 printing and LPR printing are both enabled on the printer.

Server is clustered OES-NW-sp2 plus post-patches including all the
latest updates to NDPSM, iPrint files, etc.
NDPSM= 3.01.20 dated June 7, 2006
NDPSGW=3.02.01 dated Oct 27, 2005

The latest drivers from Xerox have been downloaded and installed into
the Broker.

Printer has been connected in the past using Novell gateway, IP only,
LPR printing using the following gateway command:

NDPSGW PORT=LPR HOSTADDRESS=XXX.XXX.XXX.XXX PRINTERNAME=lp

and has printed in the past. This weekend the printer was migrated to
a clustered print manager using the migration tool, since then it will
not print. The printer will install to workstations, jobs can be sent
to the printer and the printer shows "printing" but never kicks out a
job. Looking at the printer in the print manager it shows that 32k of
the job has been transmitted and the job never progresses beyond this
point. All 200 other printers running from this same print manager
are working just fine.

I have changed the gateway configuration on the printer to:
NDPSGW PORT=RAW HOSTADDRESS=XXX.XXX.XXX.XXX
and verified that port9100 printing was enabled on the printer, and I
still get the same results--jobs appear to arrive at the printer but
do not process through.

I then installed the printer on my workstation as a local printer
using an IP port and was able to print to it just fine--kicks out the
job immediately. I went into the printer properties and noted that it
had, by default, set up to use LPR printing with a print name of
"lp"-- the same as I had been using in the string on the Novell
gateway. I then switched the IP port to RAW and port 9100 and again
was able to print through it. However, I have not had any success
getting this printer to print using the Novell gateway--even when
setting up a new printer agent for the printer via iManager.

Any ideas?? Thanks,

DeVern

0 Likes
6 Replies
Absent Member.
Absent Member.

Do you have IP address restrictions defined on yoru printer? Maybe the
server is using an IP address that the printer doesn't allow for printing.

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

On Wed, 07 Jun 2006 20:37:30 GMT, "Marcel Cox" <cimetmc@myrealbox.com>
wrote:

>Do you have IP address restrictions defined on yoru printer? Maybe the
>server is using an IP address that the printer doesn't allow for printing.


No restrictions set. The only info on the ip restrictions page is the
default examples, remarked out.

The printer communicates via both lpr and port 9100 when using a
standard tcpip port but will NOT communicate via either when passing
through NDPS. Driver issue?? Printer firmware issue?? This printer
worked until it was migrated and now cannot be made to work even by
building a new printer agent for it.....

Thanks,

DeVern
0 Likes
Absent Member.
Absent Member.

On Wed, 07 Jun 2006 20:37:30 GMT, "Marcel Cox" <cimetmc@myrealbox.com>
wrote:

>Do you have IP address restrictions defined on yoru printer? Maybe the
>server is using an IP address that the printer doesn't allow for printing.


More info:
Just as a test I built a print agent for this printer on a 5.1sp8
server at another site. I used the same Xerox print driver that was
used on the OES 6.5 server. I can print though this new print agent
with no problems. The server I used is running NDPSM 3.01n dated Feb
16, 2005 and NDPSGW 3.01g dated Jan 11, 2005.

??

DeVern
0 Likes
Absent Member.
Absent Member.

DeVern Gerber wrote:

>Just as a test I built a print agent for this printer on a 5.1sp8
>server at another site. I used the same Xerox print driver that was
>used on the OES 6.5 server. I can print though this new print agent
>with no problems. The server I used is running NDPSM 3.01n dated Feb
>16, 2005 and NDPSGW 3.01g dated Jan 11, 2005.



Are you using the same driver in both cases?

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

On Thu, 08 Jun 2006 06:42:08 GMT, "Marcel Cox" <cimetmc@myrealbox.com>
wrote:

>Are you using the same driver in both cases?


Yes, in fact I built print agents using all the different drivers I
have on both platforms; all of them worked on the 5.1 boxes (tried
several different servers) and none of them worked from the print
managers I had running on ANY of my OES-sp5 boxes.....

I did some more searching in the KB and couldn't find anything that
referenced this problem directly or indirectly, but did run across
TID10015999 dealing with parameters (including LPR settings) for the
NWPARAM file but I don't think that should be in play here-- both the
5.1 and 6.5 boxes have the default NWPARAMS file containing only the
following entry:

[GLOBAL]
SYNC_INTERVAL 60

I'm going to have the site get the Xerox rep out to make sure the
printer has the latest firmware and onboard tcpip stack, but since
this is working fine through the 5.1 boxes I'm still thinking the
problem is somewhere on the NW communications side....

Thanks,

DeVern

0 Likes
Absent Member.
Absent Member.

NWPARAMS was only used for Unix print services. It has no effect on NDPS.

Anyway, for your problem, I guess the only way to see what is going on is
to take a capture of the network traffic between the server and the
problem printer. Are you able to take a capture of that traffic?

--
Marcel Cox (using XanaNews 1.18.1.3)
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.