We have a Windows Server 2008 R2 box. It has one NIC, with the address 192.168.0.2. We set up RRAS, enabled VPN protocols, and told it to use a static address pool, 192.168.0.224-239. On our router, we set up a public IP to be forwarded to .224. This used to work, but now after the first reboot it doesn't. I think the cause of the problem is that the PPP adapter is missing. I've read somewhere else that the PPP adapter is not created until a user connects. But where are they supposed to connect to if it's not there? Nothing assumes the .224 IP currently, no replies from there at all. Sadly I don't remember how the PPP adapter was created when it did work.
I'm guessing now that we did it all wrong, and the clients are not supposed to connect to the PPP adapter at .224, but a preexisting, physical adapter, like at .2. So the questions are: Is my guess right? If it's not, then how do I create the PPP adapter? If it is, then why did it work before, does the server accept connections from the .2 IP and the PPP adapter's .224 IP at the same time?
So if I need a fixed, dedicated IP for the VPN, let's say I want it to be .3. The HTTPS port on the .2 IP is used by a web server, and I need SSTP, which uses the same port. I know I can assign multiple IP addresses to an adapter, but I can't find a way to assign a single IP to VPN, only an entire adapter, so I'm guessing that it would listen on all IP's of the adapter, not only .3 but .2, too. Am I forced to buy a new NIC, or can I create a new adapter for the same physical NIC, like an alias or something, so that I can use the .2 IP on the real adapter, the .3 IP on the virtual one, and assign only the virtual adapter to RRAS?