Win10 OpenVPN domain machine cannot find a domain controllerFind name of Active Directory domain controllerDomain Controller / DNS Issue - Creating Network of Virtual Machines for DevelopmentCan't connect to domain controllerHow do I ensure that a member server DNS client (dnscache) is not initialized until its hyper-v domain controller has started?Domain Controller without DNS on remote site fails to authenticateAn Active Directory Domain Controller to the domain … could not be contactedHow can I connect VS2013 Release Management on a non-domain Windows 10 machineWindows 10 OpenVPN Client connects but can't access anythingDomain controller could not be contactedRDP from Win7 to Win10 doesnt work - from Win10 to Win7 works - GPO?
I sent an angry e-mail to my interviewers about a conflict at my home institution. Could this affect my application?
Digital signature that is only verifiable by one specific person
What is the context for Napoleon's quote "[the Austrians] did not know the value of five minutes"?
Someone who is granted access to information but not expected to read it
Cremated People Pottery
How to know whether to write accidentals as sharps or flats?
How did the European Union reach the figure of 3% as a maximum allowed deficit?
Should I email my professor to clear up a (possibly very irrelevant) awkward misunderstanding?
What made the Ancient One do this in Endgame?
Manager wants to hire me; HR does not. How to proceed?
How to remove multiple elements from Set/Map AND knowing which ones were removed?
Can I give my friend the sour dough "throw away" as a starter to their sourdough starter?
Can I appeal credit ding if ex-wife is responsible for paying mortgage?
What is the color associated with lukewarm?
How would Japanese people react to someone refusing to say “itadakimasu” for religious reasons?
Co-worker is now managing my team. Does this mean that I'm being demoted?
What does the output current rating from an H-Bridge's datasheet really mean?
How can the US president give an order to a civilian?
Is there a term for someone whose preferred policies are a mix of Left and Right?
Does PC weight have a mechanical effect?
Does anyone recognize these rockets, and their location?
Can artificial satellite positions affect tides?
How to address players struggling with simple controls?
...and then she held the gun
Win10 OpenVPN domain machine cannot find a domain controller
Find name of Active Directory domain controllerDomain Controller / DNS Issue - Creating Network of Virtual Machines for DevelopmentCan't connect to domain controllerHow do I ensure that a member server DNS client (dnscache) is not initialized until its hyper-v domain controller has started?Domain Controller without DNS on remote site fails to authenticateAn Active Directory Domain Controller to the domain … could not be contactedHow can I connect VS2013 Release Management on a non-domain Windows 10 machineWindows 10 OpenVPN Client connects but can't access anythingDomain controller could not be contactedRDP from Win7 to Win10 doesnt work - from Win10 to Win7 works - GPO?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
We converted to an AD environment a few months ago. From my home office, I have a Win10 laptop that I joined to our domain with much difficulty (had to set the AD dns server on my local LAN) as compared to my Win7 desktop (never did anything special) but did manage to join and can logon as my domain self after I started VPN with a local account. Later, I could login just as my domain self w/o VPN running as I presumably used cached creds. Did not have this issue with Win7.
And my laptop OpenVPN networks initially were showing up as Public and I used PS set-netconnectionprofile to be Private (could not set DomainAuthenticated) but that was no help.
On the Win10 machine (as on the desktop) I have SecurePoint OpenVPN connected to all 3 of our AD sites just fine. I can ping 3 domain controllers, I can do an nslookup on _LDAP._TCP.DC._MSDCS.ad.mydomain.com and find all 3 of my DCs, I can ping all the domain machines with unqualified machine names, etc.
I seem to be able to do everything except -
I have to use my domain suffix when logging on (user@ad.mydomain.com not just user). Don't have to do this on my other machine.
gpupdate fails saying it cannot connect to a domain controller.
Any ideas why gpupdate fails? I see no useful info in the event logs, and my Win7 desktop using the same network runs fine in respect to domain access. I'm suspect of Win10 and/or the SecurePoint OpenVPN on Win10 yet most everything works just fine.
This "may" be related to the adapter binding order. I am unable to change the binding order of adapters in Win10 like I can in Win7 (see http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1) for the problem description.
active-directory domain-controller windows-10
asked Nov 7 '15 at 18:18
DaveDave
1144
add a comment |
We converted to an AD environment a few months ago. From my home office, I have a Win10 laptop that I joined to our domain with much difficulty (had to set the AD dns server on my local LAN) as compared to my Win7 desktop (never did anything special) but did manage to join and can logon as my domain self after I started VPN with a local account. Later, I could login just as my domain self w/o VPN running as I presumably used cached creds. Did not have this issue with Win7.
And my laptop OpenVPN networks initially were showing up as Public and I used PS set-netconnectionprofile to be Private (could not set DomainAuthenticated) but that was no help.
On the Win10 machine (as on the desktop) I have SecurePoint OpenVPN connected to all 3 of our AD sites just fine. I can ping 3 domain controllers, I can do an nslookup on _LDAP._TCP.DC._MSDCS.ad.mydomain.com and find all 3 of my DCs, I can ping all the domain machines with unqualified machine names, etc.
I seem to be able to do everything except -
I have to use my domain suffix when logging on (user@ad.mydomain.com not just user). Don't have to do this on my other machine.
gpupdate fails saying it cannot connect to a domain controller.
Any ideas why gpupdate fails? I see no useful info in the event logs, and my Win7 desktop using the same network runs fine in respect to domain access. I'm suspect of Win10 and/or the SecurePoint OpenVPN on Win10 yet most everything works just fine.
This "may" be related to the adapter binding order. I am unable to change the binding order of adapters in Win10 like I can in Win7 (see http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1) for the problem description.
active-directory domain-controller windows-10
asked Nov 7 '15 at 18:18
DaveDave
1144
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39
add a comment |
We converted to an AD environment a few months ago. From my home office, I have a Win10 laptop that I joined to our domain with much difficulty (had to set the AD dns server on my local LAN) as compared to my Win7 desktop (never did anything special) but did manage to join and can logon as my domain self after I started VPN with a local account. Later, I could login just as my domain self w/o VPN running as I presumably used cached creds. Did not have this issue with Win7.
And my laptop OpenVPN networks initially were showing up as Public and I used PS set-netconnectionprofile to be Private (could not set DomainAuthenticated) but that was no help.
On the Win10 machine (as on the desktop) I have SecurePoint OpenVPN connected to all 3 of our AD sites just fine. I can ping 3 domain controllers, I can do an nslookup on _LDAP._TCP.DC._MSDCS.ad.mydomain.com and find all 3 of my DCs, I can ping all the domain machines with unqualified machine names, etc.
I seem to be able to do everything except -
I have to use my domain suffix when logging on (user@ad.mydomain.com not just user). Don't have to do this on my other machine.
gpupdate fails saying it cannot connect to a domain controller.
Any ideas why gpupdate fails? I see no useful info in the event logs, and my Win7 desktop using the same network runs fine in respect to domain access. I'm suspect of Win10 and/or the SecurePoint OpenVPN on Win10 yet most everything works just fine.
This "may" be related to the adapter binding order. I am unable to change the binding order of adapters in Win10 like I can in Win7 (see http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1) for the problem description.
active-directory domain-controller windows-10
asked Nov 7 '15 at 18:18
DaveDave
1144
We converted to an AD environment a few months ago. From my home office, I have a Win10 laptop that I joined to our domain with much difficulty (had to set the AD dns server on my local LAN) as compared to my Win7 desktop (never did anything special) but did manage to join and can logon as my domain self after I started VPN with a local account. Later, I could login just as my domain self w/o VPN running as I presumably used cached creds. Did not have this issue with Win7.
And my laptop OpenVPN networks initially were showing up as Public and I used PS set-netconnectionprofile to be Private (could not set DomainAuthenticated) but that was no help.
On the Win10 machine (as on the desktop) I have SecurePoint OpenVPN connected to all 3 of our AD sites just fine. I can ping 3 domain controllers, I can do an nslookup on _LDAP._TCP.DC._MSDCS.ad.mydomain.com and find all 3 of my DCs, I can ping all the domain machines with unqualified machine names, etc.
I seem to be able to do everything except -
I have to use my domain suffix when logging on (user@ad.mydomain.com not just user). Don't have to do this on my other machine.
gpupdate fails saying it cannot connect to a domain controller.
Any ideas why gpupdate fails? I see no useful info in the event logs, and my Win7 desktop using the same network runs fine in respect to domain access. I'm suspect of Win10 and/or the SecurePoint OpenVPN on Win10 yet most everything works just fine.
This "may" be related to the adapter binding order. I am unable to change the binding order of adapters in Win10 like I can in Win7 (see http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1) for the problem description.
active-directory domain-controller windows-10
active-directory domain-controller windows-10
asked Nov 7 '15 at 18:18
DaveDave
1144
asked Nov 7 '15 at 18:18
DaveDave
1144
edited Nov 7 '15 at 19:39
Dave
asked Nov 7 '15 at 18:18
DaveDave
1144
asked Nov 7 '15 at 18:18
DaveDave
1144
asked Nov 7 '15 at 18:18
DaveDave
1144
1144
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39
add a comment |
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39
add a comment |
1 Answer
1
active
oldest
votes
This was an adapter binding order problem! Win10 changed this as compared to Win7. You could no longer set the binding order via Network Connections/Advanced/Advanced Settings/Adapters and Bindings.
You have to go into each and every adapter, IPv4 properties, Advanced, and turn off automatic metrics, and set a lower metric for adapters you want searched first. Didn't matter I had my DC as the preferred DNS server on my primary LAN.
Hope this helps someone because this caused me a LOT of grief trying to get a Win10 machine running on the domain via OpenVPN!
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1 has some more info.
answered Nov 7 '15 at 20:05
DaveDave
1144
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f734685%2fwin10-openvpn-domain-machine-cannot-find-a-domain-controller%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
This was an adapter binding order problem! Win10 changed this as compared to Win7. You could no longer set the binding order via Network Connections/Advanced/Advanced Settings/Adapters and Bindings.
You have to go into each and every adapter, IPv4 properties, Advanced, and turn off automatic metrics, and set a lower metric for adapters you want searched first. Didn't matter I had my DC as the preferred DNS server on my primary LAN.
Hope this helps someone because this caused me a LOT of grief trying to get a Win10 machine running on the domain via OpenVPN!
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1 has some more info.
answered Nov 7 '15 at 20:05
DaveDave
1144
add a comment |
This was an adapter binding order problem! Win10 changed this as compared to Win7. You could no longer set the binding order via Network Connections/Advanced/Advanced Settings/Adapters and Bindings.
You have to go into each and every adapter, IPv4 properties, Advanced, and turn off automatic metrics, and set a lower metric for adapters you want searched first. Didn't matter I had my DC as the preferred DNS server on my primary LAN.
Hope this helps someone because this caused me a LOT of grief trying to get a Win10 machine running on the domain via OpenVPN!
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1 has some more info.
answered Nov 7 '15 at 20:05
DaveDave
1144
add a comment |
This was an adapter binding order problem! Win10 changed this as compared to Win7. You could no longer set the binding order via Network Connections/Advanced/Advanced Settings/Adapters and Bindings.
You have to go into each and every adapter, IPv4 properties, Advanced, and turn off automatic metrics, and set a lower metric for adapters you want searched first. Didn't matter I had my DC as the preferred DNS server on my primary LAN.
Hope this helps someone because this caused me a LOT of grief trying to get a Win10 machine running on the domain via OpenVPN!
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1 has some more info.
answered Nov 7 '15 at 20:05
DaveDave
1144
This was an adapter binding order problem! Win10 changed this as compared to Win7. You could no longer set the binding order via Network Connections/Advanced/Advanced Settings/Adapters and Bindings.
You have to go into each and every adapter, IPv4 properties, Advanced, and turn off automatic metrics, and set a lower metric for adapters you want searched first. Didn't matter I had my DC as the preferred DNS server on my primary LAN.
Hope this helps someone because this caused me a LOT of grief trying to get a Win10 machine running on the domain via OpenVPN!
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306?auth=1 has some more info.
answered Nov 7 '15 at 20:05
DaveDave
1144
answered Nov 7 '15 at 20:05
DaveDave
1144
answered Nov 7 '15 at 20:05
DaveDave
1144
answered Nov 7 '15 at 20:05
DaveDave
1144
1144
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f734685%2fwin10-openvpn-domain-machine-cannot-find-a-domain-controller%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
Regarding Win7 vs Win10, AD has always required that the client be able to resolve the AD DNS names, both during AD join as well as any future AD-involved communications. Nothing changed in this regard with Windows 10.
– EEAA
Nov 7 '15 at 18:22
@EEAA - not really saying it did, just saying I did not have to add a dns address of my DC to my primary lan on win7 but did on win10. OpenVPN had the same dns servers per ipconfig /all on both machines.
– Dave
Nov 7 '15 at 18:32
To add Windows 7 to your domain, it would have had to be able to resolve AD DNS names somehow. There is no other way that it could have found your DC.
– EEAA
Nov 7 '15 at 18:35
Yes it would and it did. The dns addresses were associated with the OpenVPN adapters and presumably it found them that way. That was a couple months ago but in any event, the Win7 machine has no problems, and the Win10 machine does have the AD DC as the dns server for the main lan, and the openvpn networks and all works except gpupdate says it cannot make a DC connection. I can ping ad.mydomain.com just fine. Thx.
– Dave
Nov 7 '15 at 18:39