Direct Access on Hyper-V 2012 R2


hello

i'm running direct access on hyper-v 2012 r2. 

i have 2 servers running windows nlb.

2 processors, 8 gig of ram (they not being taxed hard)

2 nics behind nat firewall

my speed , latency on these things poor. i've seen go 65ms comparable native fortigate vpn , acceptable.  but i'm more seeing 275-800 ms , transfer speeds of 80kb/s. 2 clients.

i can't find "performance" best practices on internet other disabling other transition technologies that's client connect faster.

any 1 else have tuning guides or suggestions? thanks.

hi,

directaccess performance dependent on many factors such speed of directaccess client’s connection internet, internet latency , congestion between directaccess client , server, , current load on directaccess server.

to narrow down issue, please perform tests below:

  • please put client same subnet of directaccess server. if works, issue should caused internet or firewall.
  • please try shutdown vms on hyper-v server. try connect directaccess again. if works, please check if resource has been exhausted when vm on.

if issue persists, please check if following link helpful:

https://support.microsoft.com/en-us/kb/2883952

best regards.


steven lee please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.



Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

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

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

Azure MFA with Azure AD and RDS