COnfused if ADSL router will not allow me to use WIn 2003 NAT

hi ..
i am using a ADSL Cisco router which provides me the nating for the LAN
(192.168.0.0/24) users.
Now i want to implement win 2003 RRAS and use NAT.
My question is do when i put a public ip address provided by my ISP to the
second (external) card which is connected directly to the ADSL Router ..will
i be able to connect to the internet. I am getting confused because i think
theADSL router will NAT the public address into a private address and the
new 2003 RRAS will not be able to connect to the router as the external
interface shall be configured with a public address.

I shall configure the other (internal Card) from the 192.168.0.0/24 subnet
and also use this as the default gateway for clients.
I shall also add a static route on the External Interface with the
destination addess as 0.0.0.0 and subnet mask as 0.0.0.0 so that it acts as
default route for all trafic.

I want to implement Microsoft Nat as i want to put all the routing overhead
on the server and also extend the network.
I hope i was clear enough .

"newbie" <(E-Mail Removed)> wrote in message
news:CB967D27-86BF-4CDD-9F6B-(E-Mail Removed)...
> hi ..
> i am using a ADSL Cisco router which provides me the nating for the LAN
> (192.168.0.0/24) users.
> Now i want to implement win 2003 RRAS and use NAT.
> My question is do when i put a public ip address provided by my ISP to the
> second (external) card which is connected directly to the ADSL Router
...will

The win2003 box would physically "replace" the NAT Device. You would need a
DSL Modem to "adapt" the Server's external NIC to the Phone Line. DSL
Modems do not have IP#s. They are just "dumb" boxes that are simply a type
of "media converter" or "transceiver" that allows the Nic on the Server with
a CAT-5 cable / RJ45 Connector to be able to connect to the Phone Cable /
RJ11 Connector.

> I shall configure the other (internal Card) from the 192.168.0.0/24 subnet
> and also use this as the default gateway for clients.

Yes. The server becomes the Default Gateway of the Clients just the way the
"router" used to be.

> I shall also add a static route on the External Interface with the
> destination addess as 0.0.0.0 and subnet mask as 0.0.0.0 so that it acts
as
> default route for all trafic.

No Static Routes! The should never be a need for you to even get close to
the Routing Table,...let alone change anything in it. The Server has a
Default Gateway on the External Nic,...this is usually auto-assigned by the
ISP. The Internal Nic's Gateway must remain blank.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com