Re: NAT without DHCP? (w2k3)
- From: "Bill Grant" <not.available@online>
- Date: Sat, 12 Aug 2006 15:44:08 +1000
You do not have to use the DHCP-style allocator in NAT. You can use
static IPs or you can run DHCP on one of your servers. But you do have to
configure NAT on the RRAS server. Just leave the area for IP addresses
blank. As long as you set the RRAS server's private IP as the default
gateway on the second machine (which you have done) it should work for any
10.x.x.x address.
Alex Smirnoff wrote:
Setup scenario: Windows Server 2003 R2 x64, two network cards - one
public and one private. I followed all instructions and installed
routing and remote access services, configured one network interface
as public and another as private (with IP 10.0.0.16). Everything
works fine and server can access internet.
Then I started configuring another machine on the internal network to
use first machine as router and got stuck. I dont want to use DHCP
allocator and want to assign internall addresses manually. So I
configured second machine as such (it is another W2K3 R2 x64, if it
matters):
IP Address. . . . . . . . . . . . : 10.0.2.10
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.0.0.16
DNS Servers . . . . . . . . . . . : 10.0.0.16
Again, everything works and I can ping one machine from another. But I
cannot access outside world from the second machine. I realized that
first server will not do NAT because it doesnt know that it should do
it for particular internal IP.
So how I can the main server to do NAT for all internal network
without using DCHP?
I would really appreciate any help/advice.
Alex
.
- Prev by Date: Re: NAT Settings for exposing an internal web server to the outside world?
- Next by Date: Re: Connection to Server
- Previous by thread: NAT Settings for exposing an internal web server to the outside world?
- Next by thread: Re: NAT without DHCP? (w2k3)
- Index(es):
Relevant Pages
|
