Automatic switch did not run

Fix84 · 2021-05-12 11:45

Hi to everyone.
NSM5.0.4 on W10pro 1909 fresh install (obsolete O.S. build for organization policies).
I've two profiles with that condition:
1) if ETH1 AND ETH2 are disconnected, enable dynamically WIFI
2) if ETH OR ETH2 are connected, disable dynamically WIFI
The first is INSTANTLY executed, the second only if the NSM interface will be opened (from the minimize).
Why did this happen?

Last edited by Fix84 (2021-05-12 11:49)

NetSetMan Support · 2021-05-12 11:59

Not sure why this happened in your case, but:
1. always update to the latest version and see if the problem is still present before posting a bug report.
2. in this specific case, please try out the soon to be released version 5.0.6, because we have adjusted multiple AutoSwitch parameters for it.
3. based on your description, you don't need to use AutoSwitch to achieve what you are trying to achieve. Simply use the WiFi/LAN option in the WiFi section, as described in this help file topic:
https://www.netsetman.com/help?hf=en#hf_wifimanagement
It is made exactly for turning the WiFi adapter on and off based on the LAN connection status.

Fix84 · 2021-05-12 12:26

Well... sorry for that. I've installed 5.0.5:
the same result about my scenario and, regarding the WiFi/LAN option in the WiFi section, didn't function at all (5.0.4 and 5.0.5): WiFi card rest enable when LAN is connected and not re-enable when LAN is disconnected (just for a check, I've disabled it manually).

Last edited by Fix84 (2021-05-12 12:27)

NetSetMan Support · 2021-05-21 16:08

Fix84 wrote:

WiFi card rest enable when LAN is connected and not re-enable when LAN is disconnected (just for a check, I've disabled it manually).

This is strage. The WiFi/LAN switch feature has currently no known issues. The only possibility we see would be that it is related to your constellation with 2 LAN adapters. This constellation is actually not part of our test process for this feature. We will need to verify this separately, but we do not have a device with 2 integrated LAN ports. We will need to test this with an a second USB LAN adapter, which might have a different result.

Notice, that the WiFi adapter status isn't changed immediately after dis/connecting a LAN cable, because Windows takes a moment to recognize the change before it broadcasts this information. You basically need to wait for the LAN icon in the notification area to change. That's the moment when NetSetMan is notified about the change and triffers the WiFi/LAN switcher.

For testing purposes, disable one LAN adapter, then try if it works now.

Fix84 · 2021-05-24 15:18

1 ETH is a LAN onboard and the other one is on the docking station. We have tried some different option on NSM to reach the goal that a user that returns from mobility (wifi) and plugging the docking station cable obtain automatically switch off (disable or disconnected) his wifi card. But, all the ways, failed.
The WiFi/LAN switch feature doesn't do anything, no action, no activities. The automatic rules work well when the LAN cable has been disconnected but near to never the opposite: the automation happen only when the mouse passes over the NSM onto the tray icon (some times) or when the NSM interface will be opened (100% effective result).
This issue is user independent, is happening with local user administrator, domain user administrator with local admin role and with standard domain user.

Fix84 · 2021-06-08 16:18

Another update:
5.0.5 tested on 10 machines (all Dell laptop, Latitude and XPS) with fresh Windows 10 PRO install (1909 and 20H2 build): the problem of the automatic LAN/WIFI switch persist. At 99% of the time, the "trigger" happens when the mouse goes over the NSM on the tray icon. Never switchback after LAN is been reconnected.
In our business network is active the IEEE 802.1x authentication... I don't know if could be an issue... but I suppose that the NSM "feel" the LAN network change using the EventID 15500 on Windows-Wired-AutoConfig... but in this case, something went wrong, because I tested a schedule operation fired on Event 15500 and is it infallible.

Still waiting for your support update for doing some troubleshooting.

Fix84 · 2021-07-09 10:45

Still waiting support...
all the company notebook (over 150 clients) will be migrated to the new 5.0.5 version and we need to fix this issue.

NetSetMan Support · 2021-07-15 12:02

We did some testing for your request, but we are unable to reproduce this issue. As previously mentioned, this is most likely related to the 2 LAN ports or (based on your recent additional information) it might be a special constellation with your docking station. Normally, when a LAN cable is connected, Windows populates a message with this information. NSM listens and reacts to that. This is extremely resource friendly, because it only does something when it needs to. The alternative would be constantly polling for the LAN status, causing constant CPU usage.

In your case, this message is apparently missing for whatever reason. Hovering over the icon or performing some action in the UI might manually poll general network information from the system which then triggers the event as well.
We don't know why this message is missing in your case. Maybe it is a special driver constellation, which removes and adds the LAN port with the docking station without populating its status. In all our tests and based of what we know from our customers (where using a LAN port in a docking station is a basic use case) this normally works without problems. You can verify this, by removing and attaching the Ethernet cable to the docking station while it remains connected, which should work without problems.

Of course there might be some solution even for your constellation, where we need to listen to additional Windows messages for docking station changes, but it would be an extremely time consuming activity to track this down just for your specific case. As much as we would like to cover each constellation, we currently cannot invest a lot of time in an individual problem, that does not exist for any other customers. We have added this issue to our tracker and we will get to it when we update the AutoSwitch functionality next time. Then we will try to find a solution for this as well.

Fix84 · 2021-07-15 16:39

Do you mean that NSM looks at the Windows notification center to "trigger" the network status and not from the Windows-Wired-AutoConfig registry event?
If is that, for GPO of the customer, the notification center is disabled.
But I can't understand why, if I take a look of NSM auto switch section, where I can view if and when it fire, sometimes it's run in minutes and others never run?

NetSetMan Support · 2021-07-16 07:29

This has nothing to do with the notification center. OS and applications are communicating through so called Windows messages with each other. For specific events, Windows is sending out broadcast messages and applications can listen to them. In this case it is a message telling that a LAN connection has been established. This message is sent in the exact moment, when the Windows network icon changes from disconnected to connected. Depending on your system, drivers and network, this can take a couple of seconds. You can test this by dis/connecting the Ethernet cable instead of the docking station.

Fix84 · 2021-07-16 10:37

I repeat that I've just tested manually, following the official DELL article:
https://www.dell.com/support/kbdoc/it-i … ed?lang=en
and it is instantly: when the LAN cable is been connected or disconnected, the events happen without any delays (also with docking station). I can't really understand why NSM report this issue and even more, why sometimes it runs with constant time (like a cadency of 59-60 seconds) and other time, never.
P.S...
Just to know... there is any way to "call" the refresh check of the "auto switch button" via cmd?

NetSetMan Support · 2021-07-16 11:44

Fix84 wrote:

I repeat that I've just tested manually, following the official DELL article:
https://www.dell.com/support/kbdoc/it-i … ed?lang=en

Our suggestion to test our WiFi/LAN switcher feature manually has nothing to do with this linked article or the Wired Autoconfig service. We do not use this service. It is not a suitable solution, because this service is not active by default. We do not enable or disable any Windows services at all.

As a side note, if you start mixing up different solutions (e.g. by enabling this service) then testing becomes even more difficult.

Instead, we suggested to test our integrated feature directly with an Ethernet cable just to see that it works under normal conditions. Leave your docking station away for this test, then test by dis/connecting your Ethernet cable to the laptop directly. Maybe we are missing something, be cannot find any indication in your messages, that you have already tested this. This is not meant to be a solution for your problem, but simply a test to see that this feature normally works correctly.

Fix84 wrote:

why sometimes it runs with constant time (like a cadency of 59-60 seconds) and other time, never.

We do not use any constant timer for this feature. As described, we react based on Windows messages and the Windows NLM interface. If they are sent after exactly 60 seconds for some reason, then that's when you see a result in our software.
The WiFi/LAN switcher has been implemented about 5 years ago in our software. We know that this feature is being heavily used. There should have been more reports about problems with it, if there was a general problem with it.

Fix84 wrote:

Just to know... there is any way to "call" the refresh check of the "auto switch button" via cmd?

No, sorry.

NetSetMan Support · 2021-07-16 12:26

We just noticed that based on your message from 2021-06-08 you seem to be testing with version 5.0.5, although version 5.0.6 has been released on 2021-05-31 with multiple AutoSwitch compatibility and performance improvements. There is no change specifically for this issue, but general improvements might of course also make a big difference. Make sure to always use the latest version for testing.

Fix84 · 2021-07-16 14:17

Our suggestion to test our WiFi/LAN switcher feature manually has nothing to do with this linked article or the Wired Autoconfig service. We do not use this service. It is not a suitable solution, because this service is not active by default. We do not enable or disable any Windows services at all.

I can't know what's your "listing method" but this is the only officially support from Dell to reach the goal and use to test the "link" on LAN interface.

Instead, we suggested to test our integrated feature directly with an Ethernet cable just to see that it works under normal conditions. Leave your docking station away for this test, then test by dis/connecting your Ethernet cable to the laptop directly.

Sorry for the misunderstanding... but I need to clarify: I'm not in a situation where starting from a working NSM on a factory machine, it falls to a malfunction for some customization or something else... merely, I've never viewed it running as described. I've used W10 pro 1909, 20H1, on several different models and series DELL laptops, all fresh install with OEM drivers, no antivirus, no third-party software... same result.

We just noticed that based on your message from 2021-06-08 you seem to be testing with version 5.0.5, although version 5.0.6 has been released on 2021-05-31

I've missed indicating that I've just used the 5.0.6 instead of the 5.0.5: nothing is changed.

No, sorry.

It is possible to activate some extra logs (I've just tried all the log options available from UI) to do some troubleshooting?

NetSetMan Support

#1 2021-05-12 11:45

Automatic switch did not run

#2 2021-05-12 11:59

Re: Automatic switch did not run

#3 2021-05-12 12:26

Re: Automatic switch did not run

#4 2021-05-21 16:08

Re: Automatic switch did not run

#5 2021-05-24 15:18

Re: Automatic switch did not run

#6 2021-06-08 16:18

Re: Automatic switch did not run

#7 2021-07-09 10:45

Re: Automatic switch did not run

#8 2021-07-15 12:02

Re: Automatic switch did not run

#9 2021-07-15 16:39

Re: Automatic switch did not run

#10 2021-07-16 07:29

Re: Automatic switch did not run

#11 2021-07-16 10:37

Re: Automatic switch did not run

#12 2021-07-16 11:44

Re: Automatic switch did not run

#13 2021-07-16 12:26

Re: Automatic switch did not run

#14 2021-07-16 14:17

Re: Automatic switch did not run