Re: static routing
- From: "Robert" <user@xxxxxxx>
- Date: Mon, 2 Jul 2007 21:29:16 -0500
OK, so if I understand you, I need to create a demand dial connection on
both sides and connect them? I still don't understand how the lan users on
the side that already has the dd connection made can't access the network,
but the machine that made the connection can.
Robert
"Bill Grant" <not.available@online> wrote in message
news:uJAe2yPvHHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
To get routing working between the two sites you will need to set up a
site to site (also called router to router) connection. Routing is a
two-way process. You must have routes on the routers at both ends to be
able to get from a host in on site to a host in the other.
To do it using RRAS routers you need one in each site. The connection
is made between the routers. Each router has a static route to the other
site linked to a demand dial interface. The "calling" router connects to
the dd interface on the answering router. The static route thehn become
effective, routing traffic through the link.
"Robert" <user@xxxxxxx> wrote in message
news:ue3m2aPvHHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
Yes, your right. Here is the setup:
Branch Office
Server "WAN"
IP: 192.168.16.11
Subnet: 255.255.255.0
Gateway: 192.168.16.1
Server "LAN"
IP: 192.168.17.2
Subnet: 255.255.255.0
Gateway: "None"
Client IP Setup:
IP: 192.168.17.25
Subnet: 255.255.255.0
Gateway: 192.168.17.2
I used static ip addressing on the clients to make it easier. The
clients can connect to the internet just fine, but can't browse the
remote network. The server already has the demand dial interface
connected and I can browse the remote network from the server, but not
from the clients. I can also browse the branch office server from the
corporate office network (clients or servers). Hope this helps.
Robert
"DanJ" <DanJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:86B7F4B6-6171-4EC1-97F6-77EF1FE487E7@xxxxxxxxxxxxxxxx
Hi,
Am I right in assuming that the Branch office server itself has the
demand
dial interface?
Also, if that is the case, I assume the client PCs have their default
gateway set to the LAN IP Address of the Branch Office Server... is that
the
case?
It may be worth doing a Tracert to ensure that the Client PCs are going
the
correct route.
The Static route needs to specify the Demand Dial Interface as the
'Interface' for the Static Route. Specify destination IP Address and
Subnet
Mask for the remote network.
If you can provide a little more info, I may be able to help more, sorry
this response is slightly vague.
Dan
MCSA MCSE 2000/2003
"Robert" wrote:
I have a branch office of which I am setup a demand dial interfact for
the
network to the corporate office. I can browse resources on the
coporate
network from the branch server, but users on the branch lan cannot.
They
can access the internet, but nothing on the corporate web. I have done
a
million different combinations of static routes so the lan users can
access
the corporate network, but nothing seems to be working. Can anyone
help me
out here? I'm at a loss.
Robert
.
- Follow-Ups:
- Re: static routing
- From: Bill Grant
- Re: static routing
- References:
- static routing
- From: Robert
- Re: static routing
- From: Robert
- Re: static routing
- From: Bill Grant
- static routing
- Prev by Date: Re: RRAS Question for you routing gurus
- Next by Date: Re: RRAS Question for you routing gurus
- Previous by thread: Re: static routing
- Next by thread: Re: static routing
- Index(es):
Relevant Pages
|