very longtime profile switching...

LeV · 2017-08-17 11:56

NSM 4.5.0 switched between profiles about 16 seconds.
Old versions (or with checked "WMI IP" setting) it takes about 1-2 seconds.
Is there any ways to solve it?

WBR, Alex.

NetSetMan Support · 2017-08-17 12:19

Please post the activation log. Without it we don't know what exactly is taking what time.
What "old versions" are you referring to exactly? Like 2.x old or 4.3.0 old?

LeV · 2017-08-17 12:40

As I remember it was 3.x version. I used NSM many years and update it frequently. But only at recent months I noticed on this delay.

The longest procedure is "waiting for network connection...".

with checked "WMI IP" setting:

######################################################################

[0:00] NetSetMan 4.5.0
[0:00] Начало: Принтер Xerox (14:37:55)

[0:00] Начало: Lan
[0:00] Найден сетевой адаптер
[0:00] IP & Шлюз: Начало
[0:00] IP: Начало
           192.168.192.3 : 255.255.255.0
[0:00] IP: OK
[0:00] Шлюз: Начало
           192.168.192.2
[0:00] Шлюз: OK
[0:00] LAN / Адаптер: Начало
[0:00] Протокол-переплеты: Начало
           9 предмет
[0:00] ms_msclient: 1, vmware_bridge: 0, inspect: 1, ms_pacer: 0, ms_server: 1, ms_tcpip6: 0, ms_tcpip: 1, ms_lltdio: 0, ms_rspndr: 0
[0:00] Протокол-переплеты: OK

[0:00] Завершение (14:37:56)

without "WMI IP" setting:

######################################################################

[0:00] NetSetMan 4.5.0
[0:00] Начало: роутер (14:38:11)

[0:00] Начало: Lan
[0:00] Найден сетевой адаптер
[0:00] IP: Начало
           DHCP
[0:00] IP: OK
[0:00] Шлюз: Начало
           DHCP
[0:00] Шлюз: OK
[0:00] DNS: Начало
           8.8.8.8
[0:00] DNS: OK
[0:00] LAN / Адаптер: Начало
[0:00] Протокол-переплеты: Начало
           9 предмет
[0:00] ms_msclient: 0, vmware_bridge: 1, inspect: 1, ms_pacer: 0, ms_server: 0, ms_tcpip6: 0, ms_tcpip: 1, ms_lltdio: 0, ms_rspndr: 0
[0:00] Протокол-переплеты: OK
[0:00] Адаптер - Обновить...
[0:00] Жду сетевого подключения...
[0:15] Адаптер - Обновить: OK

[0:15] Завершение (14:38:27)

NetSetMan Support · 2017-08-17 14:38

The actual IP change takes place in less than a second. Then a waiting period for the network adapter and the network to be ready. In the background NetSetMan waits for the IP to be received from the DHCP server. As soon as it's done, the network functionality is confirmed with a request to the default gateway. Then the profile activation ends. This usually takes only 2-5 seconds. If the network doesn't respond within 15 seconds, a timeout cancels the waiting and continues with the rest of the profile activation.

We've implemented this network check to make sure the IP change is complete, before the profile continues to change the other settings. Otherwise other settings (like mapping network drives etc.) might fail, because they need the network to be working.

In your case it seems that the network isn't ready or simply isn't connected, so the 15s timeout applies.

It doesn't make sense to compare this behavior to the WMI method. We do not support or continue developing this interface, because it has many bugs and inconsistencies. It finishes the IP change immediately, but sometimes with incomplete values for no reason and it doesn't propagate the change in the system, so multiple parts of Windows are not aware of the IP change and might behave unpredictably.

Waiting for the network is an important step to accomplish reliable results. However, we understand that this waiting period could be skipped if no other settings are changed afterwards. This change is already planned together with a couple of other improvements of the activation dialog.

LeV · 2017-08-17 15:21

Thank you for fast and detailed reply!

NetSetMan Support wrote:

In your case it seems that the network isn't ready or simply isn't connected, so the 15s timeout applies.

Network is ready. After set "WMI IP" option it is switching very fast, see logfile.
I will wait for "waiting period = xx" option smile

Also it seems that NSM Tools ==> console doesn't support unicode output.

NetSetMan Support · 2017-08-17 15:34

LeV wrote:

Network is ready. After set "WMI IP" option it is switching very fast, see logfile.

The WMI method does not have any network check at all. As we said, the WMI method is very old and does not receive any updates. The network check was implemented later.
Also please notice that in your WMI example you're setting a static IP (which doesn't need to wait for DHCP) but in the other example you're setting a DHCP address, that by definition requires a DHCP server to reply first before it can be used.

To see for yourself when your network is ready, you could open cmd.exe and run
ping /t 192.168.192.1
(or whatever the IP of your router or default gateway is).
This will start a continuous ping so you can see the network status during the whole process.
Then activate the DHCP profile and observe the running ping. How long does it take until it reaches the destination after the profile activation?

LeV wrote:

Also it seems that NSM Tools ==> console doesn't support unicode output.

Thant you for mentioning this. We'll check this.

LeV · 2017-08-17 15:59

NET1: DHCP
NET2: fixed IP

I tested switching from NET2 to NET1.
"WMI IP" is off: after switching, ping ok after ~5 sec. NSM still waiting about 10 sec.
"WMI IP" is on: NSM switched fast, and ping ok after ~1-2 sec.

Now will test switching from NET2 to NET1.
"WMI IP" is on: ping ok faster than NSM finish applying. NSM still waiting about ~1-2 sec.
"WMI IP" is off: ping ok after ~5 sec. NSM still waiting about 11 sec.

So it will be optimal 5 sec delay for me.
Waiting for customized timeout setting smile

NetSetMan Support

#1 2017-08-17 11:56

very longtime profile switching...

#2 2017-08-17 12:19

Re: very longtime profile switching...

#3 2017-08-17 12:40

Re: very longtime profile switching...

#4 2017-08-17 14:38

Re: very longtime profile switching...

#5 2017-08-17 15:21

Re: very longtime profile switching...

#6 2017-08-17 15:34

Re: very longtime profile switching...

#7 2017-08-17 15:59

Re: very longtime profile switching...