Well, sure, CIFS is actually completely separate from AD. AD is just kerberos + ldap and essentially only passes out tokens that the cifs client & server use to do the authentication phase. My understanding of the limited version of cifs is that most of the non-filerview functionality is there. Drop down to a console/ssh connection and give it a go, and I¹ll bet you¹ll be fine.
-Nick
On 2/20/08 6:15 AM, "Jimmy Corncrake" oisintno@gmail.com wrote:
Many thanks for your replies. I will look at the Windows Host for Unix as detailed at http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx
With regards registering a non CIFS licensed device in the AD the impression I had was that with CIFS 'lite' installed as part of the ISCSI or FC license this was possible. This is based partially on the solution below which seems to imply this when it states that "CIFS Setup can be run and the filer can be accessed through CIFS".
https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb31674
I can test this myself of course but if anyone knows for sure that a non-cifs filer can the registered into a AD it would be good to hear confirmation.
Jimmy
On 2/20/08, Milazzo Giacomo G.Milazzo@sinergy.it wrote:
Hi
To manage "root" volume from Windows you don't need a CIFS license.
/vol/vol0 is default shared as C$ also without a CIFS license and this permit you i.e. to unzip new Data Ontap releases, manage the /etc files accessing to the filer in workgroup mode and so on (no AD integration without a real CIFS license, if I well remember).
If you need the filers to let VMware servers put their data you can do it with the bundles iSCSI or the NFS (that you've licensed).
For iSCSI with VMware you don't need CIFS to attach to the LUN you will prepare or you don't need to share the volume that will contain those LUNs(think as opposite to SnapDrive from Windows hostsin this case you need also CIFS to "see" the volume/lun path to connect/create a disk).
With VMware the only thing you have to do is to create the LUNs and map them to an initiator group containing the iSCSI iqn names of the iSCSI storage adapters created on VMware ESX servers.
Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Jimmy Corncrake Inviato: mercoledì 20 febbraio 2008 11.22 A: toasters@mathworks.com Oggetto: Accessing a Filer Root Volume from Windows with only NFS Licensed
Hi,
we are in the process of deploying a number of Filers which will provide Storage for VMWARE. To date we have always run CIFS as our Storage has up until now served Windows client requests only. Our new Filers will be running with NFS licensed as opposed to CIFS. As I am a self confessed UNIX illiterate I will want to presist with managing these new Filers from my Windows Clients. I know that ISCSI. which will be licenced. will provide us with some CIFS features such as the ability to register the devices within AD and create CIFS shares which will be read-only. However we will still want to retain the ability to read-write the root volume and in generally manage these devices as we have done until now. I assume to achieve this I will need to install NFS Client software. Does anyone have an recommendations on such client software or any other observations that may be of use to us as we step beyond our familiar boundaries?
Jimmy C.