Accessing Windows Shares from the service console

Something that has been in my admin guides for sometime is that you can use Windows Shares (or NFS if you wish in Linux) to hold ISOs/Scripts and possibly Virtual Disk templates. Previously, it was based around using Microsoft Windows 2000. With the rise of Windows 2003, it’s worth noting that security settings within Windows 2003 would stop this from working. Here’s how you would set-up Windows Share access from the Service Console

Share a folder on Windows Machine

What I did was share out the D:\Data\Work\VMware\MyFiles directory on my Windows XP Home which I run on my laptop as MyFiles

  1. Type: nano -w /etc/fstab
  2. At the end of the file type://instructor3/sources /sources smbfs ip=,username=guest,password=guest,noauto 0 0Note:
    //Instructor3/Sources is the name of my server and the source is the folder I shared. /sources will be the name of our mounting point. Smbfs tells the system to use the SMB protocol. IP is my ip address on my network. I used the administrator account to gain access. Noauto means no automatic mount of the mounting point, and 0 0 means do not do a file system check or memory dump/cache
  3. Save the File and Exit nano
  4. Create a mount point with:
  5. mkdir /sources
  6. Mount the SMB Share system with mount /sources


    Requires Free Membership to View

  1. see the files use cd /sources and ls -l to list them  


    The definition of this mount point should survive reboots but you will have to use mount /sources at the Service Console to view the files themselves.

    If you are using Windows 2003 you might find you get this error

    This is caused by the introduction of the “security signing” of SMB packets as a default (this was optional in Windows 2000). The Service Console implementation of SAMBA does not support this. The only solution is to lower the security of the file server to which you are trying to connect to. Using the Windows Policy system (make sure you use the right one! There are many!)

    Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ Security Options

    Locate the policy called “Microsoft network server: Digitally sign communications (always)”

    Choose © Disabled

    This is outlined in the MS KB Article 823659


This was first published in December 2005

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.