Re: Win Server 2003 RAS routing problems
- From: "Bill Grant" <not.available@online>
- Date: Fri, 8 Apr 2005 10:07:53 +1000
g18c@xxxxxxxxxxx wrote:
> I have been playing about with RAS between two servers... works ok. Am
> i correct in thinking that for the windows 2k box i would need to add
> a route using netsh? When using 'route' the RAS interface isnt listed
> at all, netsh seems like it is the tool to use (but complicated!). Any
> advice much appreciated,
>
> cheers,
>
> Chris
I would stick with using servers. RRAS allows you to set up demand-dial
interfaces and link the routes to those interfaces. You don't have this
ability in Pro. You can't really set up a route until after the connection
is made (because the interface doesn't exist). With RRAS you can use the
demand-dial interface name to represent the connection and tie the routes to
the dd interface (using the new static route wizard in RRAS).
.
- References:
- Win Server 2003 RAS routing problems
- From: Chris
- Re: Win Server 2003 RAS routing problems
- From: Robert L [MS-MVP]
- Re: Win Server 2003 RAS routing problems
- From: g18c
- Re: Win Server 2003 RAS routing problems
- From: g18c
- Win Server 2003 RAS routing problems
- Prev by Date: Re: Problems Logon on Ras Server
- Next by Date: Re: Unable to access private network from the VPN (NAT)
- Previous by thread: Re: Win Server 2003 RAS routing problems
- Next by thread: Re: VPN and DNS
- Index(es):
Relevant Pages
|