NetSetMan Support

mvscheven

Member

Registered: 2014-07-18

Posts: 4

Problem with static IP address

Hi,

I have been using NSM for a few weeks now, but still have
problems when switching from a WIFi profile back to my LAN profile with a static IP address.

Here is my work flow:
- Using my laptop with a WiFI profile and shutting it down while the profile is active
- Rebooting at work with Ethernet connected: NSM is not showing on the logon screen even though this option is activated.
- Logon to windows, wait for NSm to start and select the LAN profile
- Setting IP-address etc. yields no error, but connecting network drives fails

Checking the setting in the NSM popup (or Windows network connection details) shows first the correct IP address,
but after a few seconds it is changed to a wrong one.

Rebooting now solves all problem, i.e. NSM is shown on the logon screen and activating the LAN profile again
(to connect the network drives, network is working already) works fine.

I would love to get rid of the additional reboot.

Thanks a lot for any advice.

Regards
Malte

Windows 8.1 Pro, 64 bit
NSM 3.7.3
- using new IP activation method
- NSM service is active

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Problem with static IP address

Setting IP-address etc. yields no error, but connecting network drives fails
[...]
shows first the correct IP address,
but after a few seconds it is changed to a wrong one.

I'm actually not sure how this is possible. That would mean that it's either changed back or overruled by something. Do you have some other network/system settings related software installed? Maybe some vendor software that was already pre-installed?
Did you also check the activation log to see if there are some additional details reagarding the activation process that might not be visible in the main activation dialog? You're welcome to post the activation log (without any private information) here.

Rebooting at work with Ethernet connected: NSM is not showing on the logon screen even though this option is activated.
[...]
Rebooting now solves all problem, i.e. NSM is shown on the logon screen [...]

That doesn't make much sense to me, I'm afraid. The logon functionality does not depend on any available network settings. So there shouldn't be any difference between this reboot and when you're botting up at work. Do you see any difference between those reboots? Maybe in one case it's not a reboot but a hibernation or standby mode (not that it'd explain the reason for the problem but at least there would be a different situation)?
I understand this is not your main problem, but maybe it indicates the same source so finding an explaination for this problem might help solving the main problem.

Is it possible that at work you're joining a domain that requires you to already have the correct network settings when logging in?

- Rebooting at work

According to your description you're using the Non-Commercial Freeware version at work for several weeks already. Please keep in mind that this violates the license agreement. Use at work requires a NetSetMan Pro license.

mvscheven

Member

Registered: 2014-07-18

Posts: 4

Re: Problem with static IP address

Thanks for your reply. I am on a business trip this week and will try your suggestions next week.

According to your description you're using the Non-Commercial Freeware version at work for several weeks already. Please keep in mind that this violates the license agreement. Use at work requires a NetSetMan Pro license.

I know, and I am very sorry for extended the testing period for so long. I didn't find the find time so far to look into the described problems. I will certainly buy a license if NSM works fine for me, otherwise I will have to look for some alternative tool.

mvscheven

Member

Registered: 2014-07-18

Posts: 4

Re: Problem with static IP address

Maybe it is god to give a few more details about my configuration:

- I am using a ThinkPad Notebook and the LAN-Connection is at the USB Docking Station (only at work).
- I am using a Domain account, but can login without a network connection.
- I am not aware of any other network tools, Access Connections (Which I used before) is not available for Windows 8. But I have a Cisco vpn tool installed and virtual machine, both adding a few (virtual) network adapters.

This morning I tried the whole procedure and look into the details again. I am sure that I am always rebooting the machine.

After starting the notebook for the first time, in my work profile in NSM the dropdown  for the adapter is empty. I have to update the adapters to seen the correct USB LAN connection (Adapter 3). This should not be the problem, as updating the adapters manually does not help.

This is the activation log of the first try:
===================================
[0:00] Start: IBB (09:41:46)

[0:00] Start: Ethernet 3
[0:00] Adapter gefunden
[0:00] IP & Subnetzmaske: Start
[0:00] IP-Adresse: OK
[0:00] Subnetzmaske: OK
[0:00] Statisch: OK
[0:00] Gateway & Metrik: Start
[0:00] Gateway: OK
[0:00] Metrik: OK
[0:00] DNS: Start
[0:00] DNS: OK
[0:01] Warte: 5 sec
[0:06] Adapter - Aktualisieren: OK
[0:06] Drucker: Start
[0:06] Drucker (s): 0
[0:06] Drucker (u): 0
[0:06] Netzlaufwerk: Start
[0:06] Verbinde M: XXXX
[0:07] Fehlgeschlagen, Wiederholen (1/5)
[0:08] Fehlgeschlagen, Wiederholen (2/5)
[0:09] Fehlgeschlagen, Wiederholen (3/5)
[0:10] Fehlgeschlagen, Wiederholen (4/5)
[0:11] Fehlgeschlagen, Wiederholen (5/5)
[0:12] Verbinde M: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:12] Verbinde N: XXXX
[0:12] Fehlgeschlagen, Wiederholen (1/5)
[0:13] Fehlgeschlagen, Wiederholen (2/5)
[0:14] Fehlgeschlagen, Wiederholen (3/5)
[0:15] Fehlgeschlagen, Wiederholen (4/5)
[0:16] Fehlgeschlagen, Wiederholen (5/5)
[0:17] Verbinde N: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:17] Verbinde R: XXXX
[0:17] Fehlgeschlagen, Wiederholen (1/5)
[0:18] Fehlgeschlagen, Wiederholen (2/5)
[0:19] Fehlgeschlagen, Wiederholen (3/5)
[0:20] Fehlgeschlagen, Wiederholen (4/5)
[0:21] Fehlgeschlagen, Wiederholen (5/5)
[0:22] Verbinde R: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:22] Verbinde X: XXXX
[0:22] Fehlgeschlagen, Wiederholen (1/5)
[0:23] Fehlgeschlagen, Wiederholen (2/5)
[0:24] Fehlgeschlagen, Wiederholen (3/5)
[0:25] Fehlgeschlagen, Wiederholen (4/5)
[0:26] Fehlgeschlagen, Wiederholen (5/5)
[0:27] Verbinde X: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:27] Verbinde Z: XXXX
[0:27] Fehlgeschlagen, Wiederholen (1/5)
[0:28] Fehlgeschlagen, Wiederholen (2/5)
[0:29] Fehlgeschlagen, Wiederholen (3/5)
[0:30] Fehlgeschlagen, Wiederholen (4/5)
[0:31] Fehlgeschlagen, Wiederholen (5/5)
[0:32] Verbinde Z: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:32] Verbinde U: XXXX
[0:32] Fehlgeschlagen, Wiederholen (1/5)
[0:33] Fehlgeschlagen, Wiederholen (2/5)
[0:34] Fehlgeschlagen, Wiederholen (3/5)
[0:35] Fehlgeschlagen, Wiederholen (4/5)
[0:36] Fehlgeschlagen, Wiederholen (5/5)
[0:37] Verbinde U: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[0:37] Verbinde T: XXXX
[1:30] Fehlgeschlagen, Wiederholen (1/5)
[1:30] Fehlgeschlagen, Wiederholen (2/5)
[1:31] Fehlgeschlagen, Wiederholen (3/5)
[1:32] Fehlgeschlagen, Wiederholen (4/5)
[1:33] Fehlgeschlagen, Wiederholen (5/5)
[1:34] Verbinde T: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[1:34] Verbinde S: XXXX
[1:34] Fehlgeschlagen, Wiederholen (1/5)
[1:35] Fehlgeschlagen, Wiederholen (2/5)
[1:36] Fehlgeschlagen, Wiederholen (3/5)
[1:37] Fehlgeschlagen, Wiederholen (4/5)
[1:38] Fehlgeschlagen, Wiederholen (5/5)
[1:39] Verbinde S: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[1:39] Verbinde V: XXXX
[1:39] Fehlgeschlagen, Wiederholen (1/5)
[1:40] Fehlgeschlagen, Wiederholen (2/5)
[1:41] Fehlgeschlagen, Wiederholen (3/5)
[1:42] Fehlgeschlagen, Wiederholen (4/5)
[1:43] Fehlgeschlagen, Wiederholen (5/5)
[1:44] Verbinde V: Fehler 53
Der Netzwerkpfad wurde nicht gefunden
[1:44] Warte...
[1:45] Netzlaufwerk: Ende
[1:45] Adapter-Status: Start
[1:45] Adapter-Status: Neustarten
[1:46] Adapter-Status: OK
[1:46] Warte: 5 sec
[1:51] Adapter-Status: Ende

[1:51] Ende (09:43:37)
===================================

At the end of the activation, the IP address is wrong, Gateway, Subnet and DNS are correct. In the Windows Network Connection Details it says "DHCP active: No", but "automatically obtained IP address: XXX.XXX.XXX.XXX" giving the wrong IP-Address.

Repeating the activation does not change anything. The only solution I have so fare is to reboot. In this case the network settings are correct (including the IP address) and the network is active before I login. I just have to activated the NSM profile again to get the network drives.

In the Windows Network TCP/IP4 settings for the LAN adapter I kept the default, i.e. obtain IP address automatically.

mvscheven

Member

Registered: 2014-07-18

Posts: 4

Re: Problem with static IP address

I did some further testing and probably found the cause for my problems (but unfortunately no solution):

This is my setup:

- I always start with the notebook connected the the USB docking station and a fully working NSM work profile (Adapter 3).

Variant A:
- activate a NSM WiFi profile, OK
- undock the notebook, WiFi network is working fine, LAN disconnected
- reconnect docking station, LAN connection is working again, settings are still correct
- activate NSM work profile (LAN), settings remain correct

Variant B:
- activate a NSM WiFi profile, OK
- undock the notebook, WiFi network is working fine, LAN disconnected
- ** activate the same WiFi profile again, WiFi is still working **
- reconnect docking station, LAN connection is working again, settings are still correct
- activate NSM work profile (LAN), ** IP address is wrong **

So the cause is the missing LAN adapter while activating a profile.
Do you have a suggestion how to circumvent the problem?