Re: Routing through a Win2K Server
- From: "Bill Grant" <not.available@online>
- Date: Wed, 14 Sep 2005 10:54:51 +1000
Not really. You already have an interface in the 192.168.1 subnet to act
as the "public" interface for NAT. PPPoE is what is causing you grief. W2k
didn't handle PPPoE well.
Your "public" interface (ie the one which actually connects to the
Internet) is probably not the 192.168.1.1 NIC but some other IP allocated by
PPPoE. For tips on using W2k with PPPoE see Darren's website at
www.ozcableguy.com
Tonymax wrote:
> So I would set up a virtual 192.168.1.x address on the server NIC
> that's connected to the router on that subnet, and then use NAT to
> forward those individual addresses to the corresponding 192.168.0.x
> addresses on the second subnet?
>
>
>
>> As Bob said, the simplest option is to enable NAT on the RRAS
>> router.
>>
>> Without NAT you don't have enough routing info. And you can't
>> fix it by changing things at the RRAS router. The problem is at the
>> Internet router.
>>
>> The Internet router only knows about the 192.168.1 subnet. It
>> has no idea where the 192.168.0 subnet is. Because it doesn't know
>> where it is, it sends traffic for 192.168.0 to its default gateway
>> (which sends it out to the Internet where it gets dropped).
>>
>> With NAT on the RRAS router, all traffic from the 192.168.0
>> subnet uses the server's 192.168.1 address, so the Internet router
>> knows where to send it. Without NAT, you would need extra routing on
>> the Linksys to tell it where to send traffic for 192.168.0 ie
>>
>> 192.168.0.0 255.255.255.0 192.168.1.60
>>
>> "Robert L [MS-MVP]" <noreply@xxxxxxxxxxx> wrote in message
>> news:exjms59tFHA.3528@xxxxxxxxxxxxxxxxxxxxxxx
>> that web site has how to configure NAT.
>>
>> nat and firewall How to configure 2000/2003 NAT services and ports
>> NAT server can assign IP No one can access our website behind NAT
>> Server can access the Internet but not ...
>> www.chicagotech.net/nat.htm
>>
>>
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "Tonymax" <Tonymax@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:064E9EA6-029E-4A96-9236-26433E403A35@xxxxxxxxxxxxxxxx
>> lol! You can't assume anything with me, I know NOTHING! I did find
>> NAT in my
>> RRAS console, but I thought that was just for translating
>> alphanumeric urls
>> into actual IP addresses.
>>
>> So how do I go about setting this up?
>>
>>
>> --
>> Tony Peterle
>> Certified IT rookie
>>
>>
>> "Robert L [MS-MVP]" wrote:
>>
>> > I am assuming you also enabled the NAT so that the lower part
>> can access the upper part and internet but no another way. So, check
>> the NAT settings. >
>> > nat and firewall
>> > In the Select Routing Protocol dialog box, click NAT/Firewall,
>> and then click OK.
>> > .... NAT/Firewall blocks the client accessing the Internet. ...
>> > www.chicagotech.net/nat.htm
>> >
>> > Bob Lin, MS-MVP, MCSE & CNE
>> > Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> > How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> > "Tonymax" <Tonymax@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:7063344C-67C3-4D4C-B1D4-EF0467B7E40C@xxxxxxxxxxxxxxxx
>> > I am a relative newbie to IT, although I think I can grasp it
>> fairly well,
>> > I'm having trouble with getting my two NICs in my win2K server
>> to talk to
>> > each other.
>> >
>> > Here's the setup (we're talking VERY simple here!)
>> >
>> > DSLmodem (fixed, public IP)
>> > l
>> > l
>> > Linksys Router (makes the PPPoE Connection, all ports
>> forwarded to server)
>> > 192.168.1.1 (DHCP enabled, range .20
>> to .39) > 255.255.255.0 l
>> > l l
>> > l l
>> > 192.168.1.60 192.168.1.20 to .39
>> > 255.255.255.0 255.255.255.0
>> > Win2KServer Other computers in
>> office > First (built in) NIC
>> > l
>> > Second NIC
>> > 192.168.0.1
>> > 255.255.255.0
>> > l
>> > l
>> > Other equipment with web pages, fixed IPs from 192.168.0.205
>> to 213 >
>> >
>> > The computers hooked up to the Linksys are fine, and I can hit
>> the first NIC
>> > of the server from inside or outside the Linksys (we want our
>> server to host
>> > a small public website with connectivity to the equipment
>> connected to the
>> > second NIC). I can get to the equipment on the second NIC with
>> port > forwarding, but only on specific ports. I cannot ping the
>> second NIC
>> or any
>> > of the euipment connected to it from anywhere on the upper
>> part of the > network. Yet if I connect a computer on the lower
>> part of the network, I can
>> > access the Internet fine.
>> >
>> > I have RRAS enabled, even checked the IPRouterEnable in my
>> registry to make
>> > sure it was set to 1. I've tried adding secong (virtual) IP
>> addresses to both
>> > NICs in each others subnets, I've tried to establish an IP
>> tunnel between the
>> > two, I've tried Active Directory and adding RIP to the first
>> NIC, even tried
>> > setting the whole thing up as a domain controller. No go.
>> >
>> > I've played some with the static routes, but I really don't
>> know what I'm
>> > doing, and I can't seem to find the answers anywhere in the
>> Help menus or in
>> > any of the books I've read.
>> >
>> > What am I missing here? why won't the two NICs swap some
>> packets so I can
>> > hit that 192.168.0.x subnet from the 192.168.1.x subnet?
>> >
>> > Sorry to be such an idiot, this is all pretty new to me!
>> >
>> > Tony
>> >
>> > --
>> > Tony Peterle
>> > Certified IT rookie
.
- References:
- Routing through a Win2K Server
- From: Tonymax
- Re: Routing through a Win2K Server
- From: Tonymax
- Re: Routing through a Win2K Server
- From: Bill Grant
- Re: Routing through a Win2K Server
- From: Tonymax
- Routing through a Win2K Server
- Prev by Date: Re: Direct Dial Routing Issue
- Next by Date: Re: Direct Dial Routing Issue
- Previous by thread: Re: Routing through a Win2K Server
- Next by thread: Remote RAS Client DNS Registration
- Index(es):
Relevant Pages
|
Loading
