In Windows on the relevant system set up NFS service and client mount in two ways:
The first:
(There are built-in NFS service built on Windows Server2008R2 and other such similar version of the Enterprise Edition Server service)
(Special Note: The following is the author piazini fruits of labor, I cut the chart, on this basis, coupled with his understanding but because it is before the cut-off Figure, forget the URL.)
Setting shared directory:
On the client, I wrote a bat executable file, I put the source code stickers:
Note @rem command corresponding to the C language / * ----------------------- * / @echo OFF @rem Color 0A title mount 172 .16.1.200 PAUSE @echo showmount command execution results are as follows showmount - E 172.16.1.200 PAUSE @echo operate the E letter Choice / C 123 / M "by the letter E 1 loading, the solution linked by 2, to cancel press. 3" IF ERRORLEVEL . 3 GOTO End IF ERRORLEVEL 2 GOTO umount IF ERRORLEVEL . 1 GOTO Mount : Mount Mount 172.16.1.200 : / E the NFS: @echo executed successfully mount such use NET / persistent: Yes Choice / M "performed by Y, is not performed by the N" iF ERRORLEVEL 2 GOTO nO iF ERRORLEVEL1 GOTO yes : NO GOTO End : yes @echo ON NET use / persistent: yes @echo OFF GOTO End GOTO End : umount umount E: GOTO End : End echo all ok now, then worship pause
Another: haneWin
( In the third-party software haneWin build)
A, haneWIN software server configuration
- HaneWIN install software
- Sign up :( haneWIN NFS Server Keygen.exe ) runs RI, enter the Name , click the left button to generate Serial ( Min. 8 Chars eingeben ... at least 8 characters)
- Click Output -> compiler output file table
A pop-up notepad editing interface. My configuration is as follows:
# exports example
c:\upload -public -name:NFS
# C: \ upload is shared folder path
# -Public represents public authority -readonly read-only
# -Name: NFS indicate why the name display
#c:\upload -range 192.168.1 192.168.10
# -range within the network can be set up to share the machine's iP address range , if not -range this parameter range, then that is the intranet all machines open ( 192.168.1 within the network can share the machine's starting address of 192.168.10 within the network can be shared the end of the address of the machine)
4. must be restarted to take effect . ( Windows started -> haneWIN Software -> NFS-> Restart all services)
5. Then the firewall settings, as shown below
Second, client settings: (for the mounting operation)
- Please refer to this windows mounted nfs.png shots .
Wherein Before mounting dos enter:
ping 192.168.1.49 # First can ping the same NFS server
mount -h or mount? # command help (not an error, indicating that the client is available)
showmount -e 192.168.1.49 # View mount point
192.168.1.49:/NFS X Mount : # mount X disk
(Where / NFS is available showmount command to find out , that is, on the server side exports provided)
-o nolock 192.168.1.49:/NFS the X-Mount : # with mount -h command to view the know -o nolock to disable the lock
umount x: # solution linked to X disk
View monut # mount machine parameters
net use / persistent: yes # This command is to perpetuate disk mapping
(Note: If you have to mount the disk will cause the remote NFS server restart error can only forcibly kill off the service to shut down)
These two methods are windows method under. Linux set up would be better at, but because of the company's services are windows server2008R2 on, so linux is not to study. Another more screenshots and haneWin saved hard disk.