RE: 2 router to internal sbs std network
- From: "rpaverd" <rpaverd@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Apr 2005 07:19:03 -0700
Mike,
Assuming you have your VPN set up correctly, all your Ip addresses in your
remote location should be visible to the main office location - that is, you
can ping all PCs from both locations, you may need to set up static routes
for the remote site to communicate with the main office.
Therefore, assuming main office address range is 10.0.120.x with router at
10.0.120.1 and remote office range is 192.168.120.x with router at
192.168.120.1 you should add the static routes 10.0.120.0 255.255.255.0
192.168.120.1 to your remote office router and 192.168.20.0 255.255.255.0
10.0.120.1 to the main office router.
This is dependent on the type of LAN to LAN VPN you have set up..
You may have to change your IIS settings to allow users on the 192.168.120
network to access companyweb.
DHCP will not work across a routed connection therefore the remote site IP
addresses will need to be allocated by your router, but remember to retain
the server IP address for DNS
Have fun,
good luck
"mike" wrote:
> Im able to connect to router to router(main office to remote site) but how is
> it done that i want my network to see it only one big network and i want to
> use the log on screen with out using the xp VPN( i just want to use the
> router to router vpn)
>
> thanks
.
- Follow-Ups:
- RE: 2 router to internal sbs std network
- From: mike
- RE: 2 router to internal sbs std network
- References:
- 2 router to internal sbs std network
- From: mike
- 2 router to internal sbs std network
- Prev by Date: Some websites not publishing
- Next by Date: Re: New Security Group Does Not Work
- Previous by thread: 2 router to internal sbs std network
- Next by thread: RE: 2 router to internal sbs std network
- Index(es):
Relevant Pages
|
