VLAN + NAT

Hello,

See if someone can help me out in here:

Scenario
---------

Windows 2003 server with two NIC

NIC1 has a public IP range, lets say, 161.56.31.0 [255.255.252.0] (The
public IP chosen is an example)
NIC2 has a private IP, 192.168.0.0 [255.255.255.0]
NAT service running on Windows 2003 server

NIC1 is working on my VLAN1 and NIC2 on my VLAN2, in other words, NIC2 is
connected to the port of a switch (3COM 3300) which is configured to work on
VLAN2.


Problem
---------

I'm trying to give access to client machines giving a private IP by working
on VLAN2, but then accesing the network doing NAT to VLAN1 (public IP). I'm
strungling configuring the NAT service!


Question1
----------

Does the NAT service lease IPs? In other words, does it have any DHCP
functionality or does it relies on an external DHCP?

Question2
-----------

In case I have to enable the DHCP server, would it clash with the other DHCP
server which I have on the network, running on another server, leasing
public IPs


Any ideas?

Thanks you all,

Fernando.

1. No, that is DHCP's job. You might want to review RFC1631 for the
operation of NAT.
http://www.faqs.org/rfcs/rfc1631.html

2. Here's a link on configuring NAT
http://www.windowsnetworking.com/art...AT-router.html


"Fernando" <(E-Mail Removed)> wrote in message
news:%23%(E-Mail Removed)...
> Hello,
>
> See if someone can help me out in here:
>
> Scenario
> ---------
>
> Windows 2003 server with two NIC
>
> NIC1 has a public IP range, lets say, 161.56.31.0 [255.255.252.0] (The
> public IP chosen is an example)
> NIC2 has a private IP, 192.168.0.0 [255.255.255.0]
> NAT service running on Windows 2003 server
>
> NIC1 is working on my VLAN1 and NIC2 on my VLAN2, in other words, NIC2 is
> connected to the port of a switch (3COM 3300) which is configured to work
on
> VLAN2.
>
>
> Problem
> ---------
>
> I'm trying to give access to client machines giving a private IP by
working
> on VLAN2, but then accesing the network doing NAT to VLAN1 (public IP).
I'm
> strungling configuring the NAT service!
>
>
> Question1
> ----------
>
> Does the NAT service lease IPs? In other words, does it have any DHCP
> functionality or does it relies on an external DHCP?
>
> Question2
> -----------
>
> In case I have to enable the DHCP server, would it clash with the other
DHCP
> server which I have on the network, running on another server, leasing
> public IPs
>
>
> Any ideas?
>
> Thanks you all,
>
> Fernando.
>
>
>

NAT does not act as a DHCP server by default. It only does it if you
specifically give it a batch of IP addresses to use for this purpose.Whether
you use that option for your private IP subnet or set up a new scope in your
existing DHCP server is up to you.

Neteng wrote:
> 1. No, that is DHCP's job. You might want to review RFC1631 for the
> operation of NAT.
> http://www.faqs.org/rfcs/rfc1631.html
>
> 2. Here's a link on configuring NAT
> http://www.windowsnetworking.com/art...AT-router.html
>
>
> "Fernando" <(E-Mail Removed)> wrote in message
> news:%23%(E-Mail Removed)...
>> Hello,
>>
>> See if someone can help me out in here:
>>
>> Scenario
>> ---------
>>
>> Windows 2003 server with two NIC
>>
>> NIC1 has a public IP range, lets say, 161.56.31.0 [255.255.252.0]
>> (The public IP chosen is an example)
>> NIC2 has a private IP, 192.168.0.0 [255.255.255.0]
>> NAT service running on Windows 2003 server
>>
>> NIC1 is working on my VLAN1 and NIC2 on my VLAN2, in other words,
>> NIC2 is connected to the port of a switch (3COM 3300) which is
>> configured to work on VLAN2.
>>
>>
>> Problem
>> ---------
>>
>> I'm trying to give access to client machines giving a private IP by
>> working on VLAN2, but then accesing the network doing NAT to VLAN1
>> (public IP). I'm strungling configuring the NAT service!
>>
>>
>> Question1
>> ----------
>>
>> Does the NAT service lease IPs? In other words, does it have any DHCP
>> functionality or does it relies on an external DHCP?
>>
>> Question2
>> -----------
>>
>> In case I have to enable the DHCP server, would it clash with the
>> other DHCP server which I have on the network, running on another
>> server, leasing public IPs
>>
>>
>> Any ideas?
>>
>> Thanks you all,
>>
>> Fernando.