5 replies
by espen
The best solution is to create a full mesh
network, with leased lines between them,
setting up an IP subnet in each branch,
routing between them. ideally, you would
have one server in each branch, serving
DHCP, and DNS. You don't actually have
to use Wins. If you are going to use one
central DHCP server, you need to bridge
the different branches, rather than route
them.
Then you can set up one leased line to
the internet, and use that one for all
branches to connect to the internet.
I would suggest upscaling the access
databases to SQL, as that makes your life
a lot easier. (Access over IP will behave
funny, I think..)
by infosysguy
by mpdcsup
If you're going to go to the expense of leased lines and a private WAN (which isn't cost-effective for something driven off MS Access). Not only would you not want to bridge (a flat model just does not bode well on a mixed-speed network), you woulddefinitely want WINS running (or your local offices would see only equipment in the local office). As for DHCP, you can use a single DHCP server on multiple subnets if you know what you're doing.
As for the task at hand, though, I reiterate:
You are mixing apples and oranges here. Virtual Private Networking is a security method and an intranet is an information sharing methodology that assumes security exists in the first place. Tying your offices together over public lines without VPN would open your internal networks to other parties.
You might be able to get by with an Extranet, but without knowing more details about the application and its implementation, I wouldn't even be able to begin making any recommendations.
by infosysguy
by infosysguy
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending