Filter
Top Products
ApplianceWare v.5.3 Complete FAQ – February 24, 2004 – Page 25 of 30
Optifacio Software Services, Inc.
1.5.2.8 I cannot connect to a share over Samba or Windows networking although I can
see its name on the list. Why that happens?
There can be several reasons for that. For example, you cannot connect to a non-public share
without appropriate access rights. In this case, you should set up them using ApplianceView client
software.
This may also be due to the fact that Windows 95, 98, and Millennium Edition (Me), as well
as smbclient version prior to 3.0, are not able to display share names longer than 12 characters.
That is why you should use either Windows NT4.0, 2000, XP, 2003-based client machines, or
ApplianceView client software in order to learn exact share path and name, and then type this name
into the Explorer window (on Windows) or smbmount command line (on Linux).
1.5.2.9 I would like to connect to an Appliance share over AFP protocol but using
domain user name since this user owns a share. Is this possible?
You can do that. But you should use a mixed\ prefix before user name, e.g. mixed\user1 for
connection.
1.5.2.10 ApplianceWare-enabled server is actually Linux-based appliance. Is there any
mapping between POSIX and Windows Access Control Lists (ACLs)?
Answer on this question is based on an excerpt from the following document:
http://www.suse.de/~agruen/acl/linux-acls/online/
Microsoft Windows supports ACLs on its NTFS file system, and in its Common Internet File
System (CIFS) protocol, which formerly has been known as the Server Message Block (SMB)
protocol. CIFS is used to offer file and print services over a network. Samba is an Open Source
implementation of CIFS. It is used to offer UNIX file and print services to Windows users. Samba
allows POSIX ACLs to be manipulated from Windows. This feature adds a new quality of
interoperability between UNIX and Windows.
The ACL model of Windows differs from the POSIX ACL model in a number of ways, so it