Proof of Concept: NFS Attributes Editor

Proof of Concept: NFS Attributes Editor We come across a lot of people who have IdMU tools installed even though they don’t use the NIS authentication. This, primarily, happens because they have NFS in their environment and with Windows Vista and later, the only way to get identities mapped is by way of Active Directory…


Using Kerberos Authentication for Server for NFS

Using Kerberos Authentication for Server for NFS It has always been attributed that the NFS communication is inherently insecure and that’s completely true. There are certain security options but they aren’t enough to protect the data from unauthorized access. Fortunately, the NFS architecture is flexible and it allows you to plug in additional authentication methods. So,…


Managing Client Groups – An Easier Approach

Managing Client Groups – An Easier Approach On UNIX-based NFS servers, it’s much easier to control access to the NFS shares based on host names or IP addresses. You just have to put them in the export file and it’s done. It’s not so difficult in Windows either – you can click on the Permission…


Getting AD Lookup to work without UNIX Attributes tab

Getting AD Lookup to work without UNIX Attributes tab The previous post talks about how to get the UNIX Attributes tab to work without installing IdMU components. In this post, I would like to talk about what attributes the NFS components expect to be populated in AD for user and group object before it can…

5

AD Lookup with ADAM/ADLDS

AD Lookup with ADAM/ADLDS With removal of UNM in Vista/W2K8, it became really problematic to map users in non-AD environments to use with Vista/LH NFS Servers and Clients. For client, a workaround was discovered which was essentially a registry tweak and did allow more than user to be able to access the resources. Now, a…


Limitation with Active Directory Lookup feature in Microsoft Services for NFS

Limitation with Active Directory Lookup feature in Microsoft Services for NFS The Active Directory Lookup feature that was introduced with Windows Server 2003 R2. This feature greatly simplifies the UNIX identity information management but has its own set of limitation. I thoughy I’ll document them here – 1. If you are using Client for NFS in conjunction…


Set up Services for Network File System in Windows Server 2008

Set up Services for Network File System in Windows Server 2008 The Microsoft Services for NFS continues to be the part of the operating system in Windows Server 2008 and seems we will see more improvements when Windows Server 2008 R2 is released. In Windows Server 2008, a major change from the Windows Server 2003…

10

How User Name Mapping works?

How User Name Mapping works? User Name Mapping is the core NFS authentication component in Services for UNIX, Windows Server 2003 R2 and Windows Vista. It bridges the gap presented by difference in user identification methods used by Windows and UNIX systems. It plays equally important role for Server for NFS and Client for NFS…

8

Set up Server for NFS in Windows Server 2003 R2

Set up Server for NFS in Windows Server 2003 R2 In this post, I will talk about configuring Microsoft Services for Network File System, mainly Server for NFS and User Name Mapping, in Windows Server 2003 R2. You can follow the same steps for Services for UNIX (SFU) 3.5 except only a few of them…

11

Using chown/chgrp from UNIX clients

Using chown/chgrp from UNIX clients Why it is still owned by 4294967294? Haven’t I mapped root user to Administrator user? Well, you might recall – in Windows world a file or directory can be owned by a user or a group. Since default owner happens to be the Administrators group, you can see this mount…