Windows Server2012 R2 Deploying a network File system

Network File System Preview

The network File system services and Roles feature in Windows server2012 R2 with Windows server2012 contains the file and storage server roles. The network File system provides enterprise-class file sharing solutions that are based on Windows and non-Windows systems.

Function description

With the NFS protocol, you can transfer files on files that are running Windows and non-Windows operating systems.

Windows Server 2012,nfs contains two components, NFS server side and NFS client. NFS Server enables NFS file servers to run Windows Server2012 computers as non-Windows computers, and NFS clients enable one to run Windows Server 2012 of Windows computers go to access files for NFS servers that are stored on non-Windows computers.

Real-world applications

Use Windows NFS file server to provide multi-protocol access to the same file share on different clients using SMB and NFS protocols

Deploying a Windows NFS file server in an apparent non-Windows operating system environment to access NFS file shares for non-Windows computers

Migrating applications from one operating system to another by using the data stored by the file share accessed by the SMB and the NFS protocol.

New features added to the network file system

Support NFS4.1

About the simplicity of firewall settings

Supports RPCSEC_GSS protocol for stronger security

Support for Windows and UNIX file semantics

Deploy with a clustered file server

NFS modules for the Windows kernel

Upgrade for NFS Management

Integration with Recovery Key Manager

Scenarios that use NFS

NFS supports a hybrid environment based on Windows and UNIX operating systems. The following deployment scenario is how file sharing is deployed.

Providing file sharing in a heterogeneous environment

Using multiple protocols (SMB Protocol and NFS protocol) to access the same file share, when you deploy a Windows file server, you need to collaborate on a user's different computers in Windows and UNIX. When a file share is configured, it is shared via SMB with the NFS protocol. Windows operating system users access files using the SMB protocol, and UNIX users access files using the NFS protocol.

To implement this scenario, you must implement an effective mapping source configuration

1) Mapping File

2) Active Directory service

3) RFC2307 compatible light Active Directory service (LDAP) storage

4) User Name Mapping (UNM) server

File sharing for UNIX-based environments

Windows file server provides file access sharing based on the UNIX client environment. The non-mapped UNIX user access (UUUA) option is the first to implement an NFS share in Windows Server R2, so that the server can use NFS data storage without having to create a UNIX-to-Windows Windows account mapping.

System Requirements

Server for NFS can be deployed on any version of Windows server2012. You can use NFS and UNIX-based computers that are running NFS servers or NFS clients if these NFS servers and client implementations conform to one of the following protocol specifications

NFS Version 4.1 protocol specification

NFS Version 3.0 Protocol specification

NFS Version 2.0 Protocol specification

Deploying the NFS Architecture

To deploy an NFS server, you need to deploy the following servers and remain connected on your local physical network.

One or more servers running Windows Server 2012, the server will install two primary NFS Component Services: NFS Service side and NFS client. The two Component Services can be installed on the same computer or on a different computer.

Domain controllers that run the functional level of Windows SERVER2008R2, which provides user authorization and mapping for Windows environments

Without a domain controller, you can use the Network Information service to provide user Authorization for UNIX environment users, or you can use a computer running the User Name Mapping service to save passwords and group files.

Install Network File System (NFS) install Network File System (NFS) using the Server Manager method

1. Select the file and storage service in the ADD Roles and Features Wizard

2. Under File and Storage service, select File server and server for NFS.

3. Select Install

Install (slightly) Configure NFS licensing using the command line method

Using NFS4.1 with the NFS3.0 protocol, you can use the following authorization and security options.

RPCSEC_CSS Authorization

KRB5 Authorization

krb5i authorization, with confirmation of no modification

krb5p authorization, authorization with encrypted information

Auth_sys creating an SMB file Share

1. Select File and storage service in Server Manager, click Share, select New in Task Share

2. Select the configuration page, protocol type SMB or NFS

3. Select share location, and select a custom path C:\Share

4. Set share name, select the default name

5. Set other Settings, select Allow Caching of share

6. Set permissions, set the user's access control type

7. Setting Management Properties

9. Set Quota

10. View confirmation Information

Test connection

After you set up the SMB share, test the Windows operating system with the Linux operating system

1) Windows Test Connection

\\192.168.56.15\share

2) connection to Linux

For the CENTOS7 operating system also supports the SMB protocol, the SMB sharing method for accessing Windows is

Smb://192.168.56.15/share/

You can also use smbclient access (this method displays the results as a command line)

[Email protected] desktop]# smbclient--user=administrator//192.168.56.15/share

Enter Administrator ' s password:

Domain=[qstest] os=[windows server R2 standard Evaluation 9600] server=[windows server 6 R2 standard Evaluation. 3]

SMB: \> Help

Windows Server2012 R2 Deploying a network File system