I have been trying to eliminate my colored ship disconnects thinking it was Frontier's servers, which may be the case for some of you no doubt.
In any event, I don't know if this information would be useful to some others with colored ship disconnects, but what I found Windows 10 doing to networking really surprised me.
On a different front and for security reasons, I have most of Hyper-V turned on, in the bios and on Windows 10. I use the sandbox as well as Virtual Machines.
Now, Hyper-V has a virtual network adapter which uses IP's in the 172 range for some unknown reason known only to Microsoft, Hyper-V creates multiple virtual network adapters which can be seen in Control Panel/Device Manager under Network Adapters and Hyper-V creates these on the fly, as I have yet to discover what sets it off.
In any event, I have a DHCP Router with assigned IP addresses in the 192 range, and watching my network connection in a gadget, I see it, all by itself, change network adapters to a Hper-V network adapter. My system is still fully functional on LAN and WAN, but if I load up Elite when one of these Hyper-V virtual network adapters has become primary or is active, Elite will fail to connect to Frontier servers. I can see the Hyper-V Adapter and network IP in Elite's Network Settings.
Here is a link to explain this issue for Windows 10 Hyper-V Network Adapter Spawning.
So, in Device Manager under Network Adapters, if you see this:
You have spawning Hyper-V Network Adapters which may be taking over your network connection in the background without you realizing it.
The only way to temporarily solve this is to "uninstall" the "Hyper V Virtual Ethernet Adapters" with #n in the list above. This will not solve the problem long term, as in Microsoft's infinite wisdom, you must uninstall Hyper-V in "Programs and Features" before the adapter will stop spawning, which I am not going to do.
I just make sure I am using the adapter with my IP range before loading Elite.
So, if anyone has a solution which will stop the "Hyper-V Virtual Ethernet Adapter #n's" from spawning, but leave the primary "Hyper-V Virtual Ethernet Adapter" for use by Windows and VM, I would (and so would the world), appreciate a solution.
This happens in the background on Windows 10 with Hyper-V enabled, and unless your watching your network adapters or IP's, I doubt anyone would notice. My only clue was Elite's disconnects and when I look at Elite's network settings, it's using the wrong adapter and has the wrong address range.
This is Windows 10 being stupid as I'm sure Microsoft has a reason for it, but making sure I'm on the right network adapter has brought my colored ship disconnects to a stop.
Maybe it will help someone else. I just thought I would mention it here.
In any event, I don't know if this information would be useful to some others with colored ship disconnects, but what I found Windows 10 doing to networking really surprised me.
On a different front and for security reasons, I have most of Hyper-V turned on, in the bios and on Windows 10. I use the sandbox as well as Virtual Machines.
Now, Hyper-V has a virtual network adapter which uses IP's in the 172 range for some unknown reason known only to Microsoft, Hyper-V creates multiple virtual network adapters which can be seen in Control Panel/Device Manager under Network Adapters and Hyper-V creates these on the fly, as I have yet to discover what sets it off.
In any event, I have a DHCP Router with assigned IP addresses in the 192 range, and watching my network connection in a gadget, I see it, all by itself, change network adapters to a Hper-V network adapter. My system is still fully functional on LAN and WAN, but if I load up Elite when one of these Hyper-V virtual network adapters has become primary or is active, Elite will fail to connect to Frontier servers. I can see the Hyper-V Adapter and network IP in Elite's Network Settings.
Here is a link to explain this issue for Windows 10 Hyper-V Network Adapter Spawning.
Multiple Hyper-V Virtual Ethernet Adapters keep spawning in the Device Manager
Hello, I have a Windows 10 Pro (2004) freshly installed and these adapters keep spawning in the Device Manager. I don't even know what they are for. I deleted them ("Uninstall the device" function),
answers.microsoft.com
So, in Device Manager under Network Adapters, if you see this:
You have spawning Hyper-V Network Adapters which may be taking over your network connection in the background without you realizing it.
The only way to temporarily solve this is to "uninstall" the "Hyper V Virtual Ethernet Adapters" with #n in the list above. This will not solve the problem long term, as in Microsoft's infinite wisdom, you must uninstall Hyper-V in "Programs and Features" before the adapter will stop spawning, which I am not going to do.
I just make sure I am using the adapter with my IP range before loading Elite.
So, if anyone has a solution which will stop the "Hyper-V Virtual Ethernet Adapter #n's" from spawning, but leave the primary "Hyper-V Virtual Ethernet Adapter" for use by Windows and VM, I would (and so would the world), appreciate a solution.
This happens in the background on Windows 10 with Hyper-V enabled, and unless your watching your network adapters or IP's, I doubt anyone would notice. My only clue was Elite's disconnects and when I look at Elite's network settings, it's using the wrong adapter and has the wrong address range.
This is Windows 10 being stupid as I'm sure Microsoft has a reason for it, but making sure I'm on the right network adapter has brought my colored ship disconnects to a stop.
Maybe it will help someone else. I just thought I would mention it here.
