Question Locked

VPNs

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Management has called for us to install a server in our main office - we've decided on Windows Server 2008 Standard.
However, we have a *small* sister office that only has a network (no server) about 100 miles away that should also be able to log on and share network resources.
Then we might have some 'travelling' users such as those that might plug into the internet at a hotel.
In addition we have a *small* remote office in the Democratic Republic of Congo (we are in South Africa) that would also need to access.

Management has specifically mentioned the probable implementation of a VPN solution.

Unfortunately VPNs are complex beasts for me, can you perhaps advise me on the best or most feasible solution?

Here are some also related and random questions - you don't have to answer them, but they give you an example of where I'm at:
1) Is a VPN even necessary?
2) What relevant solutions does Windows Server 2008 Standard offer?
3) Would the VPN services of Windows Server 2008 be sufficient?
4) Microsoft advises me that the VPN services of Windows Server are only relevant for server-to-server. They say we'd have one server here, one server at our sister office. Is this correct?
5) Microsoft also advises me that my relevant solutions are Terminal Service sessions or a server-to-server solution. Do you think this is accurate?
6) We have a Netgear router-to-router VPN solution to connect the two branches, but this is expensive. Do you believe this expense might be justified?
7) Any useful advice would be appreciated.

Thanks guys! I owe you one!

3 replies

by robo_dev

First of all, a VPN is very necessary. In the threat environment that currently exists on the Intranet, servers of any type are under constant attack from an ever more sophisticated array of both human and bot attackers. I've seen servers and even whole networks compromised totally as the result of one single SSH vulnerability.

My advice is not to bother with any of the Microsoft VPN solutions; they are both less secure and more trouble to support.

A hardware-based solution from Cisco, for example, is going to do everything you need it to do. Even a low-cost Cisco 800-series router can do VPNs very well. More speed and more features cost more money.

Most hardware-based VPN solutions from Cisco and others can provide both site-to-site and user-VPNs in the same box.

A hardware-based solution is not going to be cheap. But it will be much more secure, faster, more reliable, and easier to support. In other words, you get what you pay for....

http://computer.howstuffworks.com/vpn3.htm

http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns142/networking_solutions_sub_solution_home.html

Book on VPNs:
http://books.google.com/books?id=PMRmPPjTkVsC&pg=PA18&lpg=PA18&dq=site-tosite+vpn&source=bll&ots=85NSqvIbln&sig=S7z_lfsseUM8Wf5bJnLI5RpHOQo&hl=en&ei=P28VSqKrEJ3FtgfHmPDjDA&sa=X&oi=book_result&ct=result&resnum=11

by nimmo

First up you should always try to keep as many resources locally as you can, since the branch offices don't have a local server the users there would be best off using the Terminal server (make sure you have appropriate bandwidth in both locations for this)

Mobile users should always use a PPTP VPN connection (any VPN solution is fine) to the SBS server when connecting back to the domain; I'd advise you should create a new DNS A record for this purpose i.e. remote.domain.com or something similar.

If you did put a server in the branch office's you should make it an AD replica and global catalog so that local users in the branch office don't need to authenticate across the WAN to get on the network.

Definitely put a VPN in place between the two servers but make sure when you do that you aren't sending all traffic through the VPN just domain traffic.

This discussion is closed to new replies.