Unable to Join to Domain from Remote Site

-

i have 2 servers in remote ad site i'm unable join/dcpromo domain.  i'm able ping fqdn of domain (domain.com) , resolves pdc.  additionally, i'm able nslookup srv records in domain without issue.  dcdiag passes tests on both domain controllers in main site.  nothing appears not work in main site.

when attempting domain join, recieve login prompt, enter credentials domain presented following error:

"the following error occurred attempting join domain "domain.com": specified network name no longer available.

what's odd, doesn't matter credentials put in, valid or invalid, same error message.

history: server i'm attempting join domain used domain controller in remote site, stopped replicating domain information, disjoined domain re-join it.  that's now.  second server member server on domain, wasn't able dcpromo, thinking there issues domain trust relationship, disjoined domain , unable join domain.

i've opened critical support case microsoft, we're @ 13 hours no response, i'm reaching out forums.

hi,

regarding current issue, following articles may useful us.

joining computer domain on client vpn connection

http://msmvps.com/blogs/acefekay/archive/2012/01/18/joining-a-computer-to-a-domain-over-a-client-vpn-connection.aspx

how connect ad ds sites on internet?

http://www.networksteve.com/forum/topic.php/how_to_connect_ad_ds_sites_over_the_internet/?topicid=23216&posts=8

best regards,

andy qi

andy qi
technet community support



Windows Server  >  Windows Server General Forum



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more