Why isn't my VPN setup working?











up vote
0
down vote

favorite












I'm attempting to setup remote access via VPN. I have found the Windows 10 'incoming connections' feature which seems to act as a VPN server. I have PPTP passthrough enabled on my router. I have a static IP address from my ISP, and their modem configured to full-bridge mode.



The first place I'm confused is that when I purchased the static IP address, the ISP provided two IP addresses... one as the gateway, and another as the 'usable' address. They said I should use the 'usable' for my VPN connections. However, I'm unable to ping the usable address - it times out. I can, however, ping the gateway address just fine.



When I setup the 'incoming connections' on the machine that hosts the files I'm trying to access, it allowed me to create what seemed to be VPN credentials for a user that I created there. Then, to test, I connected a laptop to the hotspot on my phone to see if I could reach the host machine via VPN. For this, I went through the Windows 10 VPN settings as follows:



VPN Provider: Windows (built-in)
Connection name: Test
Server name or address: The 'usable' address provided by the ISP, but I've tried the gateway address they gave me as well... they both fail (errors listed below)
VPN type: Point to Point Tunneling Protocol (PPTP)
Type of sign-in info: User name and password
User name (optional): Username I created on the Windows 10 VPN server through 'incoming connections'
Password (optional): Password I created on the Windows 10 VPN server through 'incoming connections'
When I attempt to connect to the usable address, it first says verifying sign-in info, and then proceeds to "Connecting to [usable address]"... which tells me that it was able to authenticate the VPN user I created above. Good right? Well then it says:



The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.



Out of curiosity, I tried using the gateway address instead of the usable address... and that spits out:



The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.



Ok, enough typing for now... oh, by the way, the machines are both Windows 10 and the router is a Linksys EA6350.



Any help is greatly appreciated!










share|improve this question






















  • But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
    – grawity
    Dec 2 at 20:39










  • Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
    – iwalkathinline
    Dec 2 at 23:13










  • You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
    – Appleoddity
    Dec 2 at 23:43

















up vote
0
down vote

favorite












I'm attempting to setup remote access via VPN. I have found the Windows 10 'incoming connections' feature which seems to act as a VPN server. I have PPTP passthrough enabled on my router. I have a static IP address from my ISP, and their modem configured to full-bridge mode.



The first place I'm confused is that when I purchased the static IP address, the ISP provided two IP addresses... one as the gateway, and another as the 'usable' address. They said I should use the 'usable' for my VPN connections. However, I'm unable to ping the usable address - it times out. I can, however, ping the gateway address just fine.



When I setup the 'incoming connections' on the machine that hosts the files I'm trying to access, it allowed me to create what seemed to be VPN credentials for a user that I created there. Then, to test, I connected a laptop to the hotspot on my phone to see if I could reach the host machine via VPN. For this, I went through the Windows 10 VPN settings as follows:



VPN Provider: Windows (built-in)
Connection name: Test
Server name or address: The 'usable' address provided by the ISP, but I've tried the gateway address they gave me as well... they both fail (errors listed below)
VPN type: Point to Point Tunneling Protocol (PPTP)
Type of sign-in info: User name and password
User name (optional): Username I created on the Windows 10 VPN server through 'incoming connections'
Password (optional): Password I created on the Windows 10 VPN server through 'incoming connections'
When I attempt to connect to the usable address, it first says verifying sign-in info, and then proceeds to "Connecting to [usable address]"... which tells me that it was able to authenticate the VPN user I created above. Good right? Well then it says:



The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.



Out of curiosity, I tried using the gateway address instead of the usable address... and that spits out:



The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.



Ok, enough typing for now... oh, by the way, the machines are both Windows 10 and the router is a Linksys EA6350.



Any help is greatly appreciated!










share|improve this question






















  • But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
    – grawity
    Dec 2 at 20:39










  • Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
    – iwalkathinline
    Dec 2 at 23:13










  • You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
    – Appleoddity
    Dec 2 at 23:43















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm attempting to setup remote access via VPN. I have found the Windows 10 'incoming connections' feature which seems to act as a VPN server. I have PPTP passthrough enabled on my router. I have a static IP address from my ISP, and their modem configured to full-bridge mode.



The first place I'm confused is that when I purchased the static IP address, the ISP provided two IP addresses... one as the gateway, and another as the 'usable' address. They said I should use the 'usable' for my VPN connections. However, I'm unable to ping the usable address - it times out. I can, however, ping the gateway address just fine.



When I setup the 'incoming connections' on the machine that hosts the files I'm trying to access, it allowed me to create what seemed to be VPN credentials for a user that I created there. Then, to test, I connected a laptop to the hotspot on my phone to see if I could reach the host machine via VPN. For this, I went through the Windows 10 VPN settings as follows:



VPN Provider: Windows (built-in)
Connection name: Test
Server name or address: The 'usable' address provided by the ISP, but I've tried the gateway address they gave me as well... they both fail (errors listed below)
VPN type: Point to Point Tunneling Protocol (PPTP)
Type of sign-in info: User name and password
User name (optional): Username I created on the Windows 10 VPN server through 'incoming connections'
Password (optional): Password I created on the Windows 10 VPN server through 'incoming connections'
When I attempt to connect to the usable address, it first says verifying sign-in info, and then proceeds to "Connecting to [usable address]"... which tells me that it was able to authenticate the VPN user I created above. Good right? Well then it says:



The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.



Out of curiosity, I tried using the gateway address instead of the usable address... and that spits out:



The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.



Ok, enough typing for now... oh, by the way, the machines are both Windows 10 and the router is a Linksys EA6350.



Any help is greatly appreciated!










share|improve this question













I'm attempting to setup remote access via VPN. I have found the Windows 10 'incoming connections' feature which seems to act as a VPN server. I have PPTP passthrough enabled on my router. I have a static IP address from my ISP, and their modem configured to full-bridge mode.



The first place I'm confused is that when I purchased the static IP address, the ISP provided two IP addresses... one as the gateway, and another as the 'usable' address. They said I should use the 'usable' for my VPN connections. However, I'm unable to ping the usable address - it times out. I can, however, ping the gateway address just fine.



When I setup the 'incoming connections' on the machine that hosts the files I'm trying to access, it allowed me to create what seemed to be VPN credentials for a user that I created there. Then, to test, I connected a laptop to the hotspot on my phone to see if I could reach the host machine via VPN. For this, I went through the Windows 10 VPN settings as follows:



VPN Provider: Windows (built-in)
Connection name: Test
Server name or address: The 'usable' address provided by the ISP, but I've tried the gateway address they gave me as well... they both fail (errors listed below)
VPN type: Point to Point Tunneling Protocol (PPTP)
Type of sign-in info: User name and password
User name (optional): Username I created on the Windows 10 VPN server through 'incoming connections'
Password (optional): Password I created on the Windows 10 VPN server through 'incoming connections'
When I attempt to connect to the usable address, it first says verifying sign-in info, and then proceeds to "Connecting to [usable address]"... which tells me that it was able to authenticate the VPN user I created above. Good right? Well then it says:



The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.



Out of curiosity, I tried using the gateway address instead of the usable address... and that spits out:



The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.



Ok, enough typing for now... oh, by the way, the machines are both Windows 10 and the router is a Linksys EA6350.



Any help is greatly appreciated!







networking vpn






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 2 at 20:00









iwalkathinline

12




12












  • But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
    – grawity
    Dec 2 at 20:39










  • Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
    – iwalkathinline
    Dec 2 at 23:13










  • You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
    – Appleoddity
    Dec 2 at 23:43




















  • But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
    – grawity
    Dec 2 at 20:39










  • Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
    – iwalkathinline
    Dec 2 at 23:13










  • You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
    – Appleoddity
    Dec 2 at 23:43


















But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
– grawity
Dec 2 at 20:39




But have you configured that 'usable' address in some device? (Depending on ISP, either the router or the VPN server itself.) IMHO, if the address doesn't work yet, you really need to fix that first and configuring the VPN is a waste of time until then.
– grawity
Dec 2 at 20:39












Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
– iwalkathinline
Dec 2 at 23:13




Yes I added the usable address to the router, and it made the internet work again so I think that part is configured correctly.
– iwalkathinline
Dec 2 at 23:13












You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
– Appleoddity
Dec 2 at 23:43






You need to do more than turn on pptp pass through. You need to forward TCP port 1723 to your VPN server.
– Appleoddity
Dec 2 at 23:43

















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380257%2fwhy-isnt-my-vpn-setup-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380257%2fwhy-isnt-my-vpn-setup-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕