I'm using Windows Server 2008 R2. The server is running RRAS, and is configured for both VPN and NAT.
The server has two NICs, BE (10.1.0.0/16 network), and FE (two public IP address assigned). The NAT is setup with the BE as the internal, and the FE as the internet-facing network.
The server can access both the internet and the BE network just fine, but machines on the BE network are unable to access the internet. They can resolve the IPs (so DNS is working), but they get request timeout when I ping any public IP address. The machines on the BE network all use the server as their default gateway.
To enable NAT, I simply added the FE, BE, and Internal interfaces to the NAT list in the RRAS mmc. I also tried specifying the address pool in the FE properties under the NAT section in the RRAS mmc, but this setting didn't seem to make a difference.
What am I missing? Is there a good way to debug these issues?
The server has two NICs, BE (10.1.0.0/16 network), and FE (two public IP address assigned). The NAT is setup with the BE as the internal, and the FE as the internet-facing network.
The server can access both the internet and the BE network just fine, but machines on the BE network are unable to access the internet. They can resolve the IPs (so DNS is working), but they get request timeout when I ping any public IP address. The machines on the BE network all use the server as their default gateway.
To enable NAT, I simply added the FE, BE, and Internal interfaces to the NAT list in the RRAS mmc. I also tried specifying the address pool in the FE properties under the NAT section in the RRAS mmc, but this setting didn't seem to make a difference.
What am I missing? Is there a good way to debug these issues?