VirtualBox - Windows Server 2012 R2 Domain Controller - Windows 10 - pfSense

[networknovice]

For software testing purpose, I am trying to duplicate one of our customers network environment. Our customer has a Windows Server 2012 R2 acting as Domain Controller as well as a couple of Windows 10 computers used as Workstation. Our software resides on the server and should be accessible from the Workstations.

In order to duplicate their configurations, within my VirtualBox (v. 6.0.4) environment, I created three virtual machines running the following software:

• pfSense 2.4.4-Release-p2
  ** Network Adapter #1: NAT
  ** Network Adapter #2: Internal Network (pfSense Network)
  ** WAN (wan) -> em0 -> v4/DHCP4: 10.0.2.15/24
  ** LAN (lan) -> em1 -> v4: 10.0.0.254/24

• Windows Server 2012 R2
  ** Network Adapter #1: Internal Network (pfSense Network)
  ** Internet Protocol Version 4:
  ** IP Address: 10.0.0.11
  ** Subnet masks: 255.255.255.0
  ** Default gateway: 10.0.0.1
  ** Preferred DNS server: 127.0.0.1

• Windows 10
  ** Network Adapter #1: Internal Network (pfSense Network)
  ** Internet Protocol Version 4:
  ** IP Address: 10.0.0.12
  ** Subnet masks: 255.255.255.0
  ** Default gateway: 10.0.0.254
  ** Preferred DNS server: 10.0.0.1

I am able to launch all three virtual machines and run our software from either the Server directly or from the Workstation. However, I am unable to access the Internet from either the Server or the Workstation.

I am a total novice when it comes to networking and don't know what else to do. Any advice on how to solve and/or troubleshoot my problem would be greatly appreciated.

Thank you.

[KOM]

Make the pfSense VM's em0 a bridged adapter, not NAT. Then it will pretend to be a real client on your network and pull an IP address from your real router.

[networknovice]

Thanks for the suggestion.

As suggested, I set Network Adapter #1 to 'Bridged Adapter.' Then I relaunched my three virtual machines. On my 'pfSense 2.4.4-Release-p2' vm, my new WAN is em0 is now pulling an IP address from my real router. However, I still do not have Internet access from within the server and/or the workstation.

[KOM]

This is to be expected based on your configuration being totally wrong. Gateway on LAN should be your pfSense LAN IP 10.0.0.254, not this 10.0.0.1 address. DNS can either be pfSense or your Windows Server.

[networknovice]

@KOM Once again, thank you very much for your invaluable input.

Per your suggestion, I replaced my 'Windows Server 2012 R2' default gateway address of '10.0.0.1' with '10.0.0.254' (my pfSense LAN IP).

Problem solved: I now have Internet access from both my server as well as my workstation and our software is accessible from both as well.

Thank you.

[KOM]

Glad it's working for you.