Vpn connection droppes Windows 8.1 Enterprise

Hi.
I've an issue related VPN connection.
I've setup PPTP connection like this:
Windows 8.1 Ent. ->Wi-Fi -> Dlink DIR-300 -> Ericsson GPON -> FC -> ISP -> Ericsson GPON -> Dlink DSR 500N
After few minutes i connect to the DSR 500N over VPN PPTP, the connection is dropping. Mostly it seems when I'm starting the RDP connection. After this I can normally connect again, but there is another problem, I should delete the ROUTE and Add it again
to have an access in network on another side.
Before this I've the Windows 7 Enterprise on the same computer, and haven't seen any problem like this.
Can you explain me how can I fix it?

Hi!
In this case I would download Fiddler and start it just before you connect to the VPN.
This will show you an exact log of what is happening and why it's happening, the instant it happens.
You can download Fiddler from this site: http://www.telerik.com/fiddler
The log will be clear and it's not as advanced as it might look when you first start it :)
Best regards
Andreas Molin

Similar Messages

  • How to set VPN Connection in Windows 7 64bit?

    Hi
    How can I set up a Vpn in connection in Windows 7 x64 bit.
    Thanks.

    Hi,
    Go to Control panel-Network and Internet-Network sharing Center.
    http://www.windows7hacker.com/index.php/2009/08/how-to-set-up-a-vpn-connection-in-windows-7/
    Note, you should know the login and password to have the Internet access :)

  • How do I stop users from using the standard inbuilt VPN connection in Windows

    We have a UAG Portal setup to check the security of users computers etc then if it is all correct they are presented with the log in and once logged in the are connected to the corpirate network via a SSTP connection.  The all works fine but the issue
    I have is users can bypass all the checking but just going into network connections on their local computer and creating a SSTP VPN connection, like on this webpage http://blogs.technet.com/b/tugait/archive/2011/10/12/how-to-publish-a-vpn-sstp-using-your-uag-in-a-https-trunk.aspx
    Any idea how to stop users being able to do this and forcing them to use Internet Explorer?

    Found my answer on this page  http://technet.microsoft.com/en-us/library/ee809077.aspx 
    "To enforce Forefront UAG portal authentication, do not set users dial-in properties to Allow
    access."

  • SMB and VPN connected to Windows Server 2003

    I have search the web for an answer on this problem, I've only found peoble with same problem, but still no solution :o/
    I wan't to connect to my office (windows2003) from my OSX 10.4.2 at home. I've set up an VPN connection and can PING the server (and others) on the network. Works fine.
    When I connect to the server via SMB://server/ I get a list with all different folders (or servers) I can connect to but I get rejected with the answer Bad name or password. Now to the funny part; I can connect in the Terminal using smbclient with the same user and pwd just rejected in Finder!!!
    I've read about this problem on http://www.macwindows.com/tiger.html#052305a but I can't find a solution. Someone mentioned a bug with apple number #4108992 - Can anyone tell me where I can read about that? Or better - Where I can find a solution. (I've tried to erase keychain)
    Rgds
    /Johan

    My school sets up our network disk space with access via FTP. I don't know if that is an option through your company. While I have to download files to work with them and then upload them again to the network space to access them at work, it does allow me to look at the directory structure. I use an FTP client (not the one built into OS X). This might be an option for you to check on with your IT department. (This also eliminates my need to use VPN.)
    Hope this helps.
    PB G4 15"   Mac OS X (10.4.3)  

  • Setup router to router VPN connecting 2 windows domain networks via 2 RV042 routers

    I am using 2 RV042 routers.  I have created a point to point VPN with Remote Security Group Type= Subnet, using the default IPSec settings. 
    Under advanced settings-  Aggressive Mode, Keep Alive enabled.
    Location A- SBS 2011 standard, Servername=SBSServer, Domainname = Smallbusiness.Local, IP address 10.1.10.50
    DHCP range 10.1.10.100 to 10.1.10.175.  DNS and Print services. No WINS.  
    Location B- Server 2008 R2, Sername=SBSServer, Domain name=Smallbusiness.Local, IP address 192.168.10.50
    DHCP range 192.168.10.100 to 192.168.10.175,  DNS, Print Services and Remote Desktop Services.  No WINS
    I am wondering 2 things.  Can I setup the VPN tunnel to route traffice between the 2 networks without changing the server names.  Leaving the servernames the same.  I have it setup that way but also had netbios broadcast enable.  If I disable netbios broadcast will that be enough for these networks to be independent of each other.  I was hoping not to have to rename the domain and there are advantages to having the same user and domain name when mapping drives between networks.  I have not needed to authenticate those drives or provide credititals for printing either. 
    2) Should I change the domain name so that each network has a unique domain name or, if I change the servername of the 2008 R2 server will that essentially solve my network issues, the primary issue being that location b has clients that occasionally can not find the 2008 R2 domain controller.  After a restart the usually resolve to the correct domain controller.
    Essentially what I am asking is what are the best practices to connect 2 separate Windows domain networks via a VPN and have those networks capable of file sharing to the each others domain server and printing to the network printers at both loations.
    Should I have separate domain names-
    Should I have separate server and computer names-

    "reserved not zero on payload" generally means your pre-shared keys don't match. Try removing the "crypto isakmp key ...." line and retyping it in again on both sides. In particular DON'T cut/paste it from one router config into another, this quite often puts a space character onto the end of the key, which the router interprets as part of the key and they therefore don't match.

  • How can I connect to windows vpn

    Hello,
    I am trying to connect to a Windows VPN through my macbook air running Lion. Anyone know how?

    I was struggling with this for a few days as well!  Finally got it working though ! YAY !
    Here are the steps:
    1. Add this to your registry:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PolicyAgent]
    "AssumeUDPEncapsulationContextOnSendRule"=dword:00000002
    2. Open secpol.msc (click start > search for secpol.msc)
    - Local Policies > Security Options
    - Network Security : LAN Manager Auth Level…
    - Set to: Send LM & NTLMv2 - UseNTLMv2…
    And
    - Network Security : Minimum session security… clients
    - uncheck "Require 128-bit encryption"
    3. Restart PC
    4. Create VPN Connection on Windows 7
    - Host Name: (server IP or yourhost.name.com)
    - PPP Settings : Enable LCP (only)
    - Type: L2TP/IPSec
    - Pre-shared key : yoursharedsecret
    - Data encryption : Optional encryption
    - Allow CHAO and CHAPv2
    5. Router on server-side must allow VPN Passthrough and forward ports: 50, 51, 500, 548, 1701, 1723, 4500 to the server box. Also, do not filter anonymous internet requests, multicast or NAT Redirection but enable SPI Firewall.
    ...now you should be good to go

  • IPad2, Verizon 3G, VPN Connectivity Issues

    Greetings all. I am the systems administrator for my corporation and have seen an issue that I wish to present to the community for discussion.
    For those enterprise users that have an iPad2 with Verizons 3G, are you experiencing connectivity issues while trying to connect to your VPNs from the 3G network? If so, have you found any work around to allow connectivity or does it work fine for you?
    Here's a summary of my issues:
    We have a VPN server built on Debian Linux that has been in operation for over four years. It handles remote VPN connections from Windows, Linux,  Android, OS X, iOS, and from many different devices including multiple flavors of Apple products (iMacs, Minis, MacBooks, iPads, etc.). To date, it has performed flawlessly with assorted devices connecting to it through broadband and assorted 3G networks.
    Recently I purchased an iPad2 with Verizon 3G. I was able to set up the VPN connection using PPTP and connect using a Wi-Fi connection. When I turned off the Wi-Fi and attempted the same connection via Verizon 3G, it fails. I then took an associates iPad1 using AT&T 3G, set up the same connection, and was able to connect. I don't have access to an iPad2 on AT&T 3G so, I can't speak for that.
    Here's the logs from the VPN server while connecting from my iPad2:
    Wi-Fi
    Jul 27 05:20:43 localhost pppd[31694]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
    Jul 27 05:20:43 localhost pppd[31694]: pptpd-logwtmp: $Version$
    Jul 27 05:20:43 localhost pppd[31694]: pppd 2.4.4 started by root, uid 0
    Jul 27 05:20:43 localhost pppd[31694]: Using interface ppp2
    Jul 27 05:20:43 localhost pppd[31694]: Connect: ppp2 <--> /dev/pts/4
    Jul 27 05:20:46 localhost pppd[31694]: Unsupported protocol 'IPv6 Control Protocol' (0x8057) received
    Jul 27 05:20:46 localhost pppd[31694]: found interface eth1 for proxy arp
    Jul 27 05:20:46 localhost pppd[31694]: local  IP address 192.168.1.69
    Jul 27 05:20:46 localhost pppd[31694]: remote IP address 192.168.1.82
    Jul 27 05:20:46 localhost pppd[31694]: pptpd-logwtmp.so ip-up ppp2 scott XXX.XXX.XXX.XXX (removed external IP for security reasons)
    Quick connect, able to utilize VPN connection normally. No issues.
    Verizon 3G
    Jul 27 05:20:29 localhost pppd[31682]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
    Jul 27 05:20:29 localhost pppd[31682]: pptpd-logwtmp: $Version$
    Jul 27 05:20:29 localhost pppd[31682]: pppd 2.4.4 started by root, uid 0
    Jul 27 05:20:29 localhost pppd[31682]: Using interface ppp2
    Jul 27 05:20:29 localhost pppd[31682]: Connect: ppp2 <--> /dev/pts/4
    Jul 27 05:20:32 localhost pppd[31682]: peer refused to authenticate: terminating link
    Jul 27 05:20:33 localhost pppd[31682]: Connection terminated.
    Jul 27 05:20:33 localhost pppd[31682]: Exit.
    As you can see, the peer refuses to authenticate causing the link to be terminated while attempting to connect using Verizons network. This is with the same VPN connection settings on the iPad2 that just worked with WiFi connection from the same device.
    Here's what I can verify with regards to 3G networks:
    Older (<4) iPhones and iPad1 using AT&T can connect
    Windows and OS X based laptops using Sprint 3G can connect
    Android based smart phones using Sprint 3G can connect
    I have not called Verizon or Apple Support yet but, that's next when I have the time. My initial conclusion is that there is something with Verizons 3G services that is causing the issue. It may be that Verizon is using some sort of data compression process that is problematic with VPN transmission. While the log shows an unsupported IPv6 protocol when connecting via Wi-Fi, it still negotiates a successful connection and I don't think that's the root cause for the disconnect. Thoughts?

    Hi Alexander,
    I am running in to the exact same issue (although not with Linux).  Did you ever find a fix for this?  I have some support tickets open with my VAR's, but found your post and thought I would check.  If I find anything I will post.
    Thanks
    Stu

  • Slow VPN Connection

    I have had Windows Server 2012 Essentials setup and running now for over 12 months and have been using the Remote Web Access to share certain files with our employees. When using the RWA you can download files in seconds without issue.
    I recently wanted to setup a VPN connection to the server so that I could remote manage the server if needed rather than have to go to the office all the time. I added the role on the server, forwarded port 1723 as needed whilst at the office. Then at home
    created a VPN connection on my Windows 7 PC. The VPN connects very quickly without issue but when trying to do anything the lag is very slow. On the laptop I used the cmd prompt so I could ping the server to see what was going on, i get a lot of time outs
    when doing anything, even when trying to just open a folder that is also shared by RWA and opens without issue.
    If i use Remote Desktop it just constantly times out and closes, so cant do anything.
    It appears this is just a VPN issue as RWA works perfectly. Any ideas as to what would cause this?

    Hi,
    Regarding the current issue, I suggest we could refer to the following similar thread to see if it helps. Please follow the suggestions Tiger provided in the thread.
    Slow VPN Connection to Windows Server 2008
    http://social.technet.microsoft.com/Forums/en-US/3e68223a-26d8-4f39-a476-e7092c44afd9/slow-vpn-connection-to-windows-server-2008?forum=winserversecurity
    In addition, here is an article about how to troubleshoot VPN slowness issue.
    Why is something so slow over a VPN connection?
    http://projectdream.org/wordpress/2007/03/20/why-is-something-so-slow-over-a-vpn-connection/
    Hope it helps.
    Best Regards,
    Andy Qi
    Andy Qi
    TechNet Community Support

  • Network Location Awareness disconnecting Wi-Fi when VPN connected

    Hi All,
    We have VPN software which creates a virtual NIC. When it connects using the Wi-Fi bearer interface we often see that the Wi-Fi connection drops after exactly 60 seconds from the VPN establishing an IP address. We only get this problem when the VPN is used
    on Windows 8. Windows 7 never has this issue. We have looked at NCSI, allowing packets through the Wi-Fi interface, and network profiles nut no success.
    We found that when the "Network Location Awareness" service is disabled (which also stops the dependent services Network List, HomeGroup and Network Connected Devices Auto-Setup) then the Wi-Fi connection is reliable. This leads us to think that
    NLA takes control of the Wireless interface to drop the connection. We cannot find any information on NLA changes in Windows 8, as we don't get the issue on Windows 7.
    Any insight appreciated.
    Alan

    Hi,
    Have you tried to establish a VPN connection with windows integrated VPN client? If it works, it means that the software VPN client affects the WIFI connection.
    If it still doesn’t work, you may check this,
    Try to connect to other Aps.
    Install latest WIFI NIC driver.
    It could be the security software issue. Try clean boot for a test.
    Besides, is there any error or warning related to WIFI or VPN in the event viewer? It is helpful for further troubleshooting.
    Hope this helps.
    Steven Lee
    TechNet Community Support

  • Possibility to configure Freedome VPN connection on unsupported devices

    I have this idea, which I think would be useful in this world of many different OSes:
    I suggest that you would make it possible to, for example, configure the VPN connection on Windows Phone. Windows Phone has the possibility to configure VPN profiles at the settings, and so do many other OSes that are not supported by Freedome. This would also solve the problem of having no VPN on Linux. Of cource it wouldn't be as easy as pressing a big button, but many privacy-aware users would benefit from it. 

    Hi Jay,
    So, when you say you need to connect your website to your Local Network, is your website a Paas instance or a IaaS instance, i.e., website hosted in a VM using IIS?
    Do you have a single instance of the website or multiple instances that have been added to a VNET and need to be connected to the On-Premise Network?
    What VPN device are you using to connect Azure to On-Prem?
    If you have one website instance that needs to connect to an On-prem network Point-to-Site (P2S) connection would make sense. However, if you have multiple instances of your website in a VNET you would need a Site-to-Site (S2S) connection.
    Please be advised that only devices that support Dynamic Routing Gateway would work when configuring P2S connections.
    Regards,
    Malar.

  • Window 8.1 system unable to access network shares via VPN connection

    Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
    I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
    My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
    The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
    So to access network shares they have to use their domain credentials to create a VPN connection.
    Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
    They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
    those shares either.
    You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
    So...
    I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
    Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

    I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
    This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
    I can see all the shares, so dns seems to be fine right?
    So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
    When I try to create a mapped drive by machine name I receive the following message:
    Windows cannot access \\fileserver.dev.lan\all
    You do not have permissions to access \\fileserver.dev.lan. contact your network administrator  to request access.
    But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
    This only seems to happen on windows 8.1, which leads me to think that has something to do with OS. 
    I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

  • Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

    I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
    from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
    8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
    apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
    Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
    I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS)  improves display
    and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
    remote connections for family, non-commercial use.
    Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
    T. Webster

    Hi,
    It depends on the quality of the network connection to run the software smoothly throuth RDP.  And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
    Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
    whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
    Regarding more information about RDP, please take a look at the following articles:
    Remote Desktop app help
    Remote Desktop Connection: frequently asked questions
    Best regards
    Michael Shao
    TechNet Community Support

  • VPN connection created with CMAK fails to update routing table on Windows 8.1 with error 8000ffff

    When my clients connect their CMAK-created VPN, it fails to run the script to set their routing table with the following error:
    Custom script (to update your routing table) failed (8000ffff)
    My objective is to create a VPN connection with split tunneling - does not use the VPN connection as the client's default gateway.
    All my clients are on Windows 8.1 64-bit, and are logged in with Administrative privileges
    My VPN Clients are on 10.242.2.0/24, my internal network is on 10.172.16.0/24
    I want only traffic for 10.172.16.0 to go via the VPN. Everything else should go via the client's internet connection
    My Connection Manager Administration Kit profile, was created on Windows 2012 R2 CMAK with the following settings:
    "Make this connection the client's default gateway" is UNticked on the IPv4 tab.
    Define a routing table update is specified with a text file containing:
    +++ Start of txt file +++
    REMOVE_GATEWAY
    add 10.172.16.0 mask 255.255.255.0 default metric default if default
    +++ End of txt file +++
    The txt file is saved in DOS/Windows format (not Unicode or UTF-8 which I've read causes problems)
    I've tried everything in lower and upper case in the txt file after reading that the file might be case sensitive
    The following appears on the client with logging enabled:
    [cmdial32] 10:42:34
    03 Pre-Init Event       CallingProcess = C:\WINDOWS\system32\rasautou.exe
    [cmdial32] 10:42:40
    04 Pre-Connect Event    ConnectionType = 1
    [cmdial32] 10:42:40
    06 Pre-Tunnel Event     UserName = UserName Domain =  DUNSetting = VPN (L2TP x64 NoGW) Tunnel DeviceName =  TunnelAddress = vpn.mydomain.tld
    [cmdial32] 10:42:43
    07 Connect Event
    [cmdial32] 10:42:43
    09 Custom Action Exe    ActionType = Connect Actions Description = (none) ActionPath = CMDL32.EXE. The program was launched successfully.
    [cmdial32] 10:42:43
    08 Custom Action Dll    ActionType = Connect Actions Description = to update your routing table ActionPath = C:\Users\UserName\AppData\Roaming\Microsoft\Network\Connections\Cm\VPN64\CMROUTE.DLL ReturnValue
    = 0x8000ffff
    [cmdial32] 10:42:43
    21 On-Error Event       ErrorCode = -2147418113 ErrorSource = to update your routing table
    [cmdial32] 10:42:43
    13 Disconnect Event     CallingProcess = C:\WINDOWS\system32\cmdial32.dll
    Where can I find out what error codes 8000ffff or -2147418113 mean?

    That was it. Thanks, Steven
    "By default, the dial-up entry and the VPN entry have Make this connection the default gateway selected.
    Leave this default in place, and remove any gateways by using the REMOVE_GATEWAY command in the routing table update file itself."
    It seems counter-intuitive to leave
    Make this connection the default gateway selected, when I specifically don't want that behaviour, but leaving it selected and using REMOVE_GATEWAY works for me.

  • VPN Connection Seen As Public Network In Windows 8.1 & No Way To Change It?

    Hello,
    I have a perfectly working VPN setup in Windows 7 however since I have got a Windows 8 computer and subsequently upgraded it to 8.1 when I connect to the VPN it assigns the connection as Public and I cannot view any of the network shares.
    As I understand it, in Windows 8 you could go into the network section of Change PC Settings, right click over the VPN and enable sharing which would convert the public network type to private however there is no longer this option to enable sharing in 8.1
    So I'm left with having to disable the public firewall and then connect to the VPN where it works perfectly but is a bit of a pain.
    I'm hoping someone can help me to change the network type of the VPN connection from Public to Private, unfortunately the laptop runs Windows 8.1 Home Premium so I do not have access to gpedit.msc
    Hope someone can help.
    Regards,
    Mike

    Hi Mike,
    Based on my knowledge, we can use the following method to change the network type of connection from Public to Private.
    Set Network to be Private in Windows 8 and 8.1 in Registry
    1.Press Win + R keys to open the Run dialog, type regedit, and press Enter.
    2.In Registry Editor, navigate to the location below:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
    3.Expand Profiles, click on each long GUID number subkey, and look at its PofileName string value in the right pane to see if it has the current network name (ex: Network) until found.
    4.When you find the correct PofileName for your network name, double click/tap on the Category DWORD value in the same right pane to modify it.
    5.Type in a new Data value number for the network location you want, and click/tap on OK.
    Network location      Data value
    Public                                0
    Private                             1
    Domain                            2
    6.When finished, please reboot your computer.
    Hope this helps.
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Error 720 when establishing VPN connection to RRAS server in Windows 8.1

    Hi,
    I am unable to establish a VPN connection to my Windows Server 2008 R2 RRAS server. I have tried all protocols, but always getting the same error: "Error 720: A connection to the remote computer could not be established. You might need to change
    the network settings for this connection".
    I am able to connect using another Windows 7 computer, on the same network and with exactly the same VPN parameters. So this is clearly not a problem with RRAS, the remote router or firewall and/or the local router.
    Strangely, the connection works by unchecking IPv4 and checking IPv6 in the connection properties. But I need IPv4 to work. All IPv4 settings are blank, nothing statically configured here.
    Note: This is a clean install of Windows 8.1, not an upgrade from a previous version.
    Thank you for helping me out!

    Hi,
    This behavior can occur if your computer and the RAS server don't have a protocol in common, or if RAS is not configured correctly. The error code 720 indicates no PPP control protocols configured.
    Assuming the RRAS is using, we need to make the Windows client is running PPTP too. To do this follow these steps:
    1. Right click VPN connection, and then click Properties.
    2. In the VPN Connection Properties dialog box, click the Networking tab, and make sure you have a protocol that the RAS server runing.
    If you don't have a protocol that the RAS server is running, add the needed protocol:
    1. Click install, click Protocol, and then click Add;
    2. Click the protocol that you need to install, and then click OK.
    3. Click Close in the VPN Connection Properties dialog box.
    Karen Hu
    TechNet Community Support

Maybe you are looking for