The first useful screen of the wizard asks you to determine exactly what kind of network connection you'd like to create. For this article, you're connecting to a VPN, so choose the "Connect to the network at my workplace" option. It doesn't really matter where your VPN resides. Click Next when you're ready. There are two ways that you can connect to your workplace— 1 dial-up; or 2 VPN.
For this step, select the Virtual Private Network connection option and click the Next button. The next step of the wizard asks you to name the new connection. You can use just about anything you want here since this just helps to keep track of what's what on your client machine. A name is useful if you have more than one VPN connection to manage. The next step of the wizard asks you to decide which users should be able to use this new connection.
Do you want it available for just the use of the currently logged in user, or should it be available for any user? Keep in mind that, even if a connection is available to a logged in user that you don't want connected to the VPN, user must still provide valid credentials to actually attach to the VPN services.
For this example, I've enabled the VPN connection for my use only. Finally, you're finished creating the initial connection, as evidenced by a screen that looks like the one shown in Figure F. Click Finish. The Network Connection Wizard just creates the initial connection with common parameters.
Now that it's created, you need to make modifications based on your environment. In particular, I've often run into trouble with Network Connection Wizard-created VPN connections' default gateway setting—more on that in a bit. As soon as you're done with the Network Connection Wizard, the new connection pops up so that you can connect to the remote VPN server. The example, shown below in Figure G , contains the username and password, which I provided.
Before you hit the Connect button, take a little time to adjust the client settings. Thanks to the Mikrotik RouterOS and similar platforms, setup for this kind of tunnel is very simple today. Moreover, this tutorial is the client-side part of our PPTP series. You can find here the detailed explanation of the server side setup. Therefore, I would not recommended to you to expose those systems to the Internet. The PPTP protocol was developed by a group of vendors during the late s. The part of its popularity lays in the simplicity of the implementation and the built-in support in virtually every operating system.
Although we rarely need VPN on the server platform, we can do it with ease in the same way. Due the lack of adequate security level, I recommend that you use this protocol only in your lab. We will see all our connections in this window. We will choose the New Connection Wizard. Therefore, choose appropriate connection from the drop-down list.
In case you want to use the DNS a. Notice the checkbox labeled "Enable security on the selected interface by setting up Basic Firewall" underneath the list of network interfaces. It's a good idea to enable since option it helps to protect your server from outside attack. A hardware firewall is still a good idea, too. With the selection of the Internet-connected NIC out of the way, you need to tell the RRAS wizard which network external clients should connect to in order to access resources.
Notice that the adapter selected for Internet access is not an option here. Just like every other client out there, your external VPN clients will need IP addresses that are local to the VPN server so that the clients can access the appropriate resources. Second, you can have your VPN server handle the distribution of IP addresses for any clients that connect to the server. To make this option work, you give your VPN server a range of available IP addresses that it can use.
This is the method I prefer since I can tell at a glance exactly from where a client is connecting. If they're in the VPN "pool" of addresses, I know they're remote, for example. So, for this setting, as shown in Figure F below, I prefer to use the "From a specified range of addresses" option. Make your selection and click Next. If you select the "From a specified range of addresses" option on the previous screen, you now have to tell the RRAS wizard exactly which addresses should be reserved for distribution to VPN clients.
To do this, click the New button on the Address Range Assignment screen. Type in the starting and ending IP addresses for the new range and click OK. The "Number of addresses" field will be filled in automatically based on your entry. This way when you are accessing your VPN server from outside, your router will know where to send the request.
Saturday, August 2, PM. Monday, August 4, AM. Your router must support gre protocol 47 and most do. Make sure you forward PPTP port to See page on your Router's manual. Tuesday, August 5, PM. Thursday, August 7, AM. Monday, August 18, AM. Monday, August 18, PM. Tuesday, August 19, AM. Sorry, I should check in more often. You may have a differnet revision. For testing purposes, I use an inexpensive D-Link router which goes for much less than the Zyzel 2.
Make sure your permissions are set correctly and you have no firewalls enabled, or configure accordingly.
0コメント