Adaptec 5325301507 Administration Guide - Page 45

Windows Networking Configuration, Support for Windows Networking (SMB)

Page 45 highlights

Windows Networking Configuration Windows Networking Configuration Windows SMB and security settings are configured on the Network > Windows screen of the Administration Tool. Topics include: • Support for Windows Networking (SMB) • Support for Windows Network Authentication Support for Windows Networking (SMB) The default settings make the SnapServer available to SMB clients in the workgroup named Workgroup. Language support is set to North America/Europe (code page 850); opportunistic locking is enabled, as is participation in master browser elections. See the online help for details in configuring these options. Consider the following when configuring access for your Windows networking clients. Windows Networking File and Folder Name Support In Windows networking, most file and directory names are transmitted as a 2-byte (16-bit) UCS-2 character set. However, this is not true in every case. Some are still sent via a single byte character set. The Language Support option selected for Windows networking clients is used only to enable the server to accept file and folder names in a single byte character set. Caution When Unicode is disabled, do not name files and folders in character sets not included in this list (e.g., Cyrillic). Such files and folders may be impossible to open or delete. Support for Microsoft Name Resolution Servers The SnapServer supports both of the Microsoft name resolution services: Windows Internet Naming Service (WINS) and Dynamic Domain Name System (DDNS). However, when you use a domain name server with a Windows Active Directory (ADS) server, make sure the forward and reverse name lookup is correctly set up. ADS can use a UNIX BIND server for DNS as well. ShareName$ Support GuardianOS supports appending the dollar-sign character ($) to the name of a share in order to hide the share from SMB clients accessing the SnapServer. Note As with Windows servers, shares ending in '$' are not truly hidden, but rather are filtered out by the Windows client. As a result, some clients and protocols can Chapter 2 Network Access to the Server 29

  • 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
  • 247
  • 248
  • 249
  • 250

Windows Networking Configuration
Chapter 2
Network Access to the Server
29
Windows Networking Configuration
Windows SMB and security settings are configured on the
Network > Windows
screen of the Administration Tool.
Topics include:
Support for Windows Networking (SMB)
Support for Windows Network Authentication
Support for Windows Networking (SMB)
The default settings make the SnapServer available to SMB clients in the workgroup
named
Workgroup
. Language support is set to North America/Europe (code page
850); opportunistic locking is enabled, as is participation in master browser
elections. See the online help for details in configuring these options.
Consider the following when configuring access for your Windows networking
clients.
Windows Networking File and Folder Name Support
In Windows networking, most file and directory names are transmitted as a 2-byte
(16-bit) UCS-2 character set. However, this is not true in every case. Some are still
sent via a single byte character set. The Language Support option selected for
Windows networking clients is used only to enable the server to accept file and
folder names in a single byte character set.
Caution
When Unicode is disabled, do not name files and folders in character sets
not included in this list (e.g., Cyrillic). Such files and folders may be impossible to
open or delete.
Support for Microsoft Name Resolution Servers
The SnapServer supports both of the Microsoft name resolution services: Windows
Internet Naming Service (WINS) and Dynamic Domain Name System (DDNS).
However, when you use a domain name server with a Windows Active Directory
(ADS) server, make sure the forward and reverse name lookup is correctly set up.
ADS can use a UNIX BIND server for DNS as well.
ShareName$ Support
GuardianOS supports appending the dollar-sign character ($) to the name of a share
in order to hide the share from SMB clients accessing the SnapServer.
Note
As with Windows servers, shares ending in '$' are not truly hidden, but rather
are filtered out by the Windows client. As a result, some clients and protocols can