> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 03, 2004 11:23 PM > To: [EMAIL PROTECTED] > Subject: RE: LPRng: After upgrade still Stalling remote printers > > > >> -----Original Message----- > >> From: Shawn Clark [mailto:[EMAIL PROTECTED] > >> Sent: Monday, March 01, 2004 10:00 AM > >> To: [EMAIL PROTECTED] > >> Subject: LPRng: After upgrade still Stalling remote printers > >> > >> > >> Hello, > >> > >> We have several printers attached to Linksys Print Servers. > >> When multiple > >> jobs are spooled through LPRng the print queues seem to > hang up and go > >> into "stalled" state. Removing the printjobs from the queue > >> seems to be > >> the only way to get these print queues working properly again. > >> > >> While the LPRng print queue is stalled, MS Windows is able to print > >> directly to the Linksys devices. > >> > >> Any help would be greatly appreciated. > >> > >> We are running Debian/Sid - LPRng-3.8.25. > >> > >> Here is my printcap entry and lpq output for this printer > while it is > >> stalled: > >> > >> .common: > >> :sd=/var/spool/lpd/%P > >> :lf=/var/spool/lpd/%P/log > >> :af=/var/spool/lpd/%P/acct > >> :sh:mx=0:mc=0 > >> > >> sea-ps-24-p1|lp1 > >> :cm=(Back Office)Okidata ML391 Plus @ SEA-PS-24 on Port 1:\ > >> :tc=.common > >> :[EMAIL PROTECTED] > >> > >> > >> # lpq -P sea-ps-24-p1 > >> > >> Printer: [EMAIL PROTECTED] '(Back Office)Okidata ML391 Plus @ > >> SEA-PS-24 on Port 1' (dest [EMAIL PROTECTED]) > >> Queue: 8 printable jobs > >> Server: pid 7168 active > >> Unspooler: pid 7322 active > >> Status: waiting for subserver to exit at 13:10:09.756 > >> Rank Owner/ID Class Job Files > >> Size Time > >> stalled(1757sec) [EMAIL PROTECTED] A 792 > smbprn.001697.L2b079 19804 > >> 12:22:46 > >> 2 [EMAIL PROTECTED] A 815 > smbprn.001698.rSE4Xe 19804 > >> 12:23:14 > >> 3 [EMAIL PROTECTED] A 836 > smbprn.001699.IMePPy 19804 > >> 12:24:47 > >> 4 [EMAIL PROTECTED] A 12 > smbprn.001700.FtF9lg 19804 > >> 12:34:00 > >> 5 [EMAIL PROTECTED] A 38 > smbprn.001701.izWmGI 19804 > >> 12:36:21 > >> 6 [EMAIL PROTECTED] A 57 > smbprn.001703.gyxopI 19804 > >> 12:36:54 > >> 7 [EMAIL PROTECTED] A 72 > smbprn.001705.0U21rL 19804 > >> 12:38:21 > >> 8 [EMAIL PROTECTED] A 733 > smbprn.001710.lE0LvC 10024 > >> 13:07:29 > >> (LPD Server): > >> (P1)STATE: Idle > >> TYPE: Parallel > >> PRINTER STATUS: On-Line > >> > >> > > Shawn, > > > > Should [EMAIL PROTECTED] instead of [EMAIL PROTECTED] > > > > "(P1)STATE: Idle" Makes me think that... > > > > I have a USB printer on a Linksys printserver, > > and the printer is listed as "\\PRINTSERVER\P1". > > It has 3 logical ports available, by I don't > > know what they'd be labeled. > > > > Jim > > > > > Hi Jim, > > Thanks for reading my post. I was beginning to wonder if my > question was > covered somewhere obvious that I must have overlooked a dozen > times trying > to figure this one out. > > I didn't test useing P1 instead of L1(logical port 1) for the > print queue > name, but Im pretty sure that is not the problem. I believe > the problem > is that the Linksys print servers are complete pieces of > SH*T! I put an > Intel NetExpressPro print server in one of the Linksys' place > and it works > with no problems. In fact where, with the Linksys, when I > spool 6 small > jobs(printcap file with 8 entries) one right after the other, > they stack > up in LPRng's spool and then hang that print queue...with the > Intel the > jobs don't hang around in the queue long enough to be > detected by lpc or > lpq....they get fired off to the Intel unit and print out with no > problems. > > It would be interesting to know how this Linksys device could > cause the > LPRng queue to stall.....anyone? > > Cheers, > > shawn > Shawn,
I'm not sure if this info was included with your printserver; it's from http://www.linksys.com/support/support.asp?spid=18 and applies to the EPSX3 mainly, with comments re: the PPSX1 included. You're right to use L1, not P1. Sorry 'bout that! Try modifying your printcap entry to this and see what happens: :rm=SEA-PS-24 :rp=L1 Maybe with the socket support? :rm=SEA-PS-24 :rp=4010 or :lp=SEA-PS-24%4010 ---------------------------------------------------------- TCP/IP Setup for Linux & Unix ---------------------------------------------------------- Note that the examples below should not be used verbatim, as your system's configuration will certainly be different from ours. Your IP address may be different, and you can substitute another name for printserver in the examples below. These instructions are provided for your convenience only. Linksys does not provide Technical Support by telephone for Unix or Linux at this time. If you have difficulties getting the installation to work, try using the Linksys listserver by sending e-mail to: [EMAIL PROTECTED] and include the words SUBSCRIBE SUPPORT-HELP in the body of the e-mail. The 10/100 1-Port and 3-Port PrintServer is supported under all flavors of Linux and Unix via the TCP/IP protocol that use LPR/LPD printing. Follow the example below to get the PrintServer up and running with your system. /etc/hosts 10.0.0.10 printserver # linksys printserver An IP address can be assigned to the unit using arp/telnet or arp/ping or rarp protocols. For rarp: You need to create /etc/ethers if it does not exist. Get the ID number off the bottom of the PrintServer unit. It will usually have a number like SCXXYYZZ or SCCXYYZZ. Convert the number into a MAC address by combining them with the prefix numbers 00:c0:02. For example, if the number is SCXXYYZZ, then the MAC address will be 00:c0:02:XX:YY:ZZ. If the number is SCCXYYZZ, then the MAC address will be 00:c0:02:CX:YY:ZZ. In both of these examples, be sure to replace XX, YY, and ZZ with the numbers from the bottom of the PrintServer unit. /etc/ethers 00:c0:02:XX:YY:ZZ printserver Verify that rarp is running. On System V type : ps -ef | grep rarpd For BSD type : ps -ax | grep rarpd If rarp is not running, type rarpd -a Note: The PrintServer will only use rarp if the IP address is 0.0.0.0 in the PrintServer unit. Using arp and telnet: Use the following commands after creating the proper entries in /etc/hosts Arp -s printserver 00:c0:02:XX:YY:ZZ Next issue the command : ping printserver You should get back normal ping replies. Using telnet printserver: Telnet commands are: monitor, followed by exit. Use Ctrl-C to stop the monitor command. To store the IP address as permanent using tftp do the following: tftp printserver tftp> get CONFIG tftp> quit Edit CONFIG with vi or some other text editor: 0001 BOX_NAME: SCXXXXXX 4000 IP_ADDR: 0.0.0.0 4001 GATEWAY: 0.0.0.0 4002 MASK : 0.0.0.0 Make the changes needed and then do the following: tftp printserver tftp> put CONFIG tftp> get RESET Wait for the red light on the printserver to go out and then issue: tftp> quit Your printserver is now configured. Next, make an entry in /etc/printcap for each port on the print server: /etc/printcap # hp printer on lpt1 of print server hp|Remote Printer1|lp1:\ # this line can be anything you want :lp=:\ :rm=printserver:\ :rp=L1:\ # L1 for LPT1, L2 for LPT2, L3 for LPT3 :sd=:\ # usually something like /var/spool/lpd :mx#0: # bubblejet printer on lpt2 of print server bj|Remote Printer2|lp2:\ # this line can be anything you want :lp=:\ :rm=printserver:\ :rp=L2:\ # L1 for LPT1, L2 for LPT2, L3 for LPT3 :sd=:\ # usually something like /var/spool/lpd :mx#0: # dot matrix line printer on lpt3 of print server lp|Remote Printer3|lp3:\ # this line can be anything you want :lp=:\ :rm=printserver:\ :rp=L3:\ # L1 for LPT1, L2 for LPT2, L3 for LPT3 :sd=:\ # usually something like /var/spool/lpd :mx#0: The above example is for EPSX3, the Linksys 3-Port PrintServer. The same can be used for PPSX1, our single port model, except that only L1 is valid for the rp line. To get your printers started, you may need to issue: lpc start hp lpc start bj lpc start lp For OS's that need direct socket support, the following is a correlation between sockets and ports: LPT1 is socket 4010 LPT2 is socket 4020 LPT3 is socket 4030 ---------------------------------------------------------- Hope this helps, Jim ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
