AD DNS servers across WAN

-

hi, have inherited network looks running 2 separate dns servers on each side of wan. both dcs of same domain.

issue 1 side of wan has trouble pinging dhcp clients on other side.

each side has own dhcp , dns, , looks neither dns setup secondary..

question best practice in situation? if setup site 2 secondary dns server, have same issues resolving dhcp clients?

thanks,

dekkar

if understand problem, having troubles ping clients on other site. if case can start following steps:

  • try ping client on other site using ip address. if successful while not case when ping using dns name there should problem dns resolution. check it, can use nslookup. if clients not getting registered need check dns servers accept dns dynamic registration , computers configured register dns records (if not can try temporary disable security software in use might blocking dns registration too)
  • if ip ping not successful problem should not related dns resolution. in case, need make sure icmp not blocked firewall (on computer or network level). tracert should let know on level icmp requests getting dropped.

this posting provided "as is" no warranties or guarantees , , confers no rights.

get active directory user last logon

create active directory test domain similar production one

management of test accounts in active directory production domain - part i

management of test accounts in active directory production domain - part ii

management of test accounts in active directory production domain - part iii

reset active directory user password



Windows Server  >  Directory Services



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 ...
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 ...
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 authenticati...
Read more