Posted by Bruno Biancucci on March 18, 2011 at 12:59:45:
In Reply to: CometAnywhere printing?...> posted by Tom Fulton on March 17, 2011 at 11:38:10:
I've done it a slightly different way than the VPN solution. Setup all the printers on the CA Host using networked printers. For printers that don't have a tcp port, get a print server that will convert parallel port to tcp. For local printers this is easy. For those at remote locations, you'll need to get fancy with the port setting of the print driver at the CA Host server (the default is 9100), so I used 9101, 9102, 9103... and port forwarding on the firewall. If you only have one remote printer at a location, the standard port 9100 would work just fine and any firewall on the market will also work. I normally use NOIP to keep track of a remote location(s). The firewall at the remote location would have to listen for incoming tcp connections on port 9100 (or 9101, 9102 or what ever) and NAT them back to the default port 9100. Note, non of the 'out of the box' firewalls like Linksys, dlink, netgear will allow for NAT; you'll need a higher end firewall or a Linux firewall will do the trick.
Cool part about this setup, is that any CA session can print to any printer found on the CA host. So you can have reports printed to any/all locations from within your program.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.