Windows 10 Outlook will not connect over VPN

Multi tool use
Been seeing this issue, hope someone else has solved.
When my windows 10 users are connected to VPN, outlook will not connect. No errors, just tries to connect and goes to disconnected. Network drives work properly, hostnames resolve, just Outlook not connecting.
When not connected to VPN, Outlook connects fine. However then users do not have network shares etc.
Have not seen this on any Win7 or 8 users.
Details - Windows 10, Office 2013, Watchguard VPN, Exchange 2010.
networking windows-10 microsoft-outlook vpn
add a comment |
Been seeing this issue, hope someone else has solved.
When my windows 10 users are connected to VPN, outlook will not connect. No errors, just tries to connect and goes to disconnected. Network drives work properly, hostnames resolve, just Outlook not connecting.
When not connected to VPN, Outlook connects fine. However then users do not have network shares etc.
Have not seen this on any Win7 or 8 users.
Details - Windows 10, Office 2013, Watchguard VPN, Exchange 2010.
networking windows-10 microsoft-outlook vpn
1
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56
add a comment |
Been seeing this issue, hope someone else has solved.
When my windows 10 users are connected to VPN, outlook will not connect. No errors, just tries to connect and goes to disconnected. Network drives work properly, hostnames resolve, just Outlook not connecting.
When not connected to VPN, Outlook connects fine. However then users do not have network shares etc.
Have not seen this on any Win7 or 8 users.
Details - Windows 10, Office 2013, Watchguard VPN, Exchange 2010.
networking windows-10 microsoft-outlook vpn
Been seeing this issue, hope someone else has solved.
When my windows 10 users are connected to VPN, outlook will not connect. No errors, just tries to connect and goes to disconnected. Network drives work properly, hostnames resolve, just Outlook not connecting.
When not connected to VPN, Outlook connects fine. However then users do not have network shares etc.
Have not seen this on any Win7 or 8 users.
Details - Windows 10, Office 2013, Watchguard VPN, Exchange 2010.
networking windows-10 microsoft-outlook vpn
networking windows-10 microsoft-outlook vpn
asked Jun 3 '16 at 16:09
AdamAdam
111
111
1
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56
add a comment |
1
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56
1
1
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56
add a comment |
1 Answer
1
active
oldest
votes
What kind of vpn are you using, Windows built-in vpn or some vpn software?
If using Windows built-in vpn, then try this solution:
If you've never used Power Shell, it's pretty easy. In Win10, go to "Start" then find the folder for "Windows Power Shell" click the > to open the folder in the menu, and select the program "Windows Power Shell" by right-clicking on it and selecting "run as administrator."
The Power Shell window will then pop up. If you don't see it, it may be hidden by whatever else you have on your screen. But it will be there.
At the command line, just enter the first command, without the quotes
"Get-VpnConnection"
This will return a detailed listing of the settings for your Microsoft built-in VPN client adapter that you've already set up to connect remotely to a server, i.e., it will show all the settings for each VPN.
Next, perform the second command without the quotes
"Set-VpnConnection -Name "myVPN" -SplitTunneling $True"
Be sure to insert the actual name of your own VPN (whatever you named it and what is shown next to "Name" after you perform the first command and get the settings returned) in the space for "myVPN", but be sure to place the command "-Name" before it.
Once you've typed in both commands, hit Enter.
The commands are case-sensitive, so be mindful of that.
Once you've entered both commands, nothing will happen, no pop-ups or anything.
Just quit powershell and try to connect to your vpn
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1084104%2fwindows-10-outlook-will-not-connect-over-vpn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What kind of vpn are you using, Windows built-in vpn or some vpn software?
If using Windows built-in vpn, then try this solution:
If you've never used Power Shell, it's pretty easy. In Win10, go to "Start" then find the folder for "Windows Power Shell" click the > to open the folder in the menu, and select the program "Windows Power Shell" by right-clicking on it and selecting "run as administrator."
The Power Shell window will then pop up. If you don't see it, it may be hidden by whatever else you have on your screen. But it will be there.
At the command line, just enter the first command, without the quotes
"Get-VpnConnection"
This will return a detailed listing of the settings for your Microsoft built-in VPN client adapter that you've already set up to connect remotely to a server, i.e., it will show all the settings for each VPN.
Next, perform the second command without the quotes
"Set-VpnConnection -Name "myVPN" -SplitTunneling $True"
Be sure to insert the actual name of your own VPN (whatever you named it and what is shown next to "Name" after you perform the first command and get the settings returned) in the space for "myVPN", but be sure to place the command "-Name" before it.
Once you've typed in both commands, hit Enter.
The commands are case-sensitive, so be mindful of that.
Once you've entered both commands, nothing will happen, no pop-ups or anything.
Just quit powershell and try to connect to your vpn
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
add a comment |
What kind of vpn are you using, Windows built-in vpn or some vpn software?
If using Windows built-in vpn, then try this solution:
If you've never used Power Shell, it's pretty easy. In Win10, go to "Start" then find the folder for "Windows Power Shell" click the > to open the folder in the menu, and select the program "Windows Power Shell" by right-clicking on it and selecting "run as administrator."
The Power Shell window will then pop up. If you don't see it, it may be hidden by whatever else you have on your screen. But it will be there.
At the command line, just enter the first command, without the quotes
"Get-VpnConnection"
This will return a detailed listing of the settings for your Microsoft built-in VPN client adapter that you've already set up to connect remotely to a server, i.e., it will show all the settings for each VPN.
Next, perform the second command without the quotes
"Set-VpnConnection -Name "myVPN" -SplitTunneling $True"
Be sure to insert the actual name of your own VPN (whatever you named it and what is shown next to "Name" after you perform the first command and get the settings returned) in the space for "myVPN", but be sure to place the command "-Name" before it.
Once you've typed in both commands, hit Enter.
The commands are case-sensitive, so be mindful of that.
Once you've entered both commands, nothing will happen, no pop-ups or anything.
Just quit powershell and try to connect to your vpn
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
add a comment |
What kind of vpn are you using, Windows built-in vpn or some vpn software?
If using Windows built-in vpn, then try this solution:
If you've never used Power Shell, it's pretty easy. In Win10, go to "Start" then find the folder for "Windows Power Shell" click the > to open the folder in the menu, and select the program "Windows Power Shell" by right-clicking on it and selecting "run as administrator."
The Power Shell window will then pop up. If you don't see it, it may be hidden by whatever else you have on your screen. But it will be there.
At the command line, just enter the first command, without the quotes
"Get-VpnConnection"
This will return a detailed listing of the settings for your Microsoft built-in VPN client adapter that you've already set up to connect remotely to a server, i.e., it will show all the settings for each VPN.
Next, perform the second command without the quotes
"Set-VpnConnection -Name "myVPN" -SplitTunneling $True"
Be sure to insert the actual name of your own VPN (whatever you named it and what is shown next to "Name" after you perform the first command and get the settings returned) in the space for "myVPN", but be sure to place the command "-Name" before it.
Once you've typed in both commands, hit Enter.
The commands are case-sensitive, so be mindful of that.
Once you've entered both commands, nothing will happen, no pop-ups or anything.
Just quit powershell and try to connect to your vpn
What kind of vpn are you using, Windows built-in vpn or some vpn software?
If using Windows built-in vpn, then try this solution:
If you've never used Power Shell, it's pretty easy. In Win10, go to "Start" then find the folder for "Windows Power Shell" click the > to open the folder in the menu, and select the program "Windows Power Shell" by right-clicking on it and selecting "run as administrator."
The Power Shell window will then pop up. If you don't see it, it may be hidden by whatever else you have on your screen. But it will be there.
At the command line, just enter the first command, without the quotes
"Get-VpnConnection"
This will return a detailed listing of the settings for your Microsoft built-in VPN client adapter that you've already set up to connect remotely to a server, i.e., it will show all the settings for each VPN.
Next, perform the second command without the quotes
"Set-VpnConnection -Name "myVPN" -SplitTunneling $True"
Be sure to insert the actual name of your own VPN (whatever you named it and what is shown next to "Name" after you perform the first command and get the settings returned) in the space for "myVPN", but be sure to place the command "-Name" before it.
Once you've typed in both commands, hit Enter.
The commands are case-sensitive, so be mindful of that.
Once you've entered both commands, nothing will happen, no pop-ups or anything.
Just quit powershell and try to connect to your vpn
answered Jun 3 '16 at 16:37
NirabhroMakhalNirabhroMakhal
12
12
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
add a comment |
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Using the Watchguard SSL VPN Client
– Adam
Jun 3 '16 at 17:03
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
Thanks for this fix - it worked for me. Take the case sensitive part seriously! As an old newbie, I assumed that PowerShell, being a DOS prompt, was not case sensitive, but it is! Also, be sure your VPN name has no spaces in it. You can edit it easily thru VPN setup in Options. sarah
– Albin
Nov 4 '18 at 0:57
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1084104%2fwindows-10-outlook-will-not-connect-over-vpn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Zt8VjkfU XFTrCbdyo,93,YdwOxj8c5k4mY,FjY
1
Are you the VPN administrator?
– Julie Pelletier
Jun 3 '16 at 16:56