Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setting up a static DNS route

Status
Not open for further replies.

wardog25

Technical User
Oct 24, 2003
129
US
I have a small network which uses a router as default gateway to the internet.

I want to use one of my windows 2k server machines with 2 NICs as a router to a smaller subnet, because the smaller subnet only needs to see that server (aside from logging in and DHCP and such), so it won't clog other network traffic.

I installed RRAS and setup the 2nd subnet, but the 2nd subnet can't see my main subnet or login to the DC. And the DC can't see the 2nd subnet either. How do I set up a static route in DNS so that they all can see each other?
 
Hi!
If I understand correct this should be your configuration:

SmallSubnet--------RRAS---------BigSubnet
|
Router-------Internet

Here is what happens with the communication between the Small Subnet (SS) and the Big Subnet (BS).

A)When a machine from SS sends a packet to BS the packet is routed through the RRAS reaches the destination Machine at BS. The Destination machine does not have a route to the SS and sends the answer packet to the default Gateway - the Router. The router does not have a Route to SS (I suppose that SS is using Private IP addressing space) and the packet is dropped.

B)The same thing happens when you try to reach a machine at SS from BS. The packet reaches the Router and is dropped.

There are three solutions:
1.Set a static route to SS on the Router pointing to RRAS server(If the Router supports static routes - some of the cheap broadband routers do not support that feature).
2.Set the RRAS server as a default Gateway for SS and BS and set a Deafult Route on RRAS pointing to the Router. The inconvinience here is that if RRAS is down you do not have network and Internet connectivity.
3.Set NAT on RRAS - that is probably the easier and faster to set solution. The SS is going to be NAT-ed through one or a couple of BS subnet addresses

Make your choice and we can help you with the solution that you prefer.

NetoMeter

 
I am sorry. The diagram should be like this:
Code:
SmallSubnet--------RRAS---------BigSubnet
                           |
                         Router-------Internet

forum.gif
NetoMeter

 
Yeah, that diagram looks fine.

I guess I'd have no choice but to go with #3.
 
I couldn't get this to work right. I set up RRAS as a router and then set up NAT. Neither ever worked. NAT would not assign an IP address to my test computer. So I set up a static IP, then the test computer and RRAS server could see each other, but it never did route anything to the other subnet.

I have a question though. If I set this up as a router, is it going to route EVERYTHING to the other subnet? Cause as I said, the RRAS server is the only server the small subnet needs to see. The only reason the small subnet even needs access to the other subnet is to access a DC so it can log in. I DO NOT want traffic to the RRAS server being routed out to the large subnet before returning to it. that is exactly what i'm trying to avoid.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top