Windows 7 : SoftAP / Access Point Configuration

So I recently needed to share a 3G USB connection from a Windows 7 laptop with a variety of different devices; it turns out that this funcitonality is built-in to the OS and can be configured in a few simple steps. There are some GUI-type tools available to help you perform this operation should you want to simplify it…

Check for SoftAP Support

Execute the following command:
{code lang:ini showtitle:false lines:false hidden:false}netsh wlan show drivers{/code}

Look for “Hosted network supported  : Yes”, provided this is supported you’re good to go. If this is not supported make sure you are running the most recent version of the drivers for your wireless card, if you are then unfortunately there isn’t anything else you can do…

Configuring the SoftAP

Now, from an Administrative command prompt execute the following commands:
{code lang:ini showtitle:false lines:false hidden:false}netsh wlan set hostednetwork ssid=PRVNet key=MyPassword1 keyUsage=persistent{/code}

Configure your Internet Connection for Sharing

Modify your “internet connected” adapter so that sharing is enabled, you also need to select the correct home networking connection that you want to share the connection with – make sure you select the new Microsoft Virtual Wifi Miniport adapter.

Enabling the SoftAP

Use the following command to switch on the SoftAP:
{code lang:ini showtitle:false lines:false hidden:false}netsh wlan start hostednetwork{/code}

You should be able to connect to your new SoftAP now.

Disabling the SoftAP

To disable the SoftAP execute the command:
{code lang:ini showtitle:false lines:false hidden:false}netsh wlan stop hostednetwork{/code}

Windows : Reset WBEM Repository

Windows : Resolving WMI Connectivity Issues

VPN Clients

First check whetherCheckpoitn Secure Client is installed; the integrated Firewall within this VPN client can cause chaos with WMI. Ensure this is updgraded to version ‘VPN-1 SecureClient NGX R60 HFA03 with support for Windows 7 – CP_SecuRemoteSecureClient_NGX_R60_HFA3’.


Next try connecting to the amchine using wbemtest; from a command line on any Windows XP + system execute the command wbemtest, this will open a new window;

    1. Click Connect, then modiy the name space to be \\client_name\root\cimv2, then click connect.

Windows Firewall

If this fails confirm the following ports/settings are enabled in Windows Firewall (if configured):

    1. TCP Port 135
    2. Remote Administraton

You can always reset the Windows Firewall using the command netsh reset firewall

Reset WBEM Repository

To reset the WBEM repository follow the following instructions:

    1. Use the Start menu to right-click My Computer.
    2. Press the Manage item.
    3. Double-click Services and Applications in the left-hand pane.
    4. Press Services to expand it.
    5. Scroll to Windows Management Instrumentation in the right-hand pane and  right-click it.
    6. Press Stop.
    7. Use Windows Explorer to delete all the files in the %SystemRoot%\System32\Wbem\Repository folder.
    8. Shutdown and restart your computer. The Windows Management
    9. Instrumentation service will start and the files will be re-created

Verify Registry Settings

If WMI is still not working verify the following registry keys:


Windows 7 : Dial-in tab Missing

Windows 7 : Dial-in tab Missing

Copy the following files from a Windows Server 2008 R2 installation to a folder on your computer:


Execute the following commands to enable the functionality within dsa.msc:

copy mprsnap.dll C:\Windows\system32\
copy rasuser.dll C:\Windows\system32\
copy rtrfiltr.dll C:\Windows\system32\
copy mprsnap.dll.mui C:\Windows\system32\en-us\
copy rasuser.dll.mui C:\Windows\system32\en-us\
copy rtrfiltr.dll.mui C:\Windows\system32\en-us\
regsvr32.exe C:\Windows\system32\rasuser.dll

Windows : NetLogon Service Missing

Windows : NetLogon Service Missing

Encountered a machine today where the user was unable to connect to network printers. On further investiagtion users without cached credentials were unable to logon to the machine and received an error regarding the NetLogon service not running. After checking the netlogon service, it was infact missing!

To resolve this simply install ‘Client for Microsoft Networks’ from the LAN/Wireless network adapter configuration and reboot.

Windows 7: Mapped Drived Fail At Logon/Startup

Windows 7: Mapped Drived Fail At Logon/Startup

I cam across an issue recently where mapped drivers were not connecting at user logon. These drives were attached via the user account in AD (home drive) and via aVBS logon script.

This was resolved by setting the following registry key on the Windows 7 client:

Windows Registry Editor Version 5.00


Windows 2008 / 7: McAfee AV Auto Updates Fail

Windows 2008 R2 / 7: McAfee AV Auto Updates Fail

You may notice that automatic DAT updates, and patches fail to apply on Windows 7 and 2008 R2 systems. This is a known issue and is resolved using the process outlined in the following McAfee KB article:

By redefining the deployment task you add support for Winodws NT6.1 (Windows 7)

Windows : System Beep Ping [oy]

Windows : System Beep Ping [oy]


When resovling DNS addresses via ping you may receive a system beep and the following output:

Pinging [°ÿ] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

You are still able to ping via IP address.


This issue is caused by WinSock,to resolve, execute the following command and reboot:
netsh winsock reset