Re: RRAS Routing Problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If the clients on their respective network are already "default routed" to
their respective RRAS Box then there is no "static route" that I can think
of that should be there. The RRAS boxes already "know" about the IP Segment
on the opposite end since they are directly connected to it. The Clients
only need to know where their RRAS Box is,...they do not need to "know"
specifically about the opposite LAN.

But then it has been a while since I worked with RRAS and I have a tendency
to think of it in terms of how I would a traditional router appliance.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Jack Dawsen" <Jack Dawsen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5A2B34B5-FF37-4717-9BEA-831E067EB725@xxxxxxxxxxxxxxxx
I have one of the weirdest routing problems I've ever seen in RRAS. I have
the following configuration, :

Boston:
-All clients default routed to the RRAS Server
-Network: 192.168.1.0
-RRAS Server: 192.168.1.29
--Windows 2003 SP 2 (Enterprise Server)
--PPTP Server
--Static route set to the remote route on the 192.168.2.0 network
--One NIC, default routed to 192.168.1.1 (DSL Router to the cloud)

Fairfax:
-All clients default routed to the RRAS Server
-Network: 192.168.2.0
-RRAS Server: 192.168.2.29
--Windows 2008 (Enterprise Server)
--PPTP Server
--Static route set to the remote route on the 192.168.1.0 network
--One NIC, default routed to 192.168.2.1 (DSL Router to the cloud)

These servers have a route called BostonFairfaxRoute. It's set up
identically on both servers, using that username and the username's
password.
The RRAS servers connect the remote route successfully.

The problem lies in the ability to successfully route packets. The
following
scenarios result:

192.168.2.29: CAN PING 192.168.1.29
192.168.1.29: Cannot ping 192.168.2.29
Clients on 192.168.2.0 network: Cannot ping 192.168.1.29
Clients on the 192.1.0 network: Cannot ping 192.168.2.29

If the path between 192.168.2.29 and 192.168.1.29 didn't make it either
way
I'd understand the problem. The confusing part is that it works one way!
I've
never seen this before and have no idea how to solve it. I've verified all
of
the settings more than once in what's a very common system for me to
setup.

Anyone have any ideas?


.

Relevant Pages

  • Partial solution
    ... Once RRAS is setup for internet sharing using NAT, I went into the IP tab of ... and clients can successfully access the internet. ... > This setup has worked fine so far: clients can access internet, DNS server ...
    (microsoft.public.win2000.ras_routing)
  • Re: 2 Nics 1 Dial
    ... in RRAS if I create from scratch, ... Connection Server -> NAT -> demand-dial ... number etc, route IP packets, account info ...
    (microsoft.public.win2000.networking)
  • Re: RRAS and NAT
    ... Nslookup produces a No response from server error. ... see that happening in RRAS and as I said before, the clients arte getting IP ... NATting within RRAS is sort of binary, ...
    (microsoft.public.windows.server.networking)
  • Re: RRAS Wont Work On Dual Nic Server
    ... Was rras configured before, ... > I have an hp/compaq server with two teaming nics. ... > connectivity with internal clients and no external clients ...
    (microsoft.public.win2000.networking)
  • Re: RRAS Wont Work On Dual Nic Server
    ... Connectivity to the server is lost. ... >What do you mean that all clients lose connectivity - ... Was rras configured before, or was this ...
    (microsoft.public.win2000.networking)