Pcnfsd authetication in NFS share

I have a G5 10.4.8 serving a NFS share. The one client is a Win95 box running NFS Maestro . It has worked before but in rebuilding it, I'm stuck. The client requires pcnfsd authentication but inetd.conf states that (rpc.) pcnfsd is not yet implemented in OS X. NFS Manager has nothing as well. Is there a way to fix this?
G5 Mac OS X (10.4.8) Not OSX Server

This is frustrating!.. I've managed to get that working but i have a different issue now ..here is what i have done in details:
Server: MAC OSX 10.6.8.
Server was standalone and then I bounded to the AD then promoted to Open Directory Master without kerberos realm - as it is the AD is the one that holds the accounts.. that's how it should be correct ?
Disk utility: I mounted the NFS share and in WGM i enabled file sharing on the NFS share via AFP, and now it shows under WGM - Home tab as: afp://xserve.mydomain.com/homes
- for the clients, I bounded them to OD first for MCX and then to AD.
Directory Utility: settings for both "client & server"
*Create mobile account at login - false
*Force local home directory on startup disk - false
*Une UNC path - True with AFP protocol.
Server Admin:
* AFP is enabled on the NFS share "homes" and its auto-mounted.
* Open Directory Master:
- LDAP Server is running
- Password Server is running.
- Kerberos is stopped.
Workgroup Manager:
* I selected the test user "adtest" and assigned the home folder which is:
Home URL: afp://xserve.domain.com/homes/adtest
Full Path: /Network/Servers/xserve.domain.com/homes/adtest
and when i click on Create Home Now, it did create the user home directory under the NFS share which is auto-mounted
Active Directory Server:
under the adtest user - profile tab, i see: \\xserve.domain.com\homes\adtest
Problem:
- when i try to login with adtest user from the client, i get the error message:
"You are unable to login in o the user account "adtest" at this time - logging in to the account failed because an error occurred."
Troubleshooting:
1- logged in with local admin account and typed id adtest in terminal.. it shows all user attributes and groups, which means the machine is bound correctly to both AD & OD
2- when I change the home for the user to the the default "/Users".. i can login just fine with the adtest account.. does that look like its a permissions issue ?
Thanks again for your help.

Similar Messages

Adding NFS Share to Mountain Lion Server

Alright, here goes.
The company I work for has been using SL server for years and wanted to test a possible upgrade to ML server for NFSv4. Downloaded ML to test machine and ML server. I mounted it via server connector (nfs://blah blah..you get the idea) volume that I want to share comes up on desktop but will not show under the server app. I also have access to posix but I need full access to acl as well.
I'm trying to figure out how to access this NFS share so that I can share it from the server but cannot seem to get it working. To those who know OSX servers I probably sound like a moron, but I'm just an I.T. guy tasked with setting up a test server even though I'm not a "server guy". Any information would be greatly appreciated.
One more question. Would a migration from SL to ML server also bring along this volume? Thanks again.

I upgraded today and had the same issue. I took following steps to fix my computer.
Boot into Recovery Partition (Hold Option Button while booting)
Open Terminal.
Type resetpassword
Select your hard drive
Select the user account (Administrator)
Enter a new password for the user
Reenter password
Save
Restart
Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
Restart
Everything should be working as expected

How can a mount a NFS share exported from OpenBSD?

Hello Apple Discussions:
I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
http://www.bsdforums.org/forums/showthread.php?t=54308
Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
ON THE OPENBSD BOX:
#/etc/exports
/fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
/exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
#/etc/hosts.deny
ALL: ALL
#/etc/hosts.allow
ALL: 192.168.222.233 192.168.222.253
#/etc/rc.conf.local
portmap=YES
lockd=YES
nfs_server=YES
#here's proof that the daemons are running on the OpenBSD box;
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 863 mountd
100005 3 udp 863 mountd
100005 1 tcp 613 mountd
100005 3 tcp 613 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 895 nlockmgr
100021 3 udp 895 nlockmgr
100021 1 tcp 706 nlockmgr
100021 3 tcp 706 nlockmgr
# actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
ON THE TIGER SERVER:
# here's proof that tiger server sees the mounts:
showmount -e 192.168.222.111
Exports list on 192.168.222.111:
/fives 192.168.222.0
/exports/fives 192.168.222.233 192.168.222.253
# here's the result of user fives' attempt at mounting a share:
sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
mount_nfs: /imports/fives: Permission denied
# yet user fives has no problem mounting same share on linuxppc box.
What is different about OSX server? I thought it was supposed to speak NFS?
---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
Each user is free to choose which of those tracks they want in their library.
There is an Apple help article on multiple users.
http://docs.info.apple.com/article.html?artnum=300432

Custom NFS share point directory showing up on all network machines

Hi,
I'm in the process of migrating our 10.4 PowerMac server to a Mac Pro (running 10.5). I've been trying to recreate our 10.4 server setup as much as possible and so far I've only come across one annoying issue.
We have fink installed on the server and under our 10.4 setup the /sw directory was set up as an NFS automounted share point with a custom mount point of '/sw'. I.e. users logging into client machines saw a /sw directory and could work with that. This made it easier to add fink packages as I only needed to do this on one machine (the server). This setup worked very well under 10.4 and had been working stably for the last couple of years.
As we now have (for another month or two at least) a mix of intel and Power PC machines, I don't want to share out the (intel) server version of fink to all clients. In Server Admin, I have chosen to set the NFS protocol options to specify the IP address of just one client (an intel machine). I am only using NFS to share this directory. The plan is to add more client IP addresses as we get more intel machines.
This works for the one intel client machine. Logging in via the GUI or via ssh allows you to run programs located under the /sw directory. The problem is that a phantom /sw directory appears on all client machines, even though their IP addresses are not specified in Server Admin. The /sw directory has root/wheel permissions (for user/group) and attempting to list its contents returns 'Operation not permitted' (even with 'sudo ls /sw').
If I use Directory Utility to remove the connection to the Directory server on our main server, then the /sw directory becomes owned by root/admin and I can remove it (it appears empty). Reconnecting to the Directory Server changes the permissions back to root/wheel. It is also worth noting that when I first installed fink on the server (in /sw) the act of making this a share point also changed the permissions on /sw to root/wheel meaning that I couldn't access the fink programs that I had only just installed (this forced me to reinstall fink in /Volumes/Data/fink).
Has anyone else noticed this behavior? It almost seems like Server Admin is not honoring the list of IP addresses that are being listed as targets for client machines. I had planned to install fink locally on the PowerPC clients until we upgrade them to intel machines. However, I would then also have to install fink somewhere other than /sw as I can't write to that directory. I would presume that this behavior should happen on any NFS share point that is trying to automount to a custom mount point on a client. Can anyone else verify this?
Regards,
Keith

As a footnote. I have now removed my shared fink installation. It is no longer listed as an NFS sharepoint in Server Admin and running the 'showmount -e' command does not list it. However, a /sw directory is still being created on the server and on the client machines on our network.
This is perplexing and frustrating. There is no sharepoint any more. I rebooted the server but it makes no difference. I removed the /sw directory (on the server) by booting the machine in target firewire mode and removing it by using a 2nd machine. But following the restart, it appeared again.
This suggests that once you make any custom mountpoint (using NFS sharing) then you will forever be stuck with a directory at the root level of all your clients which you can not remove.
Keith

Launching xcode from nfs share (Ensure that Xcode.app is installed on a volume with ownership enabled)

Hi!
We have mac mini (Yosemite) and NFS server under Ubnuntu 14.04.
Also we have xcode resides on NFS share that mounted to mac.
Problem: When I try launch xcode from nfs share I got error message:
NSLocalizedRecoverySuggestion=Ensure that Xcode.app is installed on a volume with ownership enabled
You can see full error here:
https://gist.github.com/keferoff/fcfd3ea6c13f6ba481fa
The question is:
How I can launch xcode from nfs share? For some reasons I can't use xcode-select or store several xcodes locally.
Thanks in advance!

It's cool answer but I need solution how to accomplish my task. Maybe I can use iSCSI device or NBD device ot maybe there we have some NFS mount options?

Can't create or mount NFS share

I am trying to create an NFS share on a server that already does quite nicely sharing AFP and SMB. A friend tells me that this is easy but I can't make it work, I'm still told that my password is incorrect.
Can you watch this short movie to see what I'm doing and advise what I'm doing wrong?
Thank you in advance.

I am trying to create an NFS share on a server that already does quite nicely sharing AFP and SMB. A friend tells me that this is easy but I can't make it work, I'm still told that my password is incorrect.
Can you watch this short movie to see what I'm doing and advise what I'm doing wrong?
Thank you in advance.

New files and folders on a Linux client mounting a Windows 2012 Server for NFS share do not inherit Owner and Group when SetGID bit set

Problem statement
When I mount a Windows NFS service file share using UUUA and set the Owner and Group, and set the SetGID bit on the parent folder in a hierarchy. New Files and folders inside and underneath the parent folder do not inherit the Owner and Group permissions
of the parent.
I am given to understand from this Microsoft KnowledgeBase article (http://support.microsoft.com/kb/951716/en-gb) the problem is due to the Windows implmentation of NFS Services not supporting the Solaris SystemV or BSD grpid "Semantics"
However the article says the same functionality can acheived by using ACE Inheritance in conjunction with changing the Registry setting for "KeepInheritance" to enable Inheritance propagation of the Permissions by the Windows NFS Services.
1. The Precise location of the "KeepInheritance" DWORD key appears to have "moved" in Windows Server 2012 from a Services path to a Software path, is this documented somewhere? And after enabling it, (or creating it in the previous
location) the feature seems non-functional. Is there a method to file a Bug with Microsoft for this Feature?
2. All of the references on demonstrating how to set an ACE to achieve the same result "currently" either lead to broken links on Microsoft technical websites, or are not explicit they are vague or circumreferential. There are no plain Examples.
Can an Example be provided?
3. Is UUUA compatible with the method of setting ACE to acheive this result, or must the Linux client mount be "Mapped" using an Authentication source. And could that be with the new Flat File passwd and group files in c:\windows\system32\drivers\etc
and is there an Example available.
Scenario:
Windows Server 2012 Standard
File Server (Role)
+- Server for NFS (Role) << -- installed
General --
Folder path: F:\Shares\raid-6-array
Remote path: fs4:/raid-6-array
Protocol: NFS
Authentication --
No server authentication
+- No server authentication (AUTH_SYS)
++- Enable unmapped user access
+++- Allow unmapped user access by UID/GID
Share Permissions --
Name: linux_nfs_client.host.edu
Permissions: Read/Write
Root Access: Allowed
Encoding: ANSI
NTFS Permissions --
Type: Allow
Principal: BUILTIN\Administrators
Access: Full Control
Applies to: This folder only
Type: Allow
Principal: NT AUTHORITY\SYSTEM
Access: Full Control
Applies to: This folder only
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

I'm making some "major" progress on this problem.
1. Apparently the "semantics" issue to honor SGID or grpid in NFS on the server side or the client side has been debated for some time. It also existed as of 2009 between Solaris nfs server and Linux nfs clients. The Linux community defaulted to declaring
it a "Server" side issue to avoid "Race" conditions between simultaneous access users and the local file system daemons. The client would have to "check" for the SGID and reformulate its CREATE request to specify the Secondary group it would have to "notice"
by which time it could have changed on the server. SUN declined to fix it.. even though there were reports it did not behave the same between nfs3 vs nfs4 daemons.. which might be because nfs4 servers have local ACL or ACE entries to process.. and a new local/nfs
"inheritance" scheme to worry about honoring.. that could place it in conflict with remote access.. and push the responsibility "outwards" to the nfs client.. introducing a race condition, necessitating "locking" semantics.
This article covers that discovery and no resolution - http://thr3ads.net/zfs-discuss/2009/10/569334-CR6894234-improved-sgid-directory-compatibility-with-non-Solaris-NFS-clients
2. A much Older Microsoft Knowledge Based article had explicit examples of using Windows ACEs and Inheritance to "mitigate" the issue.. basically the nfs client "cannot" update an ACE to make it "Inheritable" [-but-] a Windows side Admin or Windows User
[-can-] update or promote an existing ACE to "Inheritable"
Here are the pertinent statements -
"In Windows Services for UNIX 2.3, you can use the KeepInheritance registry value to set inheritable ACEs and to make sure that these ACEs apply to newly created files and folders on NFS shares."
"Note About the Permissions That Are Set by NFS Clients
The KeepInheritance option only applies ACEs that have inheritance enabled. Any permissions that are set by an NFS client will
only apply to that file or folder, so the resulting ACEs created by an NFS client will
not have inheritance set."
"So
If you want a folder's permissions to be inherited to new subfolders and files, you must set its permissions from the Windows NFS server because the permissions that are set by NFS clients only apply to the folder itself."
http://support.microsoft.com/default.aspx?scid=kb;en-us;321049
3. I have set up a Windows 2008r2 NFS server and mounted it with a Redhat Enteprise Linux 5 release 10 x86_64 server [Oct 31, 2013] and so far this does appear to be the case.
4. In order to mount and then switch user to a non-root user to create subdirectories and files, I had to mount the NFS share (after enabling Anonymous AUTH_SYS mapping) this is not a good thing, but it was because I have been using UUUA - Unmapped Unix
User Access Mapping, which makes no attempt to "map" a Unix UID/GID set by the NFS client to a Windows User account.
To verify the Inheritance of additional ACEs on new subdirectories and files created by a non-root Unix user, on the Windows NFS server I used the right click properties, security tab context menu, then Advanced to list all the ACEs and looked at the far
Column reflecting if it applied to [This folder only, or This folder and Subdirectories, or This folder and subdirectories and files]
5. All new Subdirectories and files createdby the non-root user had a [Non-Inheritance] ACE created for them.
6. I turned a [Non-Inheritance] ACE into an [Inheritance] ACE by selecting it then clicking [Edit] and using the Drop down to select [This folder, subdirs and files] then I went back to the NFS client and created more subdirs and files. Then back to the
Windows NFS server and checked the new subdirs and folders and they did Inherit the Windows NFS server ACE! - However the UID/GID of the subdirs and folders remained unchanged, they did not reflect the new "Effective" ownership or group membership.
7. I "believe" because I was using UUUA and working "behind" the UID/GID presentation layer for the NFS client, it did not update that presentation layer. It might do that "if" I were using a Mapping mechanism and mapped UID/GID to Windows User SIDs and
Group SIDs. Windows 2008r2 no longer has a "simple" Mapping server, it does not accept flat text files and requires a Schema extension to Active Directory just to MAP a windows account to a UID/GID.. a lot of overhead. Windows Server 2012 accepts flat text
files like /etc/passwd and /etc/group to perform this function and is next on my list of things to see if that will update the UID/GID based on the Windows ACE entries. Since the Local ACE take precedence "over" Inherited ACEs there could be a problem. The
Inheritance appears to be intended [only] to retain Administrative rights over user created subdirs and files by adding an additional ACE at the time of creation.
8. I did verify from the NFS client side in Linux that "Even though" the UID/GID seem to reflect the local non-root user should not have the ability to traverse or create new files, the "phantom" NFS Server ACEs are in place and do permit the function..
reconciling the "view" with "reality" appears problematic, unless the User Mapping will update "effective" rights and ownership in the "view"
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

Issue with special character in NFS shares

Hello,
I run a Ubuntu 10.04 server for serving my files via NFS. I have no problems mounting the NFS shares in my iMac (OS X 10.6.3). I can access all files, even the ones containing special characters in their names. I can copy, create, move them with no problem, both on Finder and on the Terminal.
The problem comes when I try to synchronize or backup files using backup tools. Files with accents in their names (á, é, ã, ç, etc) are simply ignored by the backup/sync tools I am using. I could reproduce the problem in different softwares like "ChronoSync" and "File Synchronization". Accents are a must have in my network.
I saw in other posts in this forum that there might be some incompatibilities with Unicode and special chars while using Mac OS X as a NFS client for a Linux NFS server. What strikes me is that Finder and Terminal work just OK.
Any clue?
Some details of my NFS configuration:
/etc/exports on my server:
/mnt/disco01 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco02 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco03 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco04 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
On my iMac I moount them like this using Disk Utility's NFS tool:
URL: nfs://servidor/mnt/disco01
Mount point: /Network/disco01
Options: -P nosuid
Thanks for any help you can give me.

Well, I dug a little further and got a solution, although It make no sense to me.
So, the scenario is:
server URL: nfs://server/mnt/disco01
mount point: /Network/disco01
I was trying to synchronize a folder from the server called /Network/disco01/Música (meaning music in Portugueses) to a local folder /Users/shared/Música. I would use ChronoSync to keep the folders in sync, mirroring the NFS share to the local folder. ChronoSync was ignoring the folder.
After not being able to copy using the ChronoSync tool, I tried to copy the folder via the Finder. I could browse the nfs share using the finder, but not copy the files the local folder.
While trying to copy, I use Cmd-C then Cmd-V in the /User/shared/ folder. I noticed that first the Finder named the folder "Music" and then some instants after if would refuse to copy. Very strange.
I first renamed the "Música" folder on the NFS share to "Músicas", then everything worked allright, even Chronosync. Turns out that Música is the name of one of the system folder OS X creates on the user's home folder. It is actually a translation to the underlying name Music.
Why it was interfering with the copy of totally unrelated NFS and local folders I can really not understand.
More interesting, afterwards I renamed the NFS folder again to Música (without s) and it kept working.
I am happy now, but I have no clue as to why there was the problem, and why it got solved.
Hope this helps somebody in a similar situation.

[SOLVED] MPD through mounted NFS Share

Hi all. I am using MPD paired with Ncmpcpp, and in my configuration (for both mpd & ncmpcpp) I have the music directory set to /mnt/Shares/Music which is where I am mounting a NFS share located on the local network.
However ncmpcpp seems to be only partially reading the directory. In the server directory I have two subdirectories (mp3 and ogg) but my music player seems to only be reading the mp3 directory. I have tried updating the database through ncmpcpp, restarting the computer, restarting mpd through systemctl, and even tried using symlinks within the directory (and having "follow internal" and "follow external" symlinks set to "yes" in /etc/mpd.conf).
None of these seem to work in making mpd read the ogg directory.
Edit: Mounting through NFS automatically chowns the share to the local user, so not only did I have to sudo chown -R <user>:users the music share directory on the host I also had to reconfigure my MPD settings to run as a local user as well in order to have proper permissions for the NFS share. Prior to that it was running system wide as the MPD user. This has solved the problem completely.
Last edited by felixculpa (2012-12-26 05:24:19)

WonderWoofy wrote:
Awesome, don't forget to mark your thread as [Solved] by editing your first posts. Sorry I couldn't have been of better help to you. Glad you solved it though.
Edit: I did think it kind of odd (and unlikely) that ogg would not be an automatically supported format, but the source told me otherwise... strange.
Thanks. The Arch community is awesome and I appreciate the help I get in the forums. I am currently updating the database but it is taking quiet some time, so I am not 100% I have fixed the problem. After it is done, and if it works I will update the thread as [Solved].
Thanks again.
Edit: I forgot to mention that I was mistaken in the not reading ogg files part. It was reading only some files from both directories; it just wasn't reading the files it didn't have permission for I'm guessing.
Last edited by felixculpa (2012-12-26 03:47:46)

Windows 2012 R2 - Access problems to NFS shares via IPv6

Hello,
we setup some NFS shares on HNAS storage box. The connection to this storage is only possible over IPv6 network.
My server with Windows 2012 R2 has the feature 'Client for NFS' installed and a 'showmount -e servername/or IPv6 address' works. I can see all shares when i try to open the storagebox in Windows Explorer with the command "\\servername" or "\\IPv6
address", too.
My problem is, when I try to mount the share via "Map network drive" or "mount \\servername\sharename *" I get Error 53 - Network path not found.
The share is configured that every server in the IPv6 subnet could access it and it works on Unix machines, but not on Windows.
It does not matter if i set some option parameters for the "mount" command like sec=sys or anon, everytime error 53.
I don't know, if the share needs special options for Windows. I hope somebody can help.
Kind regards

Hi,
here is the output of your 2 commands:
PS C:\Users\admin> get-SmbConnection
PS C:\Users\admin> get-SmbServerConfiguration
AnnounceServer                  : False
AsynchronousCredits             : 64
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 0
AnnounceComment                 :
EnableDownlevelTimewarp         : False
EnableLeasing                   : True
EnableMultiChannel              : True
EnableStrictNameChecking        : True
AutoDisconnectTimeout           : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing   : False
EnableForcedLogoff              : True
EnableOplocks                   : True
EnableSecuritySignature         : True
ServerHidden                    : True
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                : HydraLsPipe
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RequireSecuritySignature        : False
EnableSMB1Protocol              : True
EnableSMB2Protocol              : False
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True
EncryptData                     : False
RejectUnencryptedAccess         : True
I try to access the file share with Windows Explorer. When I enter \\fe08--babe-face-cafe-dead.ipv6-literal.net (just example), I can see all shares on the storage box. When I double-click the share, I want to access, where an access is definitely allowed,
it takes a while and then the error "\\fe08--babe-face-cafe-dead.ipv6-literal.net\share is not accessable. You might not have permission to use this network resource. ..." appears. Of this action a recorded the trace.
Another way I tried is to open command line an type "mount \\fe08--babe-face-cafe-dead.ipv6-literal.net\share *". After this an error 53 occurs immediately without any wait time.

How to create an nfs share using the method "CreateShare" of class "MSFT_NfsServerTasks"

I need to use the "CreateShare" of the wmi class "MSFT_NfsServerTasks" to create a nfs share.
I am new to wmi. could somebody please guide me to achieve this. thanks in advance.

let to me rephrase my question. I need to call the MSFT_NfsServerTasks::createmethod to create the nfs share.
And the syntax for this method is
uint32 CreateShare(
[in] string Name,
[in] string Path,
[in] string NetworkName,
[in] string Authentication[],
[in] boolean UnmappedUserAccess,
[in] boolean AnonymousAccess,
[in] sint32 AnonymousUid,
[in] sint32 AnonymousGid,
[in] string LanguageEncoding,
[in] boolean AllowRootAccess,
[in] string Permission,
[in] MSFT_NfsSharePermission ClientPermission[],
[out] MSFT_NfsShare Share
And to run this method I will be using "IWbemServices::ExecMethod". This method takes the Input parameter object(IWbemClassObject). I managed to add string the parameters in the input parameterobject as,
IWbemClassObject* pInInst = NULL;:/*some code*/
VARIANT var;
var.vt = VT_BSTR;
var.bstrVal= SysAllocString(L"C:\\share1");
BSTR ArgPath = SysAllocString(L"Path");
hRes = pInInst->Put(ArgName, 0, &var, 0);
But how could I use it for other parameters e.g. string[], MSFT_NfsSharePermission ClientPermission[]etc.

Permission Denied on Solaris 10 NFS share, shared trough Windows Server 2008R2

Hello,
We have a NFS share on Windows Server 2008 R2 setup the following way,
NTFS permissions for ANONYMOUS LOGON and Everyone groups are set to Full control.
When mounting this share on our Solaris workstation, it mounts and we can view files in that mount but cannot edit or write to it.
mount -f nfs 10.0.0.2:/Folder/ /test
permissions are set as:
drwxrwxrwx 2 nobody nobody 4096 Mar 4 08:57 test/
when in test direcorie, trying to copy a file gives this error:
cp gp.txt gp_1.txt
cp: cannot create gp_1.txt: Permission denied
Please help,
Thanks

Hi,
Is there any error message in the Event Log on Windows Server 2008 R2? Please try to install the hotfix in the KB article below.
"Permission Denied" error when a UNIX user accesses files on an NFS share in Windows Server 2008 R2
http://support.microsoft.com/kb/2485529
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Files in NFS share not visable

I'm trying to install Solaris 10u4 from a Netra T1-200 install server. The client is a Sun Enterprise 5000, it boots fine during the network install but gives the error "The directory you specified doen not contain a valid Solaris OS image".
If I mount the same NFS share from a Linux box I can see all the files in the Boot directory but there are no files visable in the Tools or Solaris_10 directory. I've verified that they exist on the Netra but the are not visable in the share.
Any help in resolving this problem would be greatly appreciated.
Thanks,
Jack

OK, i can replicate it by doing the following on the server:
<pre>
# touch test\ file\ one.txt
# touch test\ file\ one\ two.txt
# touch test\ file\ one\ two\ three.txt
# touch test\ file\ one\ two\ three\ four.txt
# touch test\ file\ one\ two\ three\ four\ five.txt
</pre>
the last two files (ending in four and five) do not appear in finder.
It seems that if there are 5 or more spaces in a filename the file will not appear.
This seems like a bug doesn't it? how would I go about reporting it to apple?
Thanks
ed

NFS share mount on solaris 10 : error 48

I got the below error when mount NFS share on solaris 10 . Please help
Oct 20 10:02:12 etravel2k nfs: [ID 182275 kern.warning] WARNING: NFS server initial call to scom01 failed: error 48

Hi,
try to force the mount with nfs version 3.
# mount -o vers=3 server-name:/share-point /local-dir
regards
Walter

CM Repository for NFS share

Hello,
We are on EP 7.0 sp14 (windows) and currently have several CM repositories pointing to external Windows File shares.
Is it possible to point CM Repository to NFS share?
Thanks,
Alex
Edited by: Alex Trosman on Jan 13, 2009 10:14 PM

Hi Ramalakshmi,
you are using a CM Repository in FSDB Mode. Am I right? If so, check the following:
1. Did you configure your Network Path? The specified user should have full access to the resource.
2. Did you configure the Root Directory? Note: The Root Directory in your Repository Manager mustn't point to the same directory of your network path!!
3. Did you configure the Root Directory for Versions? Note: The Root Directory for Versions mustn't be a subfolder of your Root Directory!! Must point to a folder which contains the subfolders "versions, workingresources, workspaces, wastebasket"!
4. Persistence Mode must be set to "FSDB"
5. Windows Landscape System must be the same as your Network Path.
Hope this helps and will solve your issue.
Best regards,
Denis

Pcnfsd authetication in NFS share

Similar Messages

Maybe you are looking for