Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Simple RRAS and two networks

64 views
Skip to first unread message

keithgriffith

unread,
Oct 14, 2009, 10:47:39 AM10/14/09
to
I have a primary network that houses the bulk of my workstations, servers, and provides internet connectivity. I am adding a small group of users to the current network, and I thought that since i already had an unused server on that segment i would just use rras to connect them. They will need to access the internet, network shares, and exchange on the primary network.

I unteamed the nics om the remote rras server and assigned one to each segment.

Here is my current, non working configuration:

Primary network:
Internet gateway: 192.168.0.1
DNS: 192.168.0.101
RRAS primary nic: ip192.168.0.115 - gw192.168.0.1 - dns192.168.0.101
RRAS secondary link: ip10.10.1.1 - gw192.168.0.115 - dns192.168.0.101
Primary client ip: ip192.168.0.x - gw192.168.0.1 - dns192.168.0.101
Secondary client ip: ip10.10.1.x - gw10.10.1.1 - dns192.168.0.101

I have static routes built between the two nics as follows:
Primary: 192.168.0.0/24 gw192.168.0.1
Secondary:10.10.1.0/24 gw10.10.1.1

What have I done wrong? No routing going on. I can ping either network from the rras box, but nothing is routing.

EggHeadCafe - Software Developer Portal of Choice
Host Winforms App in IE from your web server
http://www.eggheadcafe.com/tutorials/aspnet/c40df7ba-b0c1-4de6-802b-78bbd653d184/host-winforms-app-in-ie-f.aspx

Ace Fekay [MCT]

unread,
Oct 14, 2009, 10:54:01 AM10/14/09
to

"Keith Griffith" wrote in message news:20091014104...@reawire.com...


First, you have to remove the gateway on the 10.1.1.1 NIC. Having two
gateways will definitely cause problems. Remember, "default gateway" means
only one default gateway. Can't be two.

Second, you only need one static route, which will be configured on the
192.168.0.1 router that tells that router how to get to the 10.1.1.0/24
network. Setting a static route on the RRAS server doesn't help.

Take a look at this pic to see what I mean.

Static Route Example
http://www.fekay.com/supportblogs/StaticRoutingExample.jpg

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.


Ace Fekay [MCT]

unread,
Oct 14, 2009, 11:04:19 AM10/14/09
to
"Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
news:uhA1r4NT...@TK2MSFTNGP06.phx.gbl...

Oh, one more thing. On the RRAS server, do not use NAT and just route. AD
functions (logons, authentication, etc), do not work across NAT.

If I may suggest, it may much less expensive to simply use an inexpesive
router to perform routing instead of using a Windows machine.

Ace


0 new messages