Adaptec 5325301656 Administration Guide - Page 42

Connecting from a Windows Client, Interoperability with Active Directory Authentication

Page 42 highlights

Windows Networking Configuration the Kerberos key distribution center (KDC), and the origin of group policies that are applied to the domain. Notes Kerberos requires the server's time to be closely synchronized to the domain controller's time. This means that (1) the server automatically synchronizes its time to the domain controller's and (2) NTP cannot be enabled when joined to an ADS domain. Interoperability with Active Directory Authentication The Snap Server supports the Microsoft Windows 2000/2003 family of servers that run in native ADS mode or in mixed NT/ADS mode. Snap Servers can join Active Directory domains as member servers. References to the Snap Server's shares can be added to organizational units (OU) as shared folder objects. Guest Account Access to the Snap Server The Security > Local Users screen contains an option that allows unknown users to access the Snap Server using the guest account. Restrict_Anonymous and PDC Access If you have implemented the restrict_anonymous mechanism on your domain, you may need to enter a valid domain (not local) user name and password that the Snap Server can use to communicate with the PDC. For ease of administration, Adaptec recommends that you create a unique user account on the domain using the following guidelines: • Choose a name, such as SnapServerAccess, and include a comment that makes the function of the account clear. • Set the password to never expire. Note A restrict_anonymous user account does not require administrative access. Connecting from a Windows Client Windows clients can connect to the Snap Server using either the server name or IP address. To navigate to the server using Windows Explorer, use one of these procedures: • For Microsoft Windows Vista and 2008 Server clients, navigate to Network > server_name. • For Microsoft Windows 2003, 2000, Me, or XP clients, navigate to My Network Places > workgroup_name > server_name. • For Microsoft Windows 95, 98, or NT clients, navigate to Network Neighborhood > workgroup_name > server_name. 28 Snap Server Administrator Guide

  • 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

Windows Networking Configuration
28
Snap Server Administrator Guide
the Kerberos key distribution center (KDC), and the origin of group policies that are
applied to the domain.
Notes
Kerberos requires the server's time to be closely synchronized to the domain
controller’s time. This means that (1) the server automatically synchronizes its time
to the domain controller's and (2) NTP cannot be enabled when joined to an ADS
domain.
Interoperability with Active Directory Authentication
The Snap Server supports the Microsoft Windows 2000/2003 family of servers that
run in native ADS mode or in mixed NT/ADS mode. Snap Servers can join Active
Directory domains as member servers. References to the Snap Server's shares can be
added to organizational units (OU) as shared folder objects.
Guest Account Access to the Snap Server
The
Security > Local Users
screen contains an option that allows unknown users to
access the Snap Server using the guest account.
Restrict_Anonymous and PDC Access
If you have implemented the
restrict_anonymous
mechanism on your domain, you
may need to enter a valid domain (not local) user name and password that the Snap
Server can use to communicate with the PDC. For ease of administration, Adaptec
recommends that you create a unique user account on the domain using the
following guidelines:
Choose a name, such as
SnapServerAccess
, and include a comment that makes the
function of the account clear.
Set the password to never expire.
Note
A
restrict_anonymous
user account does not require administrative access.
Connecting from a Windows Client
Windows clients can connect to the Snap Server using either the server name or IP
address. To navigate to the server using Windows Explorer, use one of these
procedures:
For Microsoft Windows Vista and 2008 Server clients, navigate to
Network >
server_name
.
For Microsoft Windows 2003, 2000, Me, or XP clients, navigate to
My Network
Places >
workgroup_name > server_name
.
For Microsoft Windows 95, 98, or NT clients, navigate to
Network Neighborhood >
workgroup_name > server_name.