HP AiO400r HP StorageWorks All-in-One Storage System User Guide (440583-006, J - Page 176

Installing NFS Authentication DLL on domain controllers, and R2 MSNFS.

Page 176 highlights

Refer to Table 51 for guidance as to when to use NFS Authentication DLL instead of S4U legacy NFS and R2 MSNFS. Table 51 Authentication table Domain controller type Legacy NFS (pre-WSS2003 R2) MSNFS (WSS2003 R2) Legacy domain controller (pre-WSS2003) Recent domain controllers (WSS2003 and later) Requires NFS Authentication DLL on domain controller Requires NFS Authentication DLL on domain controller Requires NFS Authentication DLL on domain controller Uses the built-in S4U (on the domain controller). It is unaffected by the NFS Authentication DLL on the domain controller. The S4U set of extensions to the Kerberos protocol consists of the Service-for-User-to-Proxy (S4U2Proxy) extension and the Service-for-User-to-Self (S4U2Self) extension. For more information about the S4U2 extensions, see the Kerberos articles at the following URLs: http:// searchwindowssecurity.techtarget.com/originalContent/0,289142,sid45_gci1013484,00.html (intended for IT professionals) and http://msdn.microsoft.com/msdnmag/issues/03/04/SecurityBriefs/ default.aspx (intended for developers). Installing NFS Authentication DLL on domain controllers NOTE: If the authentication software is not installed on all domain controllers that have user name mappings, including primary domain controllers, backup domain controllers, and Active Directory domains, then domain user name mappings will not work correctly. You need to install the version of NFS Authentication included with Services for UNIX 3.5. You can download Services for UNIX 3.5 at no charge from http://go.microsoft.com/fwlink/?LinkId=44501. To install the Authentication software on the domain controllers: 1. From the SFU 3.5 files, locate the directory named SFU35SEL_EN. 2. On the domain controller where the Authentication software is being installed use Windows Explorer to: a. Open the shared directory containing setup.exe. b. Double-click the file to open it. Windows Installer is opened. NOTE: If the domain controller used does not have Windows Installer installed, locate the file InstMSI.exe on the SFU 3.5 directory and run it. After this installation, the Windows Installer program starts when opening setup.exe. 3. In the Microsoft Windows Services for UNIX Setup Wizard dialog box, click Next. 4. In the User name box, enter your name. If the name of your organization does not appear in the Organization box, enter the name of your organization there. 176 Microsoft Services for Network File System (MSNFS)

  • 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

Refer to
Table 51
for guidance as to when to use NFS Authentication DLL instead of S4U legacy NFS
and R2 MSNFS.
Table 51 Authentication table
MSNFS (WSS2003 R2)
Legacy NFS (pre-WSS2003 R2)
Domain controller type
Requires NFS Authentication DLL on
domain controller
Requires NFS Authentication DLL
on domain controller
Legacy domain controller
(pre-WSS2003)
Uses the built-in S4U (on the domain
controller). It is unaffected by the NFS
Authentication DLL on the domain
controller.
Requires NFS Authentication DLL
on domain controller
Recent domain controllers
(WSS2003 and later)
The S4U set of extensions to the Kerberos protocol consists of the Service-for-User-to-Proxy (S4U2Proxy)
extension and the Service-for-User-to-Self (S4U2Self) extension. For more information about the S4U2
extensions, see the Kerberos articles at the following URLs:
h
t
tp://
s
ear
c
h
w
indo
w
s
s
ec
ur
it
y
.t
ec
h
t
ar
ge
t
.co
m/o
r
i
ginalC
o
n
t
e
n
t/0,2
8
914
2
,si
d4
5_gc
i1013
4
8
4
,
00.h
tml
(intended for IT professionals) and
h
t
tp://msdn
.mi
c
r
o
s
o
f
t
.co
m/msdnmag/is
sue
s/0
3/0
4/S
ec
ur
it
yBr
i
e
f
s/
de
f
a
ult
.a
s
p
x
(intended for developers).
Installing NFS Authentication DLL on domain controllers
NOTE:
If the authentication software is not installed on all domain controllers that have user name mappings,
including primary domain controllers, backup domain controllers, and Active Directory domains, then
domain user name mappings will not work correctly.
You need to install the version of NFS Authentication included with Services for UNIX 3.5. You can download
Services for UNIX 3.5 at no charge from
h
t
tp://g
o
.mi
c
r
o
s
o
ft
.co
m/f
w
link/?L
inkId=4
4
5
01
.
To install the Authentication software on the domain controllers:
1.
From the SFU 3.5 files, locate the directory named
SFU35SEL_EN
.
2.
On the domain controller where the Authentication software is being installed use Windows
Explorer to:
a.
Open the shared directory containing
setup.exe
.
b.
Double-click the file to open it. Windows Installer is opened.
NOTE:
If the domain controller used does not have Windows Installer installed, locate the file
InstMSI.exe
on the SFU 3.5 directory and run it. After this installation, the Windows
Installer program starts when opening
setup.exe
.
3.
In the Microsoft Windows Services for UNIX Setup Wizard dialog box, click
Next
.
4.
In the User name box, enter your name. If the name of your organization does not appear in the
Organization box, enter the name of your organization there.
Microsoft Services for Network File System (MSNFS)
176