Configure iSCSI SAN using FreeNAS 8.2

Connect an iSCSI SAN to Server 2008 R2 using the Microsoft iSCSI Initiator


You’ve installed FreeNAS 8.2 and configured it as a free iSCSI SAN. Now you need to connect to the iSCSI SAN using an iSCSI Initiator.


Note: This process is the same for both Server 2008 R2 and Win7 machines.

  1. Open the iSCSI Initiator control panel by running the iSCSICPL.exe command or navigating to Administrative Tools > iSCSI Initiator:
  2. The first time you run this, you’ll get this message. Click Yes:
  3. Enter the IP Address of your SAN into the Target field, then click Quick Connect:
  4. If you have enabled CHAP authentication on the SAN, you’ll get this Authentication Failure:
  5. On the Discovery Tab, click Discover Portal:
  6.  Enter the IP Address of your SAN into the IP Address or DNS name field, then click Advanced:
  7. Tick the Enable CHAP log on tickbox, then enter your CHAP credentials. Click OK twice:
  8. The available Targets will now be displayed on the Targets Tab. Click Connect:
  9.  Click Advanced:
  10. As before, tick the Enable CHAP log on tickbox, then enter your CHAP credentials. Click OK twice:
  11. The Target will now show as Connected:
  12. On the Volumes and Devices Tab, click Auto Configure to, erm, auto-configure that bad-boy!
  13. Navigate to Computer Management > Disk Management, and Initialise the new Disk that you just connected to:
  14. Now you can format the disk how you normally would:

  15. Job done:

Change computer names remotely using NETDOM on Windows XP

I got this familiar error message earlier when trying to change the computer name of a Windows XP machine:

“Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again”

To get around this, I used the following netdom command from my PC (replace capital words with your own):
netdom renamecomputer OLDCOMPUTERNAME /newname:NEWCOMPUTERNAME /userD:domain\administrator /passwordd:ADMINPASSWORD /usero: domain\administrator /passwordo: ADMINPASSWORD  /reboot:10
This renamed the computer and rebooted the little sucker in 10 seconds.

DCOM Error 10016

A client was getting DCOM error 10016 on Server 2003 with the following description:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Computer Services administrative tool.

I found that IIS WAMREG admin Service is the DCOM service in question by tracing the application ID. Notice it matches the ID in the error above.

To get to these properties you need to go through an MMC console like this through component services:

We know that it’s a permission error as Network Services is getting access denied to the application. Following this line of thought go to the security tab and hit customize on the launch and activation permissions:

Then hit edit:

Give Network Service full access:

Follow this procedure 2 more times to give network service full for both Access Permissions and Configuration Permissions. After giving Network Service the appropriate access the error went away.

%d bloggers like this: