HP StorageWorks 4000s NAS 4000s and 9000s Administration Guide - Page 157

Microsoft Services for NFS, Server for NFS, Authenticating User Access

Page 157 highlights

Microsoft Services for NFS 8 Microsoft Services for NFS is a comprehensive software package designed to provide complete UNIX environment integration into a Windows NT, Windows 2000, Windows Storage Server 2003, or Active Directory domain file server. Services for NFS manages tasks on both Windows and UNIX platforms. Tasks include creating NFS exports from Windows and administering user name mappings. The following Services for NFS components are included in the NAS server: ■ Server for NFS ■ User Name Mapping ■ NFS Authentication Note: Services for NFS can be implemented in both clustered and non-clustered environments. This chapter discusses Services for NFS in a non-clustered deployment. For additional information that is specific to a cluster, see the Cluster Administration chapter. Server for NFS Services for NFS enables UNIX clients to access a file share on the NAS server. The Services for NFS server supports NFS Version 2 and Version 3, and supports them both on the TCP and UDP network protocols. Services for NFS is more fully integrated into the operating system than other third-party NFS server packages. The administrative interface for NFS exports is similar to the Server Message Block (SMB) sharing interface used by Windows platforms. With Server for NFS properly configured, the administrator can create shares that are simultaneously accessible by multiple client types. For example, some of the options for shares include configurations for CIFS/SMB sharing only, simultaneous NFS/CIFS/SMB sharing, simultaneous NFS/CIFS/SMB/HTTP sharing, or simply NFS only sharing. Authenticating User Access NFS export access is granted or denied to clients based on client name or IP address. The server determines whether a specific client machine has access to an NFS export. No user logon to the NFS server takes place when a file system is exported by the NFS server. Permission to read or write to the export is granted to specific client machines. For example, if client machine M1 is granted access to an export but client M2 is not, user jdoe can access the export from M1 but not from M2. NAS 4000s and 9000s Administration Guide 157

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

157
NAS 4000s and 9000s Administration Guide
8
Microsoft Services for NFS
Microsoft Services for NFS is a comprehensive software package designed to provide
complete UNIX environment integration into a Windows NT, Windows 2000, Windows
Storage Server 2003, or Active Directory domain file server. Services for NFS manages tasks
on both Windows and UNIX platforms. Tasks include creating NFS exports from Windows
and administering user name mappings.
The following Services for NFS components are included in the NAS server:
Server for NFS
User Name Mapping
NFS Authentication
Note:
Services for NFS can be implemented in both clustered and non-clustered environments. This
chapter discusses Services for NFS in a non-clustered deployment. For additional information that is
specific to a cluster, see the Cluster Administration chapter.
Server for NFS
Services for NFS enables UNIX clients to access a file share on the NAS server. The Services
for NFS server supports NFS Version 2 and Version 3, and supports them both on the TCP and
UDP network protocols.
Services for NFS is more fully integrated into the operating system than other third-party NFS
server packages. The administrative interface for NFS exports is similar to the Server Message
Block (SMB) sharing interface used by Windows platforms. With Server for NFS properly
configured, the administrator can create shares that are simultaneously accessible by multiple
client types. For example, some of the options for shares include configurations for CIFS/SMB
sharing only, simultaneous NFS/CIFS/SMB sharing, simultaneous NFS/CIFS/SMB/HTTP
sharing, or simply NFS only sharing.
Authenticating User Access
NFS export access is granted or denied to clients based on client name or IP address. The
server determines whether a specific client machine has access to an NFS export. No user
logon to the NFS server takes place when a file system is exported by the NFS server.
Permission to read or write to the export is granted to specific client machines. For example, if
client machine M1 is granted access to an export but client M2 is not, user jdoe can access the
export from M1 but not from M2.