␡
- Challenges of File Sharing
- Different Protocols for Different Clients
- Planning File Services
- Using Apple Filing Protocol
- Configuring Apple File Service
- Monitoring AFP Activity
- Using Windows File Service
- Configuring Windows File Service
- Configuring Access and Starting Windows File Services
- Using NFS Share Point Access
- Configuring NFS
- Using FTP File Service
- Configuring FTP Service
- Network-Mounted Share Points
- Preparing for a Network Home Folder
- Configuring Network Mounts
- Controlling Access to Shared Folders
- Troubleshooting File Services
- What Youve Learned
- References
- Chapter Review
< Back
Page 21 of 21
This chapter is from the book
Chapter Review
- Name four file-sharing protocols supported by Mac OS X Server and their principal target clients.
- How does Mac OS X Server support browsing for Windows clients?
- What is the primary security concern with NFS?
- What does FTP file conversion do?
Answers
- AFP for Mac clients; SMB for Windows clients; NFS for UNIX clients; and FTP for multiple cross-platform client access are four file-sharing protocols supported by Mac OS X Server.
- On smaller networks, Mac OS X Server uses NetBIOS to advertise its presence. On larger networks, Mac OS X can be a WINS server, or it can use an existing WINS server. If there are no other servers on the network, Mac OS X Server can be a workgroup master browser or a domain master browser.
- Normally, NFS has no user-authentication process: NFS trusts that the client is who it claims to be. Beyond a security concern, this can also be a management issue if the client and server aren’t working with a unified user list. If you’re using Kerberos with NFS, you can authenticate the connection process, however.
- FTP file conversion is a feature of the FTP server that automatically encodes a file or folder requested by an FTP client. The client appends .tar, .bin, or .gz to the end of the filename, and the server does the appropriate encoding.
< Back
Page 21 of 21