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
Summary of Contents for 5325301507 - Snap Server 4400 NAS
Page 2: ......
Page 12: ...xii SnapServer Administrator Guide ...
Page 16: ...xvi SnapServer Administrator Guide ...
Page 58: ...Print Server 42 SnapServer Administrator Guide ...
Page 64: ...NIS Domain 48 SnapServer Administrator Guide ...
Page 110: ...Configuring VSS VDS for iSCSI Disks 94 SnapServer Administrator Guide ...
Page 154: ...Log View 138 SnapServer Administrator Guide ...
Page 228: ...Phone Home Support 212 SnapServer Administrator Guide ...