F5F Stay Refreshed Power Users Networks Switching from Ethernet to Wi-Fi Eliminating the Ethernet cable in favor of Wi-Fi connectivity

Switching from Ethernet to Wi-Fi Eliminating the Ethernet cable in favor of Wi-Fi connectivity

Switching from Ethernet to Wi-Fi Eliminating the Ethernet cable in favor of Wi-Fi connectivity

E
ElaticsGone
Member
196
09-13-2016, 11:14 PM
#1
Has anyone heard about this? I put my system to sleep after a while, and when I turned it back on, it connected to my Wi-Fi instead of the Ethernet network. Probably a hidden setting that can be adjusted—likely in the Windows 10 settings.
E
ElaticsGone
09-13-2016, 11:14 PM #1

Has anyone heard about this? I put my system to sleep after a while, and when I turned it back on, it connected to my Wi-Fi instead of the Ethernet network. Probably a hidden setting that can be adjusted—likely in the Windows 10 settings.

B
Baby_Pigflame
Junior Member
12
09-14-2016, 01:06 AM
#2
WiFi wasn't activated. It's usually safer to keep it off when using a wired connection to prevent possible routing issues. (I haven't noticed this in Windows before, but I guess it ignores the WiFi if it sees the same network twice.)
B
Baby_Pigflame
09-14-2016, 01:06 AM #2

WiFi wasn't activated. It's usually safer to keep it off when using a wired connection to prevent possible routing issues. (I haven't noticed this in Windows before, but I guess it ignores the WiFi if it sees the same network twice.)

H
HipsterTiger
Junior Member
21
09-14-2016, 05:57 AM
#3
It seems you're considering testing something now that you've noticed a change. Despite never turning it off, this behavior just appeared suddenly. You've been busy with many adjustments, including port updates and server modifications, and you own an unRAID system that you've customized. It might be worth checking for any misconfigurations in Docker.
H
HipsterTiger
09-14-2016, 05:57 AM #3

It seems you're considering testing something now that you've noticed a change. Despite never turning it off, this behavior just appeared suddenly. You've been busy with many adjustments, including port updates and server modifications, and you own an unRAID system that you've customized. It might be worth checking for any misconfigurations in Docker.