Virtual Private Network
- Can I use StarJet to output to a remote printer which is not configured on the server?
- Do I have to configure all the printers that I may possibly need on every server?
Those are the kind of questions EDP managers have to ask themselves when setting up a VPN (Virtual Private Network). Much software, regardless of its relationship to the printing process, relies on the so called « printer driver ». How these drivers work is important in understanding the treatment of complex printing operations. This is the software that translates Windows commands into intelligible targeted printer commands, which is pretty cool … but as each individual type of printer is linked to a different driver, a multiplicity of configurations may be required … and that’s not quite so cool!
StarJet never uses such drivers when generating and printing documents. StarJet itself generates all printer commands directly, using PCL language. And as this is used by the overriding majority of printers available on the market today, it builds files that are the same … for any printer, no matter which one is targeted.
This technology holds several key advantages :
It enables StarJet to drive printers at their nominally rated speed,
No ‘compiling’ is required to print. With conventional printing requests this is unavoidable as it’s based upon each individual printer and its’ corresponding driver,
it provides a method that avoids having to configure each and every printer for each one of your servers.
And, last but not least, it makes StarJet fully compatible with any printer available on a Virtual Private Network.