If I understand your question right, you need to export the NFS filesystem via CIFS as well. CIFS is seperately licensed. If you don't have it already, you need to pay $$$. You need to spend some time on usermapping if you have tricky NFS and CIFS permission requirements.
This is a filesystem mounted to windows box via NFS. He wants to be able to access the nfsmount with a UNC path (\\ \nas-filesystem ) rather than by z:nas-filesystem.
I would also suggest you the same as Uwe Kerner did, to access the nfs through the UNC path the best way would be to share it through the CIFS rather then mouting it as nfs and then sharing it through SAMBA.
1) you mentioned this file system will be accessed by Windows only - then why you have created NFS export of the file system not a CIFS share?
2) The user is trying to access the NAS Data on a windows box - so why to use NFS protocol (which is for UNIX hosts) and not CIFS?
3) IHere NFS export is configured on the NAS - then you must be using some NFS service (may be Unix service on windows) on the windows server to convert the NFS protocol to windows - means you are unnecessarily imposing complexities and overheads.
If this file system on the NAS is to be used by windows users only - please create a CIFS share (Native Windows protocol) and access the CIFS share via the UNC (\\CIFS_server\Share) on the windows host. Yes, you need to have a CIFS server configured on the NAS and joined to the Domain (or a standalone CIFS depending on your environment).
NFS protocol is for UNIX access and unless you need any UNIX host accessing this data, there is no need to create NFS export. Please note that the data resides on the file system which is the same here - it only matters how you are going to access the data on the network - using CIFS (windows) or NFS (Unix) or both.
You can also have multi-protocol access - means both NFS and CIFS access to the same file system - it will be little complicated from Access permission and User mapping perspective. But I understand this is not your case as you mentioned you only need Windows hosts to access the file system.
Anyway - if you have not gone through these docs - you may consider to read them on Powerlink or on Documentation CD -
1) configuring CIFS
2) Configuring NFS
3) Managing Celerra for a Multiprotocol Environment
You also may find some older posts on this forum regarding CIFS, NFS and multi-protocol access - some of them are -
Uwe-Ud0Mk
37 Posts
0
May 25th, 2010 13:00
If I understand your question right, you need to export the NFS filesystem via CIFS as well. CIFS is seperately licensed. If you don't have it already, you need to pay $$$. You need to spend some time on usermapping if you have tricky NFS and CIFS permission requirements.
ra298
1 Rookie
•
18 Posts
0
May 25th, 2010 13:00
This is a filesystem mounted to windows box via NFS. He wants to be able to access the nfsmount with a UNC path (\\ \nas-filesystem ) rather than by z:nas-filesystem.
Thanks
Uwe-Ud0Mk
37 Posts
0
May 25th, 2010 14:00
Thank you for the clarification.
Option #1: I still think the best way to access NFS resources via UNC is to share them out on the Celerra via CIFS.
Option #2: Mount the NFS filesystem on a third host with SAMBA installed. Share out the NFS mount from the SAMBA host.
On your host:
mount nas:/nasfilesystem /mountpoint or
net use \\sambaserver\share
I would recommend you do option #1.
SAMEERK1
296 Posts
0
May 26th, 2010 02:00
Hi,
I would also suggest you the same as Uwe Kerner did, to access the nfs through the UNC path the best way would be to share it through the CIFS rather then mouting it as nfs and then sharing it through SAMBA.
Sameer
nandas
4 Operator
•
1.5K Posts
0
May 26th, 2010 08:00
Hi "rha",
Welcome to the EMC Support Forums.
I have some comments on your post and query -
1) you mentioned this file system will be accessed by Windows only - then why you have created NFS export of the file system not a CIFS share?
2) The user is trying to access the NAS Data on a windows box - so why to use NFS protocol (which is for UNIX hosts) and not CIFS?
3) IHere NFS export is configured on the NAS - then you must be using some NFS service (may be Unix service on windows) on the windows server to convert the NFS protocol to windows - means you are unnecessarily imposing complexities and overheads.
If this file system on the NAS is to be used by windows users only - please create a CIFS share (Native Windows protocol) and access the CIFS share via the UNC (\\CIFS_server\Share) on the windows host. Yes, you need to have a CIFS server configured on the NAS and joined to the Domain (or a standalone CIFS depending on your environment).
NFS protocol is for UNIX access and unless you need any UNIX host accessing this data, there is no need to create NFS export. Please note that the data resides on the file system which is the same here - it only matters how you are going to access the data on the network - using CIFS (windows) or NFS (Unix) or both.
You can also have multi-protocol access - means both NFS and CIFS access to the same file system - it will be little complicated from Access permission and User mapping perspective. But I understand this is not your case as you mentioned you only need Windows hosts to access the file system.
Anyway - if you have not gone through these docs - you may consider to read them on Powerlink or on Documentation CD -
1) configuring CIFS
2) Configuring NFS
3) Managing Celerra for a Multiprotocol Environment
You also may find some older posts on this forum regarding CIFS, NFS and multi-protocol access - some of them are -
https://community.emc.com/message/381520#381520
https://community.emc.com/message/385611#385611
https://community.emc.com/message/453604#453604
Hope this helps, please feel free to revert back.
Regards,
Sandip