neohelp wrote:
kevinz, thank you for the reply. This is on Windows Server not Windows 10, and the adaptor will be connected and working for days at a time until this issue hits, and then after a full restart will work for another several days in a row. Any thoughts on how to prevent this disconnect, or at least bring the adaptor back without doing a full restart?
I have tried restarting the service, but the adaptor still gets a 169.254 address afterwards instead of a 10.0 address, and if I disable the adaptor, when I reenabled it, it says "A network cable is unplugged".
Follow the advice, regardless of it being a Server. Windows 10 and Server 2016 share common code.