NetSetMan uses the Windows WMI interface since version 2.0. If NetSetMan hangs with the message "Activating..." then this interface might be disabled or corrupted.

Please follow this step-by-step instruction:

1. Open the Services dialog (Start > Run > "services.msc")
2. Find Windows Management Instrumentation
3. Check if the Startup Type is set to Automatic and Status to Started.
4. If it's already running then the WMI Repository might be corrupted and should be recreated.
5. To do so first stop the service mentioned above (right-click > Stop)
6. Then create a backup of the repository folder and delete its content afterwards:
   %SystemRoot%\system32\wbem\Repository
7. The files are automatically recreated after a reboot.
8. After rebooting run NSM, click "Refresh" and choose an adapter.

If the WMI service isn't listed, you can reinstall it like this:

1. Insert your Windows CD.
2. Click Start > Run > Type:
   rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf
3. Reboot.

This can have lots of different causes. Therefore there are several possible solutions.
First of all you should take a look into the log which is available at a click on the "-" at the bottom of the Activating window. It might give you some useful information.

Each point is an individual solution approach so you don't have to perform all operations at once. In most cases even the first or the second point will solve the problem.

1. Make sure the status of the following services is Started and the startup type is set to Automatic.
   (Start > Run > "services.msc")
   DNS-Client
   DHCP-Client
   DCOM Server Process Launcher
   
   
2. Have a look at your Hosts file: %SystemRoot%\system32\drivers\etc\hosts
   It shouldn't be bigger than a few kb.
   If it is too big, clear it.
   
   You can open it with a text editor to view its content.
   It usually contais only the following line:
   127.0.0.1       localhost
   
   There are several programs which add up to several thousand lines in here to "protect you from advertisements or spyware". In fact blowing up the hosts file slows your system down. Just keep your Hosts file clean or at least don't add more than a few hundred entries.
   
   
3. Try to restart the DNS cache:
   net stop dnscache
   [enter]
   net start dnscache
   [enter]
   
   
4. If there's a bigger problem with your network you can use the tiny tool WinSock XP Fix 1.2. It fixes several common network problems with one click.
   
   
5. Re-/Install new drivers for your network adapter.

NetSetMan Pro has its own functions for adding a computer to a domain. Follow the short inctructions to make use of it. If you for some reason have problems joining a domain, you can use the alternate method described below.

1. Check the checkbox besides "/ Domain".
2. Enter your domain name in the top field. (e.g. "domain.local")
3. Enter your user name in the field below. (e.g. "Username")
4. Press [P] and enter the password for the user name from step 2.
   
   If you get an error message or you are not connected propperly to the domain then please do the following additional steps for the alternate method (available for NetSetMan Pro 2.3.4 and later):
5. Download this zip-file.
6. Extract its content to the program folder of NetSetMan Pro. It will automatically detect and use it instead of its own domain functions.

Using the domain feature might add a domain functional level information to the logon screen, so instead of "your.domain" you will see "your.domain (Windows 2000)". If you want to remove this information again (although it has no effect on the functionality) you need to delete the registry key "DCacheShowDomainTags" from [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon].

Important Note:

In NT domains a user can only be member of exactly one domain at the same time. This means that by joining another domain or a workgroup your membership in the previous domain is lost until your system is rejoined.

NetSetMan can only join you to a domain if your domain user account has the permission to do so.
This user account privilege is called "Add Workstation to Domain" and must be enabled on your account. If you don't have this privilege, please ask your network administrator do grant you that.

Since changing network settings is an administrative procedure, NetSetMan requires administrator privileges to work correctly. You have the following possibilities:

1. Normal: As long as you work with a Windows user account with administrator privileges, you don't have to do anything special. NetSetMan will work without any preparations.
   
   
2. Admin-Mode: As soon as you start NetSetMan with limited privileges, a dialog will appear pointing out the problem. You then have the possibility to enter a user name and a password of an account with administrator privileges which will be saved encrypted in the settings-file so NetSetMan can use them to start itself with the required privileges.
   
   
3. Service: Since version 2.5.0 you also can use the NSM Service as an alternative to the Admin-Mode. It is a special service that provides NetSetMan with the required privileges. To install the service you will need administrator privileges once. An uninstallation can be performed using the common software uninstallation dialog of Windows. You can control the service using the services dialog (services.msc) where you can stop or restart it.
   If you get the error "Invalid signature", make sure the program exe hasn't been modified and the group policy "Turn off Automatic Root Certificates Update" is deactivated.
   

Since Vista there's the special case where a user that is logged in as an administrator doesn't automatically work with administrator privileges. When NetSetMan is started it asks for elevated privileges and therefore causes an UAC (= User Account Control) notification which has to be confirmed, otherwise the above mentioned dialog will appear. To avoid UAC notifications you have the following possibilities:

1. Deactivate UAC: By deactivating UAC you'll have the same Windows behavior as you know it from previous Windows versions, i.e. without UAC prompts.
   Perform these steps: Click Start > Run > MSCONFIG.EXE > Tools > "Disable User Account Control"
   As an alternative you can exclude NetSetMan from UAC observations. That procedure is slightly complicated and is described here.
   
   
2. Service: Here as well NSM Service can be the solution. Install the service as described in the first section part 3 and NetSetMan won't ever cause an UAC notification again.
   
   
3. Run at Startup: If NetSetMan is started together with Windows and only this UAC notification shall be removed, the following workaround can do the trick. You then don't have to install the service.
   Start -> Enter "Task Scheduler" -> Choose "Create Task" from the right panel -> Under "Triggers" click "New..." and choose "At log on" -> Under "General" check "Run with highest privileges" -> Under "Actions" set the program path to NetSetMan and enter "-h" as the argument, so that NetSetMan is started minimized -> Deactivate the auto-start setting in NetSetMan
   An extended description of this procedure with screenshots can be found here.
   

What is IPv6?

The Internet Protocol (IP) as you currently know it has an address format like 192.168.0.1 and is officially called IPv4. Generally speaking that's what makes your local network and also the Internet work. After about 30 years of existence there are new requirements that only can be met by a new version of that protocol: IPv6. It covers everything we need today and a long time ahead. IPv6 is quite easy to recognize having a complete different syntax like fe80::21c:23ff:fe9c:efd3/64.

Do I need it?

If you never heard about it until now you don't need it for now. IPv6 will most likely get more popular around 2011/12. However, there are already use cases right now. If you're a pioneer in the IPv6 area you might want to use the IPv6 features that NetSetMan has to offer.

What IPv6 features does NetSetMan have?

You can assign manual address configurations in profiles as you are already used to with all the other settings. Additionally you can generate valid IPv6 addresses based on the selected IPv6 types.
More features are planned and will come step by step.

What do I need to use IPv6?

If you have Windows Vista or later, IPv6 is already a part of your operating system.

If you're using XP, you need to have SP1 (better SP2/SP3) installed. IPv6 is then installed in a deactivated form. If you really want to use it, you need to activate it by opening the command line (Win+R > cmd.exe) and typing:
netsh interface ipv6 install

If you change your mind at a later point, you can always deactivate it again by typing:
netsh interface ipv6 uninstall

If you have use for IPv6 management and have some comments for the IPv6 features in NetSetMan, please send an email with your thoughts!