Help with Internet sharing on separate network using NAT

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I am trying to set up a separate newtwork in order to establish a testing
"lab" for work. How do I set up NAT in order to allow my new network to
access the internet as well?

Scenario: one domain is on the 192.168.1.0 network behind a SOHO
router/gateway with the ip 192.168.1.1. I have set up a new server using Win
2000 with the network address 192.168.2.0 also behind this router/gateway.
Can I use NAT on this new Win 2000 server to aqcuire and share internet
access to other computers I put on the 192.168.2.0 network?

So far I have set up RRAS and installed the NAT protocol. I have 2 NICS.
NICinternal has the ip address 192.168.2.1 and NICexternal has 192.168.2.2

Am I getting close?

Sol
 
Assuming you are not using VLans - If NICexternal is connected to the SOHO
router, it must have a 192.168.1.x address. Depending on the capabilities
of the SOHO router, you may not need NAT on the Win 2000 server. Try simply
enabling LAN routing.

NICexternal should have a default gateway of 192.168.1.1. NICinternal
should have no default gateway, and machines connected to the 192.168.2.x
network should have a default gateway of 192.168.2.1. The SOHO router needs
a static route for the 192.168.2.0 network pointing to the IP address of
NICexternal. If the router does not have this capability, use NAT on the
Win2k Server. You may have problems running NAT behind a NAT router, but
this usually works.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Thanks for the help. I felt like I was getting close... :)

Question: by VLAN do you mean virtual as in Virtual Server? Because I am
setting this up using virtual server. How does this change things? Thanks
again.

Doug Sherman said:
Assuming you are not using VLans - If NICexternal is connected to the SOHO
router, it must have a 192.168.1.x address. Depending on the capabilities
of the SOHO router, you may not need NAT on the Win 2000 server. Try simply
enabling LAN routing.

NICexternal should have a default gateway of 192.168.1.1. NICinternal
should have no default gateway, and machines connected to the 192.168.2.x
network should have a default gateway of 192.168.2.1. The SOHO router needs
a static route for the 192.168.2.0 network pointing to the IP address of
NICexternal. If the router does not have this capability, use NAT on the
Win2k Server. You may have problems running NAT behind a NAT router, but
this usually works.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
Click to expand...
 
VLans are virtual LANs. This is an IEEE standard supported by some managed
switches and routers. Essentially, this allows you to emulate multi-segment
routing on a single physical LAN. See:

http://www.nwfusion.com/details/471.html

It is unlikely that a device described as a SOHO router would support this.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Thanks!

Doug Sherman said:
VLans are virtual LANs. This is an IEEE standard supported by some managed
switches and routers. Essentially, this allows you to emulate multi-segment
routing on a single physical LAN. See:

http://www.nwfusion.com/details/471.html

It is unlikely that a device described as a SOHO router would support this.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
Click to expand...
 
Back
Top