SSL-Explorer’s Community Version doesn’t give you full network access like some commercial SSL VPN solutions, but that shouldn’t stop you from printing.
This assumes that you’ve got some sort of network-enabled printer – such as a HP with an internal JetDirect card. From memory, if you’ve got an external JetDirect device with multiple physical Parallel or USB ports, the network port number changes according to the physical port used.
The setup is as follows:
- Go to Access Control, Policies, and create a new policy. Assign some users to the policy if you like.
- Go to Resources, SSL Tunnels, and create a new Tunnel with the following properties:
- Source Interface: 127.0.0.1
- Source Port: 9100
- Destination Host: Printer’s IP Address
- Destination Port: 9100
- Auto Start: Ticked, if you want the tunnel to be enabled as soon as the Java client starts
- Type: Local
- Assign the policy that was created in step one to this tunnel.
That’s it for the SSL-Explorer side of things. In Windows, make sure you’ve got the driver for your printer handy, and follow these steps:
- Go to Control Panel, Printers and Faxes, and add a new Local Printer (untick ‘Automatically Detect’ if it’s ticked)
- Create a new Standard TCP/IP Port
- As the address for the port, enter 127.0.0.1
- Click ‘Custom’, and leave the settings as:
- RAW mode
- Port 9100
- IP 127.0.0.1
- Point the Wizard to the correct printer driver, and finish the installation. If you want to print a test page, make sure that the SSL Tunnel is activated first. This can be verified by right-clicking on the SSL client’s tasktray icon and selecting ‘Tunnel Monitor’. You should see and entry for port 9100.
The way this works is that once the tunnel is enabled, it listens on 127.0.0.1 on the port you’ve specified, and redirects traffic to the IP and port specified on the network behind the SSL VPN.
In addition to this, you can add a ‘Web Forward’ of type ‘Tunneled proxy’ to the printer’s port 80 if you’d like to check up on the printer’s status via the web interface. You can then add this ‘Web Forward’ to the policy created in step 1.