Digitus Print Server

[Astrea Busbin]

Withthe "Fast Ethernet Printserver" you can easily connect your printer to your PC. This product not only supports the well-known network and printing protocols, but also peer-to-peer and server-based printing. It is compatible with all common operating systems, be it Windows, Mac or Linux. It also supports web-based management, the Windows configuration utility and the SNMP protocol. And thanks to its simple installation, it should be up and running as quickly as possible!

I just want to be able to lpr a file from Fedora to an LPD server using only an LPR client (No full CUPS install). I tried cups-client (dnf install cups-client), which installs lpr binary and I added the remote print servers to my /etc/printcap, but I get Bad file descriptor error whenever I run lpr.

One thing to remember when using a client-only function like rlpr is that if it is a non-interactive batch process or something similar generating the print request, and there is a network outage between client system and printer/spooler, at best the listing will be lost, and at worst the batch job will fail.

This is one of the reasons for local daemon functions like CUPS/LPRng/classic LPD, where the lpr client actually talks to a local daemon listening to 127.0.0.1:515 or :631, and proxies the request via that daemon: the daemon provides store-and-forward.

No network outage or glitch can possible take down that process. The client submits the print request successfully, it is accepted by that local daemon, and then the lpd/whatever daemon continues trying to forward the listing to its final destination until it achieves success. The listing is not lost, and meanwhile the batch job/whatever continues on successfully.

Fedora uses CUPS as print server, handling both local and remote printers. As far as I know, there are no native packages which talk the (legacy, deprecated) LP or LPR protocols, and haven't been for quite some time. CUPS is the de facto printing standard nowadays. Search OpenPrinting for suggestions on handling your particular beast.

Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.

After you purchase a TP-Link print server and set it up in your network, sometimes due to incorrect settings or something else, you may find it not working properly, then how to troubleshoot for varieties of situations?

We have updated our Policies. Read Privacy Policy and Terms of Use here.

This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .

With the DIGITUS 2-Port USB 2.0 Wireless Multifunction Network Server you can operate USB devices without connecting them directly to your PC or notebook. Reach your USB devices anywhere in your local network, synchronize smartphones or install print drivers remotely. You can also access the memory of compatible USB devices via the network, such as multifunction printers or external hard disks. Speeds of up to 300Mbps are possible with this network server and all USB-enabled devices can be integrated wirelessly. You can configure the connected end devices and the wireless multifunctional network server extensively via the user-friendly web interface. Turn any compatible USB device into a network device and operate it remotely!

I do not believe restarting the spool is an option without effecting the other printers and we have Hold printer for a specific non windows printing friendly application, in which I can not loose the jobs for.

Restarting the print spooler generally doesn't drop print jobs it just stops accepting new ones. End users will notice but it won't be as bad as silently dropping a print job. In general I would say it is safe to restart the service on the fly.

a. The print spooler won't stay started as long as the corrupt print job is present and the target printer is on

b. the print spooler won't let you delete the corrupt job through the GUI if the spooler is stopped

c. the printer won't print any other job until the corrupt job is completed or deleted.

I can't promise you that your situation matches this experience but I think its worth considering the behaviour observed and the implications to how the process of printing/print spooling hands things along.

edit: In the opposite take to Evan's manipulation of the spool files. You can use the print queue on Windows (start - settings - printers or start - printers) and delete the job from the print queue using the Document menu - Cancel option.

The key is in his way of dealing with it the spool service has to be stopped in dealing with it my way the spooler has to be started. If you have physical access to the printer and it is convenient to turn it off you can use my method. If you don't have access to the physical printer you can use his method.

Bouncing the spooler service is the only viable choice that I'm aware of. In my experience, some jobs get "jammed" in a queue so "severely" as to require stopping the spooler server, clearing the files that represent the jobs out of the %SystemRoot%\System32\Spool\Printers folder, and re-starting the spooler service.

You're not going to lose any jobs that are already queued for other printers by bouncing the spooler service (you can demonstrate this yourself on another server or a client-- pause a printer, put some jobs in queue, and stop / restart the spooler serivce), but if you find that you have to go the route of deleting job files from the spool directory you'll have a hard time locating them amid the other spooled files for jobs you intend to keep.

(As an aside: Microsoft could do a lot of enhancemnet of the print spooler service, IMO, to alleviate situations like you're seeing. The print spooler service has languished in a state of relatively little enhancement throughout the last few releases of Windows. Printing isn't sexy, but it's often business critical.)

Each print job is represented in the spool directory by a ".SPL" file (containing the print job data in EMF or raw format) and a matching ".SHD" file, containing "header" information about the job. This header information file contains the details about which printer the job is being sent to.

Unfortunately, the format of the ".SHD" file is officially undocumented (see for some reverse engineered documentation), so figuring out "which file is which" in the spool directory and deleting only the "corrupt" print jobs is very difficult, at best. From what I can see, the destination print queue name is in that "SHD" file as a uncode string, so I suppose it would be possible to cobble together a script using command-line tools line "strings" and "findstr" to grovel thru all the ".SHD" files to find jobs destined for the "problem" printer and delete them while leaving jobs bound for other printers untouched.

LPR

Short for line printer daemon/line printer remote, a printer protocol that uses TCP/IP to establish connections between printers and workstations on a network. The technology was developed originally for BSD UNIX and has since become the de facto cross-platform printing protocol. The LPD software typically is stored in the printer or print server and the LPR software must be installed in the client device. The LPR client sends the print request to the IP address of the LPD printer/server, which in turn queues the file and prints it when the printer becomes available.

Server-Based Printing

In a Server-based Printing architecture, network clients send printing jobs to a server, allowing the server to queue printing jobs from multiple clients. The server then connects with print server unit to execute the various printing jobs. Server-based Printing alleviates network clients printing wait time and allow clients to seamlessly send simultaneous printing jobs, hence increasing your networks performance and efficiency.

Kaynak:

Bu rnn tanıtımında kullanılmak zere aşağıdaki grselleri kullanabilirsiniz. Grselleri bilgisayarınıza kaydetmek iin grselin altında bulunan bağlantıya sağ tıklayıp "Hedefi farklı kaydet"e tıklamalısınız.

Hey everyone, I am looking for an ethernet to USB print server to use with a Zebra 420d label printer. I need to be able to print to a label printer in a lab in a remote desktop environment, so this needs to be able to work with a Windows 2008 server. Yes, I know that I should have specified the model with built in ethernet when we got the printer. Any suggestions?

3a8082e126