As promised an update from our supports team regarding the issue we have been investigating, happy to chat about it in more detail this afternoon but in essence they have found a config issue with the Automatic Metric configuration on the UC-Engine LAN Adapters which explains the issues we have been seeing.
This is set to automatic by default in Win10 and uses internal logic to give the ‘best performing’ Ethernet adapter priority. It seems in this instance the Direct Connect LAN port had by Win 10 reckoning better performance than the network side LAN port; hence it chooses Adapter 2 as its Primary port. Logins failing and it presenting the APIPA address to the world. Once this failed it would eventually fall back to the proper address and logins would work.
When set up in LAN connect mode, both have routable addresses so even if for reasons it chooses to put the Adapter2 LAN port as primary it will route just fine.
I can share a config set up if that is useful and tests can be performed with Direct Connect devices as well.
----------------------------------------------------------------------------------------------------------------------------
This is direct from the Crestron Support guys.
Symptom is very slow internet/outside connections.
Appears to be routing traffic to Direct connect dongle first.
Only appears to affect Static IP addresses on main LAN.
Cause is a bad Automatic Metric configuration.
Suggested fix:
- Click Start, Type : ncpa.cpl <press enter>
- Right click ’Properties’
(You will get 2 warning popups after pressing ok which can be ignored).
This will resolve the client’s issue with the slow network connection and sign into Teams issue.