Win8.1 Direct Access Client Stuck at "Connecting"


i'm experimenting direct access in lab setting 1 client , 3 2012 r2 servers. client running windows 8.1 enterprise.

the client able connect direct access server unable ping or connect 2 servers don't have ras installed. moreover, behavior migrates whichever server running remote access server: so, if remove role , install on server, client able communicate new server, not old.

the connection client server via ip-https (only option available me in environment). client able reliably determine when it's on internet versus intranet. however, when on internet, stays in "connecting" state , never connects, i'm still able access da server.

does have ideas on how resolve this?

hi steve -

thanks suggestion, managed resolve issue. did run troubleshooting tool previously, must confess lack of knowledge lot of ipv6 , networking terminology that's generated in log files - made difficult understand issue.

here's caused issue: mentioned, lab environment limited number of machines fulfilling multiple roles. in particular, da server backup domain controller running dns. in research, came across comment on http://directaccessguide.com mentioned da server runs dns64 support clients; made me suspicious regular dns server in way conflicting. and, in fact, before server made backup dc, da functioning fine. removing backup dc role resolved issue.

so takeaway this: don't run regular dns service on da server; if do, da client connectivity da server.




Windows Server  >  Windows Server 2012 Setup



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group