Netsetman wifi connection (by MAC) is foiled by Win 8.1

harijadig · 2019-02-01 02:54

I'm using netsetman ver.4.7.1. Non-commercial freeware version.
My OS is Win 8.1 x64.
The NSM Service is not activated.

I've been using a public wifi signal from my house to access the internet. But in the last few days, another wifi signal with the same nema (SSID) appeared (I detected it with a wifi scanner) and being stronger and closer, Win 8.1 disconnected me from the further one and connected me to this signal. However, the new signal is problematic and has very often connection drops than the old signal. Because Win 8.1 only shows the closest signal with the same name (SSID), I can't connect to the one I was using previously... until I found your app. It's very easy and helpful. I made a profile at netsetman to connect to the preferred wifi device by MAC address. It's working fine except for one thing: shortly after I activate my netsetman profile, Win 8.1 changed it to the problematic signal (which is stronger and closer). I activate my profile again, and Win 8.1 changed it again. It repeats endlessly.

Is there any way to stop Win 8.1 to keep insisting on changing my preferred wifi signal? Please help!

Last edited by harijadig (2019-02-01 04:54)

NetSetMan Support · 2019-02-01 12:03

Using the WiFi Management in NetSetMan or by creating a profile with the option "WiFi: Connect by MAC" allows you to connect to a specific access point, even if multiple access points share the same SSID (further details in the online help). However, after NetSetMan connects you to it, it’s up to Windows how to continue with this connection. If Windows decides to switch to a different AP, it’ll do so without asking NetSetMan.

What you could do is disabling the option “Connect when this network is in range” for the corresponding WiFi profile. You can do this in the previously mentioned WiFi Management dialog as well. This should prevent Windows from automatically connecting or reconnecting to that profile. On the downside, you'll always have to connect to that network manually. Unfortunately, Windows doesn't offer any other option.

Please let us know, if that solves your problem.

harijadig · 2019-02-01 15:55

I checked the wifi setting in win 8.1 for the corresponding SSID and saw the checkbox for "Connect automatically when this network is in range" is already uncheck / disabled (it's a default setting).
The same thing happened when I checked the wifi profile in netsetman for the corresponding SSID, the "Connect when this network is in range" is already disabled.

As a matter of fact, I did connect to the internet manually, so I don't mind to continue this habit if it can help me to resolve the problem. However you said this problem is more to windows than netsetman. So I can't say anymore.

Anyway, thank you for your response. I appreciated it greatly.

NetSetMan Support · 2019-02-01 16:57

In that case, you could try lowering the Roaming value for your wireless network adapter. Please be aware, that this will affect all wireless profiles alike.

Depending on the manufacturer of your NIC, this value is called "Roaming Aggressiveness" (Intel), "Roaming Sensitivity" (Realtek) or something similar.

Open Network Connections
Right-click the wireless NIC and choose Properties
Click Configure
Click the Advanced Tab
Select "Roaming Aggressiveness"

Change the default value (e.g. "Medium") to the lowest possible value ("Lowest" or "Disable") and confirm with OK.

Now connect to the desired access point and observe if your system now remains connected to it.

harijadig · 2019-02-01 23:30

I did your instructions. My network adapter is Realtek and I changed the value of "Roaming Sensitivity Value" to "disable". The choices are "high", "medium", "low", or "disable", while the default choice is "low".

After trying a few moments, it seems that Windows doesn't change my preferred access point (which has a weaker signal) with the access point that has a stronger signal anymore.

Thank you very much. This case can be closed now. I really appreciate your support.

Netsetman profile + disabling "Roaming Sensitivity Level" = Success!

NetSetMan Support

#1 2019-02-01 02:54

Netsetman wifi connection (by MAC) is foiled by Win 8.1

#2 2019-02-01 12:03

Re: Netsetman wifi connection (by MAC) is foiled by Win 8.1

#3 2019-02-01 15:55

Re: Netsetman wifi connection (by MAC) is foiled by Win 8.1

#4 2019-02-01 16:57

Re: Netsetman wifi connection (by MAC) is foiled by Win 8.1

#5 2019-02-01 23:30

Re: Netsetman wifi connection (by MAC) is foiled by Win 8.1