RRAS likes 2 network cards. One on the private network, one on the internet.
Having said that, I have configured W2K using a single card. I tried to walk someone through the process a few weeks ago, but found I couldn't remember how to get RRAS to deal with a single card. Since then, it has come to mind that the work around is to bypass the RRAS console and use the same procedure used to configure a VPN server in W2K Pro. Note that I have not had a chance to get back to that one, and I don't have W2K server on site anymore, so I won't promise this works. Again, something does work, it can be done, and I think this is the way, working from memory.
Start --> Network Connections --> New connection.
Click Next on the welcome dialog box.
On the connection type box, mark Accept Incoming Connections and click next.
On the devices page, unmark all devices. Yep, that's right. None of them should be marked. Doesn't matter that your internet connection isn't there. Click next.
Should get the Incoming Virtual Private Connection box next, mark the Allow Virtual Private Connections box and click next.
Now you should have the Allowed Users dialog, mark all accounts that are to be allowed access and click next.
On the networking components page, select the protocols you need. Make sure that you at least have TCP/IP maked.
Highlight TCP/IP and click properties. The 'Allow callers to access my local network' will enable routing from the VPN to your local network, use the option that suits you best.
In TCP/IP address assignment, the DHCP option has some problems so you will have better luck marking the 'specify TCP/IP addresses box' and entering a range of addresses. If you want to route back to your local LAN, you should be RFC compliant (192.168.1.0 net address with a 255.255.255.0 mask on your network) and select addresses from the same network for the VPN. If DHCP is running on the network, make sure the addresses are excluded from the pool. You must have at least two addresses even though you only have one connection available as the server side takes one. Four or more is a good idea as the addresses are not released immediatly upon a disconnect. If something happens to break the connection, you may not be able to get back in right away.
The box for 'Allow calling computer to specify it's own address' will do exactly what it says, however the address does have to be an available address from the specified pool. If you have the DHCP box marked, the address must be available from the DHCP server. Either way, not a good idea if you can help it.
Should be ready to hit OK on the TCP/IP properties box.
Adjust any other components/protocols as needed and hit next on the networking components dialog.
The next box is a teaser, you can't really change the Incoming Connections name, so hit finish.
Guess what!?! Your finished, as indicated by the finish button. You can go to Networking connections and adjust the properties of your incoming connection as needed.
Sorry, no screen shots or anything of the sort with this one, but it should get you going.
Also, note that this is a cut'n'paste deal from instructions for W2K Pro, so some things might be just slightly different. I'll restate again, I don't have a machine to try this with, and my memory isn't what I would like it to be, so no promises. Post back if it doesn't fly.
