One type of VPN network topology is the "hub and spoke" VPN network. In the hub and spoke network, all branch offices connect to the central office and each office is able to connect to resources on the central network, as well as other offices, by going through their local VPN gateway to link to the central office. Want to know more? Click and link and read all about it.
A much asked question on the message boards is how to pass an IPSec VPN client through the ISA Server. It can be done if and only if the IPSec implementation supports a feature called NAT Traversal. If you want to know why, how it works and how you can pass it through ISA Server, read on.
Do you need to create a gateway to gateway VPN router setup between a member server on one side and a domain controller on this other? If so, check out part 2 of this article on how to do it!
A scenario I’m seeing a lot of is where the central office runs ISA Server and the remote offices also want to run ISA Server. Not only do the remote offices want to run ISA Server, they also want the ISA Server to be a domain controller in the main domain. This allows users at the branch office to authenticate locally and use a local DNS server to resolve names throughout the organization (as well as the Internet).
Featured Links*
Receive all the latest articles by email!
Receive Real-Time & Monthly ISAserver.org article updates in your mailbox. Enter your email below! Click for Real-Time sample & Monthly sample
Become an ISAserver.org member!
Discuss your ISA Server issues with thousands of other ISA Server experts. Click here to join!