I'm running VMWare ESXi Free on a rented box.
I have 2 physical NICs, 1 connected to the Internet, one connected to the Private Network in our DC.
Each NIC is connected to a vSwitch and each vSwitch has a Management network and VM network (LAN/WAN).
Here is the diagram: https://www.dropbox.com/s/9ceg5k4jjczkvlt/vmWare%20Networking%20Config.png
I setup the pfSense VM using the guide for vmWare in the docs. https://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5
During the pfSense Setup I set my WAN interface to one of my free Public IPs and did the same with a Private IP for the LAN interface. The upstream Gateway address is provided by the DC and was typed verbatim.
The DC opened up an SSL VPN for me to connect to the private network. Once connected to the VPN, I can access the ESXi host using its Private IP (10.34.251.163), but I always get "Connection Reset" when trying to connect to the pfSense VM via its Private IP (10.34.251.164). When I connect to the VPN I'm shown as connecting to 10.2.1.21 and I'm trying to access 10.34.251.164 (/27), could this be part of the problem?
pfSense cannot PING out to Google as well currently, however pinging Google's IP works just fine. I can ping the ESXi Host and I can Ping pfSense from inside pfSense as well.
Looking in pfTop while trying to access the Web Panel over private IP, I can see the incoming TCP connection, but as I said the Browser tries to connect for a little while then says connection reset.
At this point I have no idea what to do next and any help is appreciated.
Update:
I saw this: Virtual pfSense Appliance on VMWare Host and made the changes suggested by the answer (setting promiscuous mode to allow) and I can see the incoming traffic from my VPN IP to the pfSense private IP. But I cannot access the Web GUI still. (my pfTop: https://www.dropbox.com/s/fzow6i02ijim748/pfTop.png)
Best Answer
Does it have gas in it? Can I give you a dumb answer?
Okay, then: 1. go into VMclient, open a console for pfsense and restart the PFS web interface.
A default VMware hypervisor has port 443 open, so there should not be any problem with the VMware firewall unless you tinkered with it.
While you are there, did you check the MAC assignment of the card to the LAN IP?
Can PFS ping the IP of the client trying to https: into the PFS web interface? Check cables too. Nothing feels dumber than spending hours to debug when the physical layer is the fault. It happens.
If you did all this, check the PFS logs for a TCP connection, if you see a ICMP connection and UDP but not TCP, then is a certificate required?