"Lee Jefferies" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I need some clarification!
>
> Let me say first I am using Windows Server 2008. When I configure
> Routing and Remote Access, I must specify two NIC's. One is for the
> network interface: automatically sets up filters that only allow
> VPN-related traffic, the other one is an interface over which DHCP,
> DNS and WINS configuration is obtained. I selected the wrong order my
> first attempt and the results were a forced reboot.
>
> The implication is that you must have multiple NIC's.
>
> I read the Articles on multiple adapters, but I wonder where they fall
> with the new VLAN technologies.
>
> Now I do have a external firewall that supports VPN, but you have to
> give the address of a RADIUS server, which in WS2008 means you have to
> configure VPN anyway.
No, you do not need two NICs to set up RRAS as a remote access server.
That setup is only used if the RRAS server is directly connected to the
Internet. If your server is on a private LAN behind a firewall you simply
configure your RRAS server as a remote access server. You use a different
option in the setup wizard.
When you set it up for remote access you can test it by connecting from
one of your LAN workstations. (VPN will work over any IP connection).
When this is working you can configure your firewall to forward the VPN
traffic to the RRAS server on the LAN. The VPN client connects to the public
interface of the firewall, but the VPN tunnel is created between the client
and the RRAS server on the LAN.
Are you sure that you need to configure your server as a RRAS server to
run it as a RADIUS server? I have not looked too closely at this in 2008,
but in 2000 and 2003 you could configure it as an IAS server which is fully
RADIUS compatible. I believe you can do much the same in NPS.
http://www.windowsnetworking.com/art...cy-Server.html