Managing DirectAccess clients in IPv4 only networks


we in process of implementing directaccess server 2012 r2. far, looks promising. clients can communicate our management servers desired. however, provide way our desk connect machines (for instance, able initiate remote control).

isatap technically no longer supported, seems there risks/challenges associated anyways. wondering if has come solutions this. since few, thinking configuring server allow inbound vpn ipv6 , have our desk users initiate vpn connect server few times functionality necessary. has done that? haven't set vpn in windows server in @ least 8 years, advice helpful. if have other suggestions, i'd happy accept that.

thanks!

i'm sorry follow own post quickly.

1. ipsec tunneling solve problem well? it's area have little experience in, seems possibility.

2. i've noticed while can ping clients server, can't else (rdp, access file shares, etc.) though firewall off (this testing after all). there limitations prevent me connecting client make impossible anyways?



Windows Server  >  Network Infrastructure Servers



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