Re: Build up NAT/VPN Role Server
- From: "Bill Grant" <not.available@online>
- Date: Sun, 3 Jul 2005 12:27:51 +1000
Ifyou are not running Active Directory you do not need to set up DNS.
You can set the DNS addresses directly on the clients(as you have done) or
use the NAT server as a DNS proxy (by configuring that option on the RRAS
server).
The config of the clients looks OK. I suspect the problem is with the
server config. PPPoE can be tricky. The "external" or "public" interface for
NAT must be the PPPoE interface, and this interface must have a default
route out to the Internet provider. This interface is probably not your
primary NIC. Have you configured the PPPoE interface from the RRAS console?
The "internal" or "private" interface for NAT must be your secondary NIC (ie
192.168.8.1).
Musnazril Mustaq Khan wrote:
> Hello, iam having a problems to setting up this role (refer topic) in
> windows 2003 Enterprise Server. I already trying more than 30 times
> with difference setting also already follow lot of manual+tutorial on
> the internet including MSCE E-book.
>
> my first question;
>
> is I need to run DHCP + DNS Server before i can setting up NAT/VPN
> role? Currently iam not running DHCP + DNS Server.
>
> my test enviroment is;
>
> 1 Server with 2 NIC
> Dial up to internet using Windows PPPoE (1024Kbps download / 384Kbps
> upload) 2 Client running Windows XP Pro
>
> This is Lattest Setting I had trial.
>
> Primary NIC (DHCP Enable given by ADSL Modem)
> IP = 192.168.1.2
> Subnet = 255.255.255.0
> Gateway = 192.168.1.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Secondary NIC (Manual)
> IP = 192.168.8.1
> Subnet = 255.255.254.0
> Gateway = Not Set
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Client 1 (Manual)
> IP = 192.168.8.2
> Subnet = 255.255.254.0
> Gateway = 192.168.8.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Client 2 (Manual)
> IP = 192.168.8.3
> Subnet = 255.255.254.0
> Gateway = 192.168.8.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> After Finishing Setting ALL NIC IP, iam back to the Server and run
> Manage Your Server Configuration Wizard. Follow the adding NAT/VPN
> Role Wizard, putting the adapter that have access to internet as
> Primary Adapter, All VPN client will ge connected to Secondary NIC
> and also selecting Secondary NIC as a share Internet Adapter (That
> the only one adapter offered by the wizard).
>
> After finish, iam restarting Server and also all clients. Than
> dialing to the internet. Once connected iam testing all connection.
>
> Server able to access Internet, LAN, Share Resource.
>
> Clients able to access LAN, Share Resource but unable to access
> Internet.
>
> Remote Client, Connected using VPN Connection able to access LAN,
> Share Resource but unable to access Internet.
>
> So can somebody which is expert in this role teach me the correct way
> to deploy NAT/VPN Role.
>
> Note I already testing this IP configuration.
>
> Primary NIC (DHCP Enable given by ADSL Modem)
> IP = 192.168.1.2
> Subnet = 255.255.255.0
> Gateway = 192.168.1.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Secondary NIC (Manual)
> IP = 192.168.0.1
> Subnet = 255.255.255.0
> Gateway = Not Set
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Client 1 (Manual)
> IP = 192.168.0.2
> Subnet = 255.255.255.0
> Gateway = 192.168.8.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
>
> Client 2 (Manual)
> IP = 192.168.0.3
> Subnet = 255.255.255.0
> Gateway = 192.168.8.1
> DNS1 = 202.188.1.5
> DNS2 = 202.188.0.133
.
- References:
- Build up NAT/VPN Role Server
- From: Musnazril Mustaq Khan
- Build up NAT/VPN Role Server
- Prev by Date: Re: Disable "Use Default Gateway on Remote Network" on the server?
- Next by Date: Re: pinging hostnames
- Previous by thread: Build up NAT/VPN Role Server
- Next by thread: pinging hostnames
- Index(es):
Relevant Pages
|
