Re: Connecting via remote
From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 09/15/04
- Next message: John Holt: "Scheduling"
- Previous message: Miha Pihler: "Re: Connecting via remote"
- In reply to: Phillip Windell: "Re: Connecting via remote"
- Next in thread: Phillip Windell: "Re: Connecting via remote"
- Reply: Phillip Windell: "Re: Connecting via remote"
- Reply: Glenn: "Re: Connecting via remote"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Sep 2004 18:47:06 +0200
Philip,
If I understand Glenn, they have two connections in the branch office. One
is frame relay between the offices and the other is high speed internet
access. I believe you could setup VPN server on this high speed internet
access link. At the same time you would setup VPN on internet connection in
the main office.
Let say this VPN/Router server in branch office would have IP 10.10.10.10
and Exchange server has IP 10.10.10.9. Now what you would have to do on the
clients (e.g. IPs 10.10.10.15-10.10.10.20) is add static route:
route add 10.10.10.9 mask 255.255.255.255 10.10.10.10
Now any request made to Exchange server on IP 10.10.10.0 would be routed to
VPN server and over the Internet to the main office and Exchange.
Of course in the main office you would have another VPN server with IP
10.10.10.11. Now exchange server in the main office would also have to have
static routes for every client in the branch office:
route add 10.10.10.15 mask 255.255.255.255 10.10.10.11
route add 10.10.10.16 mask 255.255.255.255 10.10.10.11
route add 10.10.10.17 mask 255.255.255.255 10.10.10.11
route add 10.10.10.18 mask 255.255.255.255 10.10.10.11
route add 10.10.10.19 mask 255.255.255.255 10.10.10.11
route add 10.10.10.20 mask 255.255.255.255 10.10.10.11
Mike
"Phillip Windell" <@.> wrote in message
news:O$SaArymEHA.2948@TK2MSFTNGP11.phx.gbl...
>
> "Miha Pihler" <mihap-news@atlantis.si> wrote in message
> news:uJc$$uumEHA.2372@TK2MSFTNGP10.phx.gbl...
> > Glen posted in his first post that he needs MAPI access. Yes, he could
> setup
> > RPC over HTTP, but there are few requirements (e.g. Exchange 2003,
Outlook
> > 2003, and few others).
>
> Yes.
>
> > One solution that I see is to use static routes on clients and on
Exchange
> > server. I am not sure how practical this solution would be since I don't
> > know how many clients there are in the remote office. Still this could
be
> > achieved by e.g. logon script.
>
> The problem is that it is all one subnet so there isn't any "routes" to
use.
> In spite of the wide geographical distance, it is still just a simple
single
> segment LAN. In order to have routes there must be segments to route
> between and a router to make it happen. Although the VPN Server can be
> thought of as a router, there still aren't any Layer3 segments.
>
> Now the Internet can provide a second segment as long as VPN doesn't come
> into it. Since the Mail server would have an Internet presents that is on
a
> Public IP#, that gives us a segment to route to. By making sure the name
> used for the mail server by the clients resolves to the Public IP#
> everything should be fine. But VPN won't be used in this case and cannot
be
> used. With VPN the outer part ot the Tunnel does not effect routing, the
> inside of the Tunnel does,...but when you step inside the Tunnel you are
> back to the Private LAN Addresses where everything is one subnet and back
to
> same same problem of not being able to route, so the traffic would ignore
> the VPN and use the 56k private link.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
- Next message: John Holt: "Scheduling"
- Previous message: Miha Pihler: "Re: Connecting via remote"
- In reply to: Phillip Windell: "Re: Connecting via remote"
- Next in thread: Phillip Windell: "Re: Connecting via remote"
- Reply: Phillip Windell: "Re: Connecting via remote"
- Reply: Glenn: "Re: Connecting via remote"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
