Server 2003 Routing and Remote Access VPN

[The_Librarian]

Hi

The LAN is running on 192.168.10.0/24 - but we're feeling the pinch with the DHCP server complaining about the address pool getting smaller and smaller.

Is it possible to assign the dial-up clients to another subnet (say 192.168.30.0/24) and have them route to 192.168.10.0/24?

That way we'll have more than enough IP's for DHCP and for dial-up clients as well.

Regards

Ook

[Le^stat]

Running a separate vlan and scope on a layer 3 switch might assist you with ip constraints.

[ponder]

Can't you do VLSM and increase the range or do you have assigned blocks on either side?

[Spazmatic]

We run a seperate vlan for our VPN clients, have the RRAS server issue IP from that VLAN.

The RRAS server can live on the VPN VLAN and just make sure your routing is setup.

There are a few options....

[lumpyza]

havent used RRAS for vpn connections for years but logic tells me you can assign the RRAS server different IP address on a different subnet under IPv4 > advanced > IP Address. then Create a new IP pool on the subnet you want ur vpn users to run on and point the dhcp forwarding to that scope...

I could be wrong but worth a look into!

Just get a proper firewall, either ISA, TMG, Fortigate, Smoothwall or any other blend of linux based firewall... will sae you time and some headaches...

[TheGuy]

Would you not need another NIC on the server that is specifically in that Subnet that then routes between the LAN and the VPN subnet. This will also make your firewall config a bit different.

I agree with Ponder change your Subnet to 255.255.252.0 Will give you 192.168.8.0 - 11.254 Then you don't even change any server IP addresses just their Subnets and the DHCP Pool.