Jump to content

Recommended Posts

Posted

Hi All,

 

When I first set up Direct Access several years ago, I hit a problem that meant I had to use the Legacy Network Adapter on the server. Not sure where I found out I had to do that, but it worked! I can now find no reference to this anywhere on the internet!

 

Our Direct Access has been performing very badly so I am now concerned that the 100mbps legacy adapter is a bottleneck but if I swap it out, Direct Access appears to break.

 

Can anyone who is running Direct Access on Hyper-V in a single NIC configuration confirm if they are using the Legacy or the Standard Network adpater.

 

Thank very much.

Posted

Standard adapter on gen2 vm’s for all our servers. It will bomb if the ssl cert has already been bound to an adapter and it then gets changed.

 

You should just be able to change the adapter and then run through the settings again and bind the ssl cert to the new adapter.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...