Something that has been in my admin guides for sometime is that you can use Windows Shares (or NFS if you wish...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
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
- Type: nano -w /etc/fstab
- At the end of the file type://instructor3/sources /sources smbfs ip=192.168.2.200,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
- Save the File and Exit nano
- Create a mount point with:
- mkdir /sources
- Mount the SMB Share system with mount /sources
To 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