The number after your network name in Windows represents an incremental count of how many times your computer has identified and connected to a network with the same name. This usually happens when the network profile is saved multiple times, possibly due to different configurations, changes in network hardware, or connecting to networks with the same name but different credentials or locations.
For example, if your network name is "AP-2A" and you see "AP-2A 10", it indicates that Windows has saved multiple profiles for your network named "AP-2A".
Why This Happens:
Duplicate Network Profiles: Every time Windows detects a network with the same name but different settings, it creates a new profile.
Changes in Network Configuration: Changes in your network settings, such as a different router or new security settings, might cause Windows to create a new profile.
Reconnecting After Network Issues: Sometimes after network troubleshooting or resetting your router, Windows may create a new profile.
Follow one of the methods in the tutorial below to remove duplicate WiFi profiles:
To delete multiple Ethernet network profiles in Windows 11, you can use several methods, including the Settings app and Command Prompt. Here are the steps for each method:
Using the Settings App
Open Settings :
Press Win + I to open the Settings app.
Navigate to Network & Internet :
Click on Network & internet on the left side.
Click on Advanced network settings on the right side.
Manage Network Profiles :
Under the "Network adapters" section, you can see the list of network profiles.
Click on the network profile you want to delete and select Forget .
Using Command Prompt
Open Command Prompt as Administrator :
Press Win + S , type cmd , right-click on Command Prompt, and select Run as administrator .
List Network Profiles :
Type the following command to list all network profiles:
netsh lan show profiles
Delete Network Profiles :
To delete a specific network profile, use the following command:
netsh lan delete profile name="ProfileName"
Replace "ProfileName" with the actual name of the network profile you want to delete.
You don't have to remove the zone, just move the IOT LAN out of the IoT Zone and into the Internal zone. There's no restrictions between devices on Internal (as indicated by the Allow All), so if that allows your laptop to connect, then there's some firewall rule between IOT and Internal that's preventing access.
If not, then perhaps some setting on that physical port is interfering.
Thanks very much for the reminder about just removing the network from the zone.
But oh wow...after removing the network from the zone, I was still blocked from accessing the hubs at their IP address, Home Assistant on my Pi, etc.
Realized I hadn't tried other browsers yesterday (my excuse for forgetting this key troubleshooting step was I have also been completing many To-Do's for my son's wedding on Friday, so things have been hectic). Tried Duck Duck Go and everything came up immediately. Cleared cache on Chrome browser for the last week and everything came up normally. Sheesh...never seen a cache problem quite like this, but that appears to have been the issue.
Going to leave things alone as much as possible until the wedding is over...don't need any more network tech issues on top of the WAF wedding stress.
Was totally unaware of this type of issue, thanks very much for the details. I'll be looking into this part of my network after the weekend when things are a little more settled at home. I've never run into anything like this before, but the fact I just changed my entire network setup I can see how this could have happened... Thanks again!
Keep in mind, this really is not an issue. If the current profile or profiles (ethernet and/or Wi-Fi) is/are working, there is nothing wrong. It is simply a matter of wanting to "clean up" anything that may be erroneous.
Totally understand. My nephew got married two weekends ago and my wife has been stressing about it for the past three months or so. Never returned so much to Amazon in one shot as I did a few weeks ago after the final decisions were made. I can't imagine the stress if we had kids and one of them was getting married. Good luck!
LOL...UPS was like, "Whoah!!" Congrats for your nephew.
It's definitely exciting around here...big day tomorrow and then my wife can go back to worrying about normal things. She loves to worry...
And...my ethernet problem seems resolved. I was poking around earlier today, looking at port setttings for switches between me and the router, other switches on other legs, and then went and tested connections from two other switches w/my laptop. Things worked fine.
Went back to my original switch and tried connecting again and it worked fine. So appears to work.
A bit mysterious why. I was looking at a LOT of switch port settings today (wife was out shopping last-minute so I had time) and there is a chance I did change something, but I think I just looked and didn't make any actual changes.
Thanks for clarifying that...I did (as noted above) connect successfully today using the same "10" profile so clearly the profile is not the problem. I'll likely just leave things be...
OMG...just realized I did change something significant in the last couple of days that could explain my changed results w/ethernet connection. I updated the Network app version 9.0.114 Official (from 9.0.108). Seems possible/probable that might explain my improved Ethernet results. Maybe something jiggled loose (or tightened up) as a result of the udpate. Feel a little better having some difference that might explain the change in my results. "Ghost" fixes are my least favorite.
Next project: Planning on getting my son to put a CGU & U6-LR into his new home (moving in soon after the wedding). U6-LR should be perfect for his place, which is around 1400 sqft, single story Craftsman. He's having an electrician over as soon as escrow closes to replace his panel, and I'm going to make sure he gets the electrician to run some cat6 into the attic so we can hang the U6-LR on the ceiling near the center of the house.
Are any of you monitoring/managing family sites in other locations? Any suggestions about what to do/what to avoid?
We have a small cottage at the beach in NJ, with a Unifi Dream Router. It has two POE ports powering cameras, and has plenty of capacity to support the devices we have up there (a UDM would be overkill).
I have a site -to-site VPN set up between there and our primary residence, using duckdns to keep track of the public IP addresses. It just works, and is one of those rare things that I never have to fiddle with. I can access anything on any network from either location, and there are firewall rules at both locations to keep the respective IOT networks in check. It's very easy to set up.
Yeah, the UDM is a great package...sold out for some time now, I believe. I would probably have started w/that for my son if it was still available, but the CGU and U6-LR AP will be a great setup for them.
Didn't think of the site-to-site VPN...that would work well I think.
I setup a VPN server at my parents house because I help maintain their HE hub and a few things. I just simply connect via my computer or phone and then have access to their network. Site to site is great but depending on your requirements it might be overkill vs connecting to VPN as you need it.
Just make sure you both have different subnets! I made that mistake in the past and put my parents on X.X.8.1 and my house on X.X.3.1
Yea.. I saw that yesterday and for a brief moment thought to install it. Then I decided to hold off for at least one or two more releases.
There are clearly some issues with it if you scan through the thread. It is already at 10 pages of posts. That said after a few revisions I will certainly try it as I really like some of the new stuff coming with it.
I've a little Unifi problem that someone more knowledgeable here may be able to solve. My previous setup was:
UDR > TP-Link unmanaged switch > U6 Lite AP's (via PoE adaptors). Due to the TP-Link switch, the topology always looked wrong with the two APs sometimes appearing to be the parent device of each other even though meshing is off and the units were hard wired.
Yesterday I added a USW-16-Lite to replace the TP-Link switch so that it's now:
UDR > USW-16-Lite > U6 Lite AP's
I did the work in this order:
power down TP link switch and remove all connections
power up USW-16 and connect the uplink to router
USW-16 adopted and updated successfully in Network
connected the two APs back to the USW-16 Lite (followed by all other devices)
It appeared to go OK. The APs and all devices are back online and everything is working. However....I'm left with Network showing "multiple devices offline" for the two access points and cannot seem to clear the error:
I've rebooted the UDR and restarted the APs but the error persists. I can only assume that it's because the UDR was the parent of the two APs when they were powered down but they were adopted by the switch when powered back up again (Network now correctly shows the USW-16 as the parent)
Does anyone have any ideas of how I can resolve this without trashing any configuration? TIA
If you click on the sideways cart next to the messsge saying multiple devices offline what does it say. I have seen occasions were that message is out of date and just informational of an event. Like today it is telling me of packet loss which happened a few hours ago and is not a current issue wait a day or two and see if it goes away.
Yeah it just brings up the logs showing the two devices going offline. The first was when I switched out a PoE adaptor on the morning and it did come straight back online afterward; the second is when I did the work replacing the switch. Everything is working OK. I wouldn't expect it to remove the log entry but also wouldn't expect the message on the dashboard to be persistent: