Virtual Private Networking (VPN) in Windows 2000

684 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
684
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Virtual Private Networking (VPN) in Windows 2000

  1. 1. Virtual Private Networking (VPN) in Windows 2000 Lee Gibson Support Professional Premier Support Microsoft Corporation
  2. 2. VPN Introduction <ul><li>Virtual private networking (VPN) in Microsoft ® Windows ® 2000 allows mobile users to connect over the Internet to a remote network. </li></ul><ul><li>With virtual private networking, the user calls the local ISP and then uses the Internet to make the connection to the Network Access Server (NAS). </li></ul><ul><li>Users only make a local call to the ISP instead of expensive long distance telephone calls to the remote access server. </li></ul>
  3. 3. Connecting Intranet Computers <ul><li>In some corporate networks, the departmental data is so sensitive that the department LAN is physically disconnected from the corporate network. </li></ul><ul><li>VPN allows the administrator to ensure that only the users on the corporate network with appropriate permissions can gain access to the protected resources of the department. </li></ul>
  4. 4. Microsoft Layer 2 Tunneling Protocols <ul><li>PPTP – Point-to-Point Tunneling Protocol </li></ul><ul><ul><li>Uses a TCP connection for tunnel maintenance and generic routing encapsulated PPP frames for tunneled data. </li></ul></ul><ul><ul><li>The payloads of the encapsulated PPP frames can be encrypted and/or compressed. </li></ul></ul><ul><li>L2TP – Layer 2 Tunneling Protocol </li></ul><ul><ul><li>Uses UDP and a series of L2TP messages for tunnel maintenance. </li></ul></ul>
  5. 5. VPN Requirements <ul><li>User authentication </li></ul><ul><li>Address management </li></ul><ul><li>Data encryption </li></ul><ul><li>Key management </li></ul><ul><li>Multi-protocol support </li></ul>
  6. 6. User Authentication <ul><li>The solution must identify the user’s identity and only allow access to authorized users. </li></ul><ul><li>The user account can be a local account on the VPN server or, in most cases, a domain account granted appropriate dial-in permissions. </li></ul><ul><li>The default policy for remote access is “Allow access if dial-in permission is enabled.” </li></ul>
  7. 7. Address Management <ul><li>VPN must assign the client an IP address on the private network. </li></ul><ul><li>The VPN server can assign the clients IP address using DHCP or a static pool of IP addresses. </li></ul><ul><li>Clients typically will have an IP address from the ISP and an IP on the private network after the VPN connection is established. </li></ul>
  8. 8. Data Encryption <ul><li>Data sent and received over the Internet must be encrypted for privacy. </li></ul><ul><li>PPTP and L2TP use PPP-based data encryption methods. </li></ul><ul><li>Optionally you can use Microsoft Point-to-Point Encryption (MPPE), based on the RSA RC4 algorithm. </li></ul><ul><li>Microsoft Implementation of the L2TP protocol uses IPSec encryption to protect the data stream from the client to the tunnel server. </li></ul>
  9. 9. Key Management <ul><li>VPN solution must generate and refresh encryption keys for the client and server. </li></ul><ul><li>MPPE relies on the initial key generated during user authentication, and then refreshes it periodically. </li></ul><ul><li>IPSec negotiates a common key during the ISAKMP exchange, and also refreshes it periodically. </li></ul>
  10. 10. Multi-protocol Support <ul><li>Microsoft Layer 2 Tunneling Protocol supports multiple payload protocols, which makes it easy for tunneling clients to access their corporate networks using IP, IPX, and NetBEUI. </li></ul>
  11. 11. VPN Server Configuration <ul><li>A typical VPN is server is multihomed. It has a one network interface that is connected to the Internet and has an Internet IP address. The second network adapter is connected to the private corporate network and has an IP address on the private network. </li></ul><ul><li>The default gateway needs to be assigned on the public network or Internet interface on the VPN Server. The private network should not contain a default gateway. If you have to route beyond the private network, you should add static routes. This is documented in our Knowledge Base article Q217079. </li></ul>
  12. 12. Configuring a VPN Server <ul><li>The following slides show screen shots of how to configure a VPN server to accept VPN connections over the Internet. </li></ul><ul><li>The slides show a typical setup of a multihomed VPN server with one network adapter connected to the Internet and another network adapter connected to the private network. </li></ul>
  13. 13. First Step: Configure Routing and Remote Access
  14. 14. On the Welcome screen, click Next
  15. 15. Select “Virtual private network (VPN) server”
  16. 16. Select “Yes, all of the available protocols are on this list”
  17. 17. Select from the “Internet connections” list. This creates custom filters on the Internet connection.
  18. 18. IP Address Assignment lets you pick your method for IP address assignment.
  19. 19. For this example, we created a static pool of IP addresses to assign clients.
  20. 20. Allows you to specify a RADIUS server, if you are using RADIUS authentication.
  21. 21. Finish Routing and Remote Access Server setup. Now you will be ready to accept VPN connections.
  22. 22. Notes from Our Setup <ul><li>When we selected our “Internet connection,” the wizard automatically built input and output filters on our Internet adapter. This prevents you from being able to ping the adapter and also limits other types of communications. The following slides show the screen shots of the filters that are automatically created by the user. </li></ul>
  23. 23. Input Filters
  24. 24. Input Filters (2)
  25. 25. Output Filters
  26. 26. Output Filters (2)

×