PAT is port address translation or port forwarding.
If you have a relatively static IP, you have a shot. And you do not have to expose your printer to the whole internet, only to the public IP address range at work.
If your firewall is flexible enough for PAT and a policy to restrict access by IP, here are your two options:
1) you add an IP printer port (pointing to your home IP) and driver to your corporate print server, and then your users simply add that printer to their work desktops profiles, work VMs, whatever they use to work remotely - just like they would any printer in the corporate environment. This is what I would recommend, because then you only have to set it up once - and the print server will distribute the driver for you automatically when folks add it to their profile.
2) you add an IP printer port (pointing to your home IP) and print driver to every desktop or VM or whatever your users use to work remotely.
Then you create a policy on your home firewall that only allows your corporate public IP range to access your device.
These folks at home will not be sending jobs from their homes, they will send the jobs from the corporate network where presumably they have a remote presence from home. You didn't specify how they work from home, so I am assuming they use Citrix Xen, VMWare Horizon, RDP etc to remotely control a Windows session that exists on the corporate network, as this is pretty typical for remote workers.
However if they work directly on their home computers, with no remote presence at the office, and they have Windows - then option 2 would also work for them on their home computers. It may also work for Mac but I am Mac illiterate.
If you have a relatively static IP, you have a shot. And you do not have to expose your printer to the whole internet, only to the public IP address range at work.
If your firewall is flexible enough for PAT and a policy to restrict access by IP, here are your two options:
1) you add an IP printer port (pointing to your home IP) and driver to your corporate print server, and then your users simply add that printer to their work desktops profiles, work VMs, whatever they use to work remotely - just like they would any printer in the corporate environment. This is what I would recommend, because then you only have to set it up once - and the print server will distribute the driver for you automatically when folks add it to their profile.
2) you add an IP printer port (pointing to your home IP) and print driver to every desktop or VM or whatever your users use to work remotely.
Then you create a policy on your home firewall that only allows your corporate public IP range to access your device.
These folks at home will not be sending jobs from their homes, they will send the jobs from the corporate network where presumably they have a remote presence from home. You didn't specify how they work from home, so I am assuming they use Citrix Xen, VMWare Horizon, RDP etc to remotely control a Windows session that exists on the corporate network, as this is pretty typical for remote workers.
However if they work directly on their home computers, with no remote presence at the office, and they have Windows - then option 2 would also work for them on their home computers. It may also work for Mac but I am Mac illiterate.






Comment