NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WMM2
Nov 21, 2020Aspirant
Set a default SSID for private wired connections
The NetGear R6230 Router allows one to define 4 separate SSID networks : 1) a private 2.4Ghz, 2) a private 5Ghz, 3) a guest 2.4Ghz, and 4) a guest 5Ghz. When connecting my laptop to the router via t...
WMM2
Nov 23, 2020Aspirant
- Whenever Windows sees a new network environment (such as a new
router), it creates a new "Network connection", and gives it a new name.
I agree that Windows is creating a new "Network connection" and gives it a new name. This seems to be happenig more than once. Today, I found that one of my ethernet connections is now named "Network 7."
I also know that I don't have any control, in Windows, over the naming convention of the wireless SSID's - that name is assigned within the router configuration. I defined MiWiFi, MiWiFi2, MeWiFi, and MeWiFi2 on the router and windows recognizes them when I turn-on WiFi connectivity. The puzzling part is the identification of a wired ethernet connection as a wireless SSID name, which is named "Ethernet" in the "Adapter Options" utility within the Windows Network and Internet Control Panel. MiWiFi2 is being assigned to my wired "Ethernet" connection as a "second name", in addition to the configurable name of "Ethernet." Notice that the WiFi connection also has a "second name" of MiWiFi2.
I certainly understand why Windows would provide the name of the SSID for the WiFi connection, but I don't understand the logic of providing that same name to the wired Ethernet connection.
schumaku
Nov 24, 2020Guru - Experienced User
WMM2 wrote:I also know that I don't have any control, in Windows, over the naming convention of the wireless SSID's - that name is assigned within the router configuration. I defined MiWiFi, MiWiFi2, MeWiFi, and MeWiFi2 on the router and windows recognizes them when I turn-on WiFi connectivity. The puzzling part is the identification of a wired ethernet connection as a wireless SSID name, which is named "Ethernet" in the "Adapter Options" utility within the Windows Network and Internet Control Panel. MiWiFi2 is being assigned to my wired "Ethernet" connection as a "second name", in addition to the configurable name of "Ethernet." Notice that the WiFi connection also has a "second name" of MiWiFi2.
I certainly understand why Windows would provide the name of the SSID for the WiFi connection, but I don't understand the logic of providing that same name to the wired Ethernet connection.
The configurable name is the network adapter name, not the network connection name.
The logic is that the Ethernet connection does currently connect to the same network (same LAN IP, same default gateway, same router MAC address, ...) - just like the MiWiFi2.
The mistake is not with you - the mistake is within Netgear (still burned in into the minds of some community members here) that they require you to configure multiple SSIDs for what is connecting to the very same network. Just spotted a new released Netgear simple wireless AP here (WAX204) which does not have this useless logic for dedicated names for each radio band. That's why you have two normal "MiWiFi" networks and two guest "MyWiFi" on air connecting to the very same network.