No connection with 3.4.2

Brent Kindsvater · 2012-04-23 21:47

I have a few XP running machines that do not run after the 3.4.2 upgrade.
When set to obtain ip automatically is shows the local area connection as Connected.
When trying to connect it says the local device name is already in use.
Tried with WMI ip got code (84)
Uninstall NetSetMan can set so all works
Reinstall NetsetMan unable to connect again

Please help with the settings, worked fine before upgrade.

NetSetMan Support · 2012-04-24 00:04

To make it clear: installing / uninstalling NetSetMan doesn't change anything on your system. If it seemed like it does, it's purely by coincidence.

Steps to get the "old" IP method back:
- In NetSetMan go to preferences and activate the old WMI IP method.
- In Windows go to your network adapters. Deactivate and activate again your network adapter.
- Restart your computer.

NetSetMan will now work again as it did before. I'm working on a solution for the problems that some users have with the new method.

Brent Kindsvater · 2012-04-24 14:08

No uninstalling NSM allows me to reactivate the network adapter.
When NSM is installed I cannot.
It does not just start working because I uninstall.

Brent Kindsvater · 2012-04-24 14:46

Installed Version 3.3.0 and all works as it did before.
I did not see a place to download previous versions, is there one?

NetSetMan Support · 2012-04-24 17:37

Brent Kindsvater wrote:

No uninstalling NSM allows me to reactivate the network adapter.
When NSM is installed I cannot.

Again: Installing/uninstalling NetSetMan from your system doesn't change anything besides removing the files from the installation folder. You can take that for granted.

I can imagine the reason for your assumption: It's possible that when you activate a profile with the described problem the activation process of NetSetMan crashes and remains active in the background or at least locks the status of your NIC. So when you try to change the status it doesn't work. So besides uninstalling you can simply also restart your computer (or manually kill the process in the task manager).

Instead of using version 3.3.0 you can activate the old IP method in the preferences as described. It will work exactly the same.

davleema · 2012-05-07 16:10

Same problem here: since 3.4.1, we have problems using DHCP on WinXP SP3 machines. When I activate the DHCP profile (everything auto), it seems to work, but the nic is not configured afterwards.

When I try to repair the interface (windows repair), it says it cannot do so because TCP/IP is not configured on the nic ? Afterwards, Netsetman doesn't see the interface any longer (refresh interfaces) .

After a reboot, the nic is there, Windows says it is connected, but the nic does not get a dhcp lease and is useless, and Netsetman does not see the nic. Using the old IP activation method does not work. Repairing the interface does not work again. Seems like the TCP/IP stack is foobar ?

Solution:
- remove NetSetman 3.4.1
- go to Device manager: uninstall nic -> scan for hardware changes -> Windows reinstalls the nic (Intel Gigabit)
- install NetSetman 3.3.0
- everything OK again

Last edited by davleema (2012-05-07 16:11)

NetSetMan Support · 2012-05-07 16:34

A couple of people are having this problem and I'm currently trying to find out the reason for this.

Can you please give some more information about your system? Do you have some "special" network drivers, tools (like Open VPN) or configurations installed?

davleema wrote:

Solution:
- remove NetSetman 3.4.1
- go to Device manager: uninstall nic -> scan for hardware changes -> Windows reinstalls the nic (Intel Gigabit)
- install NetSetman 3.3.0
- everything OK again

Your main point (re-installing the NIC) is a correct solution. However, it's not necessary to use the old version of NetSetMan! If you change to the old IP method in the preferences you'll get exactly the same behaviour as in version 3.3.0.

davleema · 2012-05-07 17:06

Ilja Herlein wrote:

A couple of people are having this problem and I'm currently trying to find out the reason for this.
Can you please give some more information about your system? Do you have some "special" network drivers, tools (like Open VPN) or configurations installed?

Afaict, nothing special: Dell Latitude E6520 laptops with Intel Gigabit adapters (82579LM). No VPN tools or "special" network stuff are installed. OS is plain WinXP Prof SP3. I have not yet tested on Win7.

Your main point (re-installing the NIC) is a correct solution. However, it's not necessary to use the old version of NetSetMan! If you change to the old IP method in the preferences you'll get exactly the same behaviour as in version 3.3.0.

I will try with the latest version (3.4.3 ?).
3.3.0 was our "last known good" version smile

davleema · 2012-05-09 12:57

Ilja Herlein wrote:

Your main point (re-installing the NIC) is a correct solution. However, it's not necessary to use the old version of NetSetMan! If you change to the old IP method in the preferences you'll get exactly the same behaviour as in version 3.3.0.

Tried 3.4.3 with old IP method today on a WinXP machine, seems to be OK.

Two Point · 2012-05-14 11:32

I am sorry to say so, this morning it happens to me. A fresh start from the laptop (Asus F3M with NVidia ethernet & Atheros AR 5006EG WLan). Downloading the mail (outlook 2003) and there was no connection possible.

It seems (i can be wrong) that the init of the cards is later then last week. The wifi-led turns on after AVG , NSM etc. Probably is this an effect of the latest mickey-sof cool update.

After the tips here in this thread, everything works. Thanks.

NetSetMan Support · 2012-05-18 00:28

Please try the new version 3.4.4 - The problem should be solved there.

NetSetMan Support

#1 2012-04-23 21:47

No connection with 3.4.2

#2 2012-04-24 00:04

Re: No connection with 3.4.2

#3 2012-04-24 14:08

Re: No connection with 3.4.2

#4 2012-04-24 14:46

Re: No connection with 3.4.2

#5 2012-04-24 17:37

Re: No connection with 3.4.2

#6 2012-05-07 16:10

Re: No connection with 3.4.2

#7 2012-05-07 16:34

Re: No connection with 3.4.2

#8 2012-05-07 17:06

Re: No connection with 3.4.2

#9 2012-05-09 12:57

Re: No connection with 3.4.2

#10 2012-05-14 11:32

Re: No connection with 3.4.2

#11 2012-05-18 00:28

Re: No connection with 3.4.2