Configure VP on Server 2003 with single NIC

Can someone point me to a resource for configuring Windows Server 2003
Routing and Remote Access services on a box with a single NIC card? The
wizard will not run to completion if there is not at least 2 NIC cards.

Environment is a small shop, single 2003 server for active directory, file
and print; single LAN segement. Not going to add a second NIC with public IP
address since Internet access is managed by router managed by ISP. Router
port forwards PPTP traffic to locally assigned IP address on server NIC.
Users want to be able to access server resources remotely from home, and when
traveling.

I have tried using the custom configuration from the RRAS setup wizard,
selecting VPN and IP Routing. However, it does not allow me to go into the
Computer Management interface afterwards and set up ports, protocols, and
authentication policies as one would normally do after the wizard has run to
completion.

Thanks.
--
Duke Fleming
Systems Engineer
Fleming Associates Inc.

quoted from http://www.chicagotech.net/vpnsetup.htm
How to setup VPN server on 2003 server

You may have two options to setup VPN server on Windows 2003. 1) Create an
incoming networking connection if you have small network or you want to
setup one PC to PC VPN; 2) If you have large numbers of incoming connections
on a server that operates as part of a distributed network or as a domain
controller, you should use RRA to create a VPN server.


Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on
http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
"Duke Fleming" <(E-Mail Removed)> wrote in message
news:937354D3-87B3-4CB7-91C7-(E-Mail Removed)...
> Can someone point me to a resource for configuring Windows Server 2003
> Routing and Remote Access services on a box with a single NIC card? The
> wizard will not run to completion if there is not at least 2 NIC cards.
>
> Environment is a small shop, single 2003 server for active directory, file
> and print; single LAN segement. Not going to add a second NIC with public
> IP
> address since Internet access is managed by router managed by ISP. Router
> port forwards PPTP traffic to locally assigned IP address on server NIC.
> Users want to be able to access server resources remotely from home, and
> when
> traveling.
>
> I have tried using the custom configuration from the RRAS setup wizard,
> selecting VPN and IP Routing. However, it does not allow me to go into
> the
> Computer Management interface afterwards and set up ports, protocols, and
> authentication policies as one would normally do after the wizard has run
> to
> completion.
>
> Thanks.
> --
> Duke Fleming
> Systems Engineer
> Fleming Associates Inc.

As you said, the standard wizard assumes you have two NICs. Use one of
the other wizard options to enable remote access on the server. Test the
setup locally (ie from a LAN client) to debug settings and policies. When
you can connect locally, forward the VPN port from your router to the
server's LAN IP and try to connect from a remote client to the router's
public interface.

Duke Fleming wrote:
> Can someone point me to a resource for configuring Windows Server 2003
> Routing and Remote Access services on a box with a single NIC card?
> The wizard will not run to completion if there is not at least 2 NIC
> cards.
>
> Environment is a small shop, single 2003 server for active directory,
> file and print; single LAN segement. Not going to add a second NIC
> with public IP address since Internet access is managed by router
> managed by ISP. Router port forwards PPTP traffic to locally
> assigned IP address on server NIC. Users want to be able to access
> server resources remotely from home, and when traveling.
>
> I have tried using the custom configuration from the RRAS setup
> wizard, selecting VPN and IP Routing. However, it does not allow me
> to go into the Computer Management interface afterwards and set up
> ports, protocols, and authentication policies as one would normally
> do after the wizard has run to completion.
>
> Thanks.

When selecting the Remote Access selection from the RRAS setup or Configure
your Server wizards, it forces you to select either VPN or dial-up as the
Remote Access configuration. Then the wizard fails on the single NIC
configuration.

NT Server 4.0 and Server 2000 allow VPN configuration for a single NIC
machine; why did Microsoft change this capability for Server 2003? This
precludes implementing a simple, cost-effective VPN solution for small
businesses to use their Windows Server as a VPN gateway. BAD business
decision.

Still looking for a solution configuring Server 2003 since rolling back to
Server 2000 is not an option for the customer.
--
Duke Fleming
Systems Engineer
Fleming Associates Inc.


"Bill Grant" wrote:

> As you said, the standard wizard assumes you have two NICs. Use one of
> the other wizard options to enable remote access on the server. Test the
> setup locally (ie from a LAN client) to debug settings and policies. When
> you can connect locally, forward the VPN port from your router to the
> server's LAN IP and try to connect from a remote client to the router's
> public interface.
>
> Duke Fleming wrote:
> > Can someone point me to a resource for configuring Windows Server 2003
> > Routing and Remote Access services on a box with a single NIC card?
> > The wizard will not run to completion if there is not at least 2 NIC
> > cards.
> >
> > Environment is a small shop, single 2003 server for active directory,
> > file and print; single LAN segement. Not going to add a second NIC
> > with public IP address since Internet access is managed by router
> > managed by ISP. Router port forwards PPTP traffic to locally
> > assigned IP address on server NIC. Users want to be able to access
> > server resources remotely from home, and when traveling.
> >
> > I have tried using the custom configuration from the RRAS setup
> > wizard, selecting VPN and IP Routing. However, it does not allow me
> > to go into the Computer Management interface afterwards and set up
> > ports, protocols, and authentication policies as one would normally
> > do after the wizard has run to completion.
> >
> > Thanks.
>
>
>

They did change the wizard (for the better in my opinion) and the option
to configure on one NIC is still there. It just has a different name.

Duke Fleming wrote:
> When selecting the Remote Access selection from the RRAS setup or
> Configure your Server wizards, it forces you to select either VPN or
> dial-up as the Remote Access configuration. Then the wizard fails on
> the single NIC configuration.
>
> NT Server 4.0 and Server 2000 allow VPN configuration for a single NIC
> machine; why did Microsoft change this capability for Server 2003?
> This precludes implementing a simple, cost-effective VPN solution for
> small businesses to use their Windows Server as a VPN gateway. BAD
> business decision.
>
> Still looking for a solution configuring Server 2003 since rolling
> back to Server 2000 is not an option for the customer.
>
>> As you said, the standard wizard assumes you have two NICs. Use
>> one of the other wizard options to enable remote access on the
>> server. Test the setup locally (ie from a LAN client) to debug
>> settings and policies. When you can connect locally, forward the VPN
>> port from your router to the server's LAN IP and try to connect from
>> a remote client to the router's public interface.
>>
>> Duke Fleming wrote:
>>> Can someone point me to a resource for configuring Windows Server
>>> 2003 Routing and Remote Access services on a box with a single NIC
>>> card? The wizard will not run to completion if there is not at
>>> least 2 NIC cards.
>>>
>>> Environment is a small shop, single 2003 server for active
>>> directory, file and print; single LAN segement. Not going to add a
>>> second NIC with public IP address since Internet access is managed
>>> by router managed by ISP. Router port forwards PPTP traffic to
>>> locally assigned IP address on server NIC. Users want to be able to
>>> access server resources remotely from home, and when traveling.
>>>
>>> I have tried using the custom configuration from the RRAS setup
>>> wizard, selecting VPN and IP Routing. However, it does not allow me
>>> to go into the Computer Management interface afterwards and set up
>>> ports, protocols, and authentication policies as one would normally
>>> do after the wizard has run to completion.
>>>
>>> Thanks.