Bill,
Thanks for the tip, and that may be a problem once it get there but
in the mean time I can't even ping a host on the other side of the inbound
RRAS tunnel. Part of what I'm stumped on is how, if it's possible that is,
to enable RIP on an inbound demand dial connection. That not withstanding I
set up a static route (on ISA) to the IP (static) of the demand dial host
(RRAS) and with RIP enabled on the internal interface of ISA it's
distributing the route to the network but it won't forward it to the remote
host (at least not as far as I can tell). We have no filters defined on
either side ISA or RRAS for this connection, this should be a standard
remote office connection to their LAN. So by my way of thinking I should be
able (once they're connected) to ping any host on their network, but I
can't, that's where I'm hung up.
James Price
(E-Mail Removed)
"Bill Grant" <not.available@online> wrote in message
news:ekyv8D$(E-Mail Removed)...
> I don't think this is a routing problem at all. I would say it was a
name
> resolution problem. Routing usually works fine with the static routes set
up
> by ISA/RRAS.
>
> DCs should not be multihomed. That includes RRAS interfaces as well as
> NICs. It causes all sorts of problems with name resolution and browsing.
See
> KB 292822 for an example of these problems and suggested fixes.
>
> "James E. Price III" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I have a 5 site RRAS to ISA network I have DC's (running DNS) and
> > workstation on each segment. I cannot figure out how to configure
either
> > ISA or RRAS to exchange routing information. For example:
> >
> > Net-A 172.16.32.0/24
> > Net-B 172.16.33.0/24
> > Net-C 192.168.1.0/24
> >
> > Net-A is running ISA configured to accept VPN clients, Nets B & C have
> RRAS
> > configured to connect the the ISA server on Net-A and configured for
RIP.
> > After connecting to ISA the DC on Net-C registers itself in DNS (AD
> > integrated) with both a 172.16.32.x address and a 192.168.1.x address.
> The
> > problem is that when the DC or a client workstation on Net-B attempts to
> > connect to the DC on Net-C it attempts to contact the 192.168.1.x
address
> > not the 172.16.32.x address and cannot find a route.
> >
> > The ISA server can't be configurd to listen for RIP on port it listens
on,
> > only on fixed ports and I have configured the RRAS servers for RIP on
> their
> > Demand Dial interfaces and specified a RIP neighbor another RRAS server
on
> > the same subnet as the ISA server but they won't exchange route
> information
> > about the 192.168.1.0/24 network.
> >
> > What am I missing?
> >
> > James Price
> > (E-Mail Removed)
> >
> >
>
>