Re: yet another vpn/routing question
From: Phillip Windell (_at_.)
Date: 04/27/04
- Next message: TR: "last names displayed in AD Uses & Computers"
- Previous message: Rav: "DNS forwarders"
- In reply to: Jeremy: "Re: yet another vpn/routing question"
- Next in thread: Jeremy: "Re: yet another vpn/routing question"
- Reply: Jeremy: "Re: yet another vpn/routing question"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Apr 2004 10:17:40 -0500
It sounds like the routing table is perfectly fine and you are only thinking
it is wrong and in the process of trying to correct it you may be messing it
up.
What you are looking at is not the Default Gateway entry. It is the Loopback
Route and that is the way it is supposed to look. The Default Gateway route
looks like this:
Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 10.146.183.253 10.146.183.251
These are loopback routes and should be there as they are. The one for
127.0.0.0 is the "localhost loopback". They do that same thing but one is
used when you use the name "localhost" (or 127.0.0.1), and the other is used
when you use the machine's name (or 10.146.183.251), but in the end they do
that same thing:
Destination Netmask Gateway Interface
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
10.146.183.251 255.255.255.255 127.0.0.1 127.0.0.1
I suspect that your problem lies somewhere in the actual configuration of
RRAS and the problem has nothing to do with the Routing table. If your
network is a single subnet private network, then there is *nothing* to
configure in any routing table. Layer3 Routers (such as RRAS) will
automatically know what to do with networks that are directly connected to
thier ports. They are refered to as simply "Directly Connected Networks" or
in some documentation it may just say "Connected Networks". There is simply
no configuration needed for such networks. "Routes" are only required when
there is more than one "hop" between the Source and Destination (in other
words two or more routers between them).
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com "Jeremy" <Nospam@nospam.com> wrote in message news:eJs4SPGLEHA.332@TK2MSFTNGP11.phx.gbl... > No it wasn't the only route, but for ease of typing I only included the one > that changed the most. Is there a easy way to use the wizard and setup VPN > with a internal network Nic and a Nic with Internet? So that in theory that > I could allow vpn's coming in on the internet nic to access the internal > network? I had it working briefly then all the sudden the route got munged > and seemed to be routing everything to the local loopback of 127.0.0.1 even > though with my limited experience I looked everywhere it was listing the > routes as still being what the network cards were set with. But the > route -print didn't match what the cards were set with my example is the > internal nic being set to a gateway of 127.0.0.1 instead of 10.146.183.253 > > -- > > > Jeremy Kettelhohn > > > "Matthew [MSFT]" <mfresoli@online.microsoft.com> wrote in message > news:cMrVULGLEHA.3900@cpmsftngxa10.phx.gbl... > > Hi Jeremy, > > > > The route itself looks to be correct. But is that the only route you see > > in the route table? > > > > One thing to be careful of is when you use the Wizard to add the VPN > > server, you will get packet filters applied to the network card (for > > security reasons). It will only pass 1723 and GRE traffic. > > > > You can go into the properties of the interface ( in RRAS under ip routing > > -> general) and remove these. As long as the server is internal (and does > > not have a direct connection to the internet), then this should be ok. > > > > > > Thank you, > > Matthew Fresoli > > Microsoft Network Support > > -- > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > Use of included script samples are subject to the terms specified at > > http://www.microsoft.com/info/cpyright.htm > > > > Note: For the benefit of the community-at-large, all responses to this > > message are best directed to the newsgroup/thread from which they > > originated. > > > > > >
- Next message: TR: "last names displayed in AD Uses & Computers"
- Previous message: Rav: "DNS forwarders"
- In reply to: Jeremy: "Re: yet another vpn/routing question"
- Next in thread: Jeremy: "Re: yet another vpn/routing question"
- Reply: Jeremy: "Re: yet another vpn/routing question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|