Re: RAS setup - routing
- From: "Bill Grant" <not.available@online>
- Date: Sun, 19 Jun 2005 09:22:25 +1000
The internal interface does not acquire an IP address until the first
remote client connects.
Øystein Tvedten wrote:
> Hi, I'm trying to move our RAS-VPN from one 2003 server to a new
> 2003 server, and have run into a small issue.
>
> When setting it up, I can't seem to find how to in IP Routing->
> General to ensure that the Internal interface gets an IP#. On the old RAS
> it
> has it's own IP (one of the IPs the DHCP relay has reserved), but on
> the new one that doesn't happen.
>
> Same with the IGMP setup, it shows nothing on the new Internal
> interface, tho it's configured as a v3 router. On the old one it
> shows as a router with it the ip# of the Internal interface as the
> querier address.
> Under Network Interfaces the Internal interface shows as enabled on
> both.
> I've browsed through my mcse books but they've not been very helpful
> right now..
>
> I did a netsh routing ip dump and compared the two outputs, but they
> looked identical to me.
>
> I'm stumped :(
>
> Øystein
.
- References:
- RAS setup - routing
- From: Øystein Tvedten
- RAS setup - routing
- Prev by Date: Routing and Remote access
- Next by Date: Re: Desperate Housewife Win 2000 Server vpn mess !
- Previous by thread: RAS setup - routing
- Next by thread: Routing and Remote access
- Index(es):
Relevant Pages
|