Issues with Packer building across subnet. PfSense

_This issue was originally opened by @Iluvitari as hashicorp/packer#8844. It was migrated here as a result of the [Packer plugin split](https://github.com/hashicorp/packer/issues/8610#issuecomment-770034737). The original body of the issue is below._

Hi,

I am basically using packer to deploy jumpboxes in a lab environment.
The lab environment:
- My local laptop with 1 physical interface and 1 virtual interface created by virtual box with ip address of 192.168.56.2

- My PfSense box built on virtual box with wan set to communicate with my physical interface for internet and then it has a lan adapter. These are "nic1" "bridged adapter" and "nic2" "host-only adapter". The host only adapter is set to have a subnet of 192.168.56.1/24. So my virtual interface is on this subnet.

- I have an AD Windows server 2016 box for DHCP, DNS and AD with ip address of 192.168.56.3

So with this my default gateway is 192.168.56.1 and my dhcp/dns should be being provided by 192.168.56.4. I have currently disabled firewalls on the AD server and I have also enabled Any any firewall rules on wan and nat for the pfsense router. SO anything should be able to come through my pfsense in theory.

My issue:
I am able to build a virtual machine with packer that lies on the subnet. BUT winRM is unable to communicate at all. Even though my local machine is sitting on the same subnet. How do I fix this?

Is it because its running of the virtual subnet? Am I able to make winrm talk through the virtual interface?

When I run log I get this message:
connection error: unknown error Post https://127.0.0.1:4327/wsman: dial tcp 127.0.0.1:4327: connectex: No connection could be made because the target machine actively refused it.

I have attatched my log file:
[packerlog3.txt](https://github.com/hashicorp/packer/files/4290365/packerlog3.txt)