At 09:22 PM 12/17/2005, you wrote:
Brinkley Harrell wrote:
At 07:14 PM 12/17/2005, you wrote:
First of all, the Samba access does not care
what file system is on the other end. It can
access FAT, VFAT, NTFS, etc. and you see the file system.
It seems that Samba does not access the file
system on the attaching client, whatever the
filesystem (Samba being the server, not the
client). So yes, it does stand to reason that
Samba doesn't care about the client's filesystem.
You've kinda answered your own question here.
Samba translates whatever file system is
presented on the server to a CIFS system to
transport over the net. If you let the user read
and write, Samba handles the host's file system for the guest client.
In common terms, it is called a Common Internet
File System (CIFS). CIFS is an enhanced version
of Microsoft's open, cross-platform Server
Message Block (SMB) protocol, the native
file-sharing protocol in the Windows 95,
Windows NT®, and OS/2 operating systems and the
standard way that millions of PC users share
files across corporate intranets. CIFS is also
widely available on Unix, VMS, and other platforms.
That doesn't quite fully address my question
regarding XP being able to authenticate to an NT domain. See below.
It wasn't intended to answer the domain question
that you never asked. What you asked was if "Can
XP Home authenticate to Samba?". And, in fact, it
does this quite well. Depending on your
samba.conf, you may read it with or without
password. The machine does not have to be part of any domain to do this.
That said, the Mac OS-X platform has no problem
using the CIFS shares on Microsoft Windows
platforms. Of course, the newer versions such
as Tiger (10.4) have the most up-to-date
versions of the software. I have no problem
accessing Linux, Windows XP, or Windows 2003 shares from my iBook.
That may answer the Mac question, but I need
some clarification. Can the Mac read and write
to a native NTFS filesystem running on a Windows 2000, or XP Home system?
See above description on how Samba writes to a FS.
If XP Home authenticates to other XP boxes, it
can authenticate to a Samba share on a Linux box.
Windows XP Home can NOT access an NT domain
server, regardless of the Windows Server's
filesystem. Micro$oft purposely crippled XP Home
this way; they expect that if you need to attach
to an NT domain, you will buy XP Pro.
Are you saying that XP Home *can* access a Samba
server /acting as a Windows NT domain server/?
If so, then Samba is the obvious (and least
expensive) solution for this network.
1. Windows XP Home can access the Samba server.
2. Samba server does not have to act as a DC.
3. Samba can replace the PDC functions of NT.
4. Still won't help XP Home.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Brinkley Harrell
http://www.fusemeister.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
