forward internet to static ip clients?

My setup is pretty basic. I'm running windows server 2003 active directory
and dns server. I have two nics in the server. one has a public ip with the
internet: 130.191.73.23 and the other has the private local network:
10.10.0.1 I only have a few XP boxes here in my small non profit
organisation, so I gave every client a static ip: 10.10.0.2 to 10.10.0.24
Another reason why I can't use dhcp or ics or nat or anything that
distributes automatic ip's, is because our building's wires already run a
network that has a dhcp server of some sort. And I don't have control over
that one.

My main question here is: how can I forward the internet using manual
forwarding to each IP or some otherhow? All the methods I found that do
forwarding use some sort of dhcp having all the clients be on automatic ip
which I can't do.

Any help would be appreciated. - Oliver

Nothing prevents you to use Windows Server 2003 NAT with static IPs. Just
add the server IP address as the DNS server and default gateway for the XP
computers.

orahm wrote:
> My setup is pretty basic. I'm running windows server 2003 active
> directory and dns server. I have two nics in the server. one has a
> public ip with the internet: 130.191.73.23 and the other has the
> private local network:
> 10.10.0.1 I only have a few XP boxes here in my small non profit
> organisation, so I gave every client a static ip: 10.10.0.2 to
> 10.10.0.24 Another reason why I can't use dhcp or ics or nat or
> anything that distributes automatic ip's, is because our building's
> wires already run a network that has a dhcp server of some sort. And
> I don't have control over that one.
>
> My main question here is: how can I forward the internet using manual
> forwarding to each IP or some otherhow? All the methods I found that
> do forwarding use some sort of dhcp having all the clients be on
> automatic ip which I can't do.
>
> Any help would be appreciated. - Oliver

There is no reason you cannot run NAT in this scenario. Simply run the
wizard. The default configuration implies that DHCP will be used to assign
addresses, but this does not prevent you from continuing to use your static
addresses. RRAS doesn't really care how clients get IPs as long as you
don't configure the DHCP allocator:

http://support.microsoft.com/kb/816581/en-us

Note your clients should be configured with a default gateway of 10.10.0.1,
and you will need to enable Forwarders in the DNS console on the server to
point to your ISP's DNS server.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"orahm" <(E-Mail Removed)> wrote in message
news:E9A2F74F-D175-4D1E-93C4-(E-Mail Removed)...
> My setup is pretty basic. I'm running windows server 2003 active directory
> and dns server. I have two nics in the server. one has a public ip with
the
> internet: 130.191.73.23 and the other has the private local network:
> 10.10.0.1 I only have a few XP boxes here in my small non profit
> organisation, so I gave every client a static ip: 10.10.0.2 to 10.10.0.24
> Another reason why I can't use dhcp or ics or nat or anything that
> distributes automatic ip's, is because our building's wires already run a
> network that has a dhcp server of some sort. And I don't have control over
> that one.
>
> My main question here is: how can I forward the internet using manual
> forwarding to each IP or some otherhow? All the methods I found that do
> forwarding use some sort of dhcp having all the clients be on automatic ip
> which I can't do.
>
> Any help would be appreciated. - Oliver
>
>

Many thanks for replying. I have configured NAT they it was described but my
test client still does not get the internet. How do I enable dns forwarders.
I do not quiet understand how to configure the dns forwarders.

"Doug Sherman [MVP]" wrote:

> There is no reason you cannot run NAT in this scenario. Simply run the
> wizard. The default configuration implies that DHCP will be used to assign
> addresses, but this does not prevent you from continuing to use your static
> addresses. RRAS doesn't really care how clients get IPs as long as you
> don't configure the DHCP allocator:
>
> http://support.microsoft.com/kb/816581/en-us
>
> Note your clients should be configured with a default gateway of 10.10.0.1,
> and you will need to enable Forwarders in the DNS console on the server to
> point to your ISP's DNS server.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "orahm" <(E-Mail Removed)> wrote in message
> news:E9A2F74F-D175-4D1E-93C4-(E-Mail Removed)...
> > My setup is pretty basic. I'm running windows server 2003 active directory
> > and dns server. I have two nics in the server. one has a public ip with
> the
> > internet: 130.191.73.23 and the other has the private local network:
> > 10.10.0.1 I only have a few XP boxes here in my small non profit
> > organisation, so I gave every client a static ip: 10.10.0.2 to 10.10.0.24
> > Another reason why I can't use dhcp or ics or nat or anything that
> > distributes automatic ip's, is because our building's wires already run a
> > network that has a dhcp server of some sort. And I don't have control over
> > that one.
> >
> > My main question here is: how can I forward the internet using manual
> > forwarding to each IP or some otherhow? All the methods I found that do
> > forwarding use some sort of dhcp having all the clients be on automatic ip
> > which I can't do.
> >
> > Any help would be appreciated. - Oliver
> >
> >
>
>
>

disregard the last message. I figured out that I need to check the
non-recursive name resultion box in my case. I works fine now.

"orahm" wrote:

> Many thanks for replying. I have configured NAT they it was described but my
> test client still does not get the internet. How do I enable dns forwarders.
> I do not quiet understand how to configure the dns forwarders.
>
> "Doug Sherman [MVP]" wrote:
>
> > There is no reason you cannot run NAT in this scenario. Simply run the
> > wizard. The default configuration implies that DHCP will be used to assign
> > addresses, but this does not prevent you from continuing to use your static
> > addresses. RRAS doesn't really care how clients get IPs as long as you
> > don't configure the DHCP allocator:
> >
> > http://support.microsoft.com/kb/816581/en-us
> >
> > Note your clients should be configured with a default gateway of 10.10.0.1,
> > and you will need to enable Forwarders in the DNS console on the server to
> > point to your ISP's DNS server.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "orahm" <(E-Mail Removed)> wrote in message
> > news:E9A2F74F-D175-4D1E-93C4-(E-Mail Removed)...
> > > My setup is pretty basic. I'm running windows server 2003 active directory
> > > and dns server. I have two nics in the server. one has a public ip with
> > the
> > > internet: 130.191.73.23 and the other has the private local network:
> > > 10.10.0.1 I only have a few XP boxes here in my small non profit
> > > organisation, so I gave every client a static ip: 10.10.0.2 to 10.10.0.24
> > > Another reason why I can't use dhcp or ics or nat or anything that
> > > distributes automatic ip's, is because our building's wires already run a
> > > network that has a dhcp server of some sort. And I don't have control over
> > > that one.
> > >
> > > My main question here is: how can I forward the internet using manual
> > > forwarding to each IP or some otherhow? All the methods I found that do
> > > forwarding use some sort of dhcp having all the clients be on automatic ip
> > > which I can't do.
> > >
> > > Any help would be appreciated. - Oliver
> > >
> > >
> >
> >
> >

Go get 'em, orahm!

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"orahm" <(E-Mail Removed)> wrote in message
news:A418C0F4-B3B7-4F90-B5C3-(E-Mail Removed)...
> disregard the last message. I figured out that I need to check the
> non-recursive name resultion box in my case. I works fine now.
>
> "orahm" wrote:
>
> > Many thanks for replying. I have configured NAT they it was described
but my
> > test client still does not get the internet. How do I enable dns
forwarders.
> > I do not quiet understand how to configure the dns forwarders.
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > There is no reason you cannot run NAT in this scenario. Simply run
the
> > > wizard. The default configuration implies that DHCP will be used to
assign
> > > addresses, but this does not prevent you from continuing to use your
static
> > > addresses. RRAS doesn't really care how clients get IPs as long as
you
> > > don't configure the DHCP allocator:
> > >
> > > http://support.microsoft.com/kb/816581/en-us
> > >
> > > Note your clients should be configured with a default gateway of
10.10.0.1,
> > > and you will need to enable Forwarders in the DNS console on the
server to
> > > point to your ISP's DNS server.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "orahm" <(E-Mail Removed)> wrote in message
> > > news:E9A2F74F-D175-4D1E-93C4-(E-Mail Removed)...
> > > > My setup is pretty basic. I'm running windows server 2003 active
directory
> > > > and dns server. I have two nics in the server. one has a public ip
with
> > > the
> > > > internet: 130.191.73.23 and the other has the private local network:
> > > > 10.10.0.1 I only have a few XP boxes here in my small non profit
> > > > organisation, so I gave every client a static ip: 10.10.0.2 to
10.10.0.24
> > > > Another reason why I can't use dhcp or ics or nat or anything that
> > > > distributes automatic ip's, is because our building's wires already
run a
> > > > network that has a dhcp server of some sort. And I don't have
control over
> > > > that one.
> > > >
> > > > My main question here is: how can I forward the internet using
manual
> > > > forwarding to each IP or some otherhow? All the methods I found that
do
> > > > forwarding use some sort of dhcp having all the clients be on
automatic ip
> > > > which I can't do.
> > > >
> > > > Any help would be appreciated. - Oliver
> > > >
> > > >
> > >
> > >
> > >