[Samba] From LDAP to tdbsam

2011-02-03 Thread Michael Urban
We are scaling back our Samba service, and no longer need the
server to act as a domain controller or do general LDAP authentication.
Since we are also going to move the service to a different piece
of hardware, I would like to simplify the setup by removing
LDAP from the operation on the new machine.

The only problem I see will be the existing user base.  Is there
an easy way to move the lm and nt hashes from the LDAP database to
a passdb.tdb file?

Mike

[PS. Of course, if I am making a mistake here, and the LDAP setup has
some advantage that I am overlooking, let me know...]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Re: Migrating W2K Workstation to Samba Domain

2005-12-13 Thread Michael Urban
My message dated: Mon, 12 Dec 2005 10:16:14 EST
 I am replacing a W2K AD server with a Samba server.  The server has
 a single W2K Workstation client, in a public area and used by a dozen
 or so different users.  When I join the workstation to the Samba domain,
 it complains that it cannot load a roaming profile (in the W2K AD domain,
 it used local profiles), and it does not create a new local profile,
 instead using a temporary profile.
 
 Obviously a permission problem somewhere.  What is the exact problem,
 and what is the solution?


I am still at sea on this.  To clarify things a bit more, users of
this workstation (under the W2K server) have local profiles, not
floating profiles.  I would like to let them continue to have local
profiles, even if it proves impossible to let them use their old
ones due to permission problems.  However, even removing their
directories from C:\Documents and Settings does not help - Windows
does not create a new one for them (as all the documentation I have
read led me to believe it would).o

logon path=
logon home=

does not seem to affect this situation.  It still seems to try
to get a floating profile, fails, and then makes a local profile
in TEMP.

Hasn't anyone performed this sort of migration before?  What
other information can I provide (or try to glean from log files)
to get this sorted out?

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Migrating W2K Workstation to Samba Domain

2005-12-12 Thread Michael Urban
I am replacing a W2K AD server with a Samba server.  The server has
a single W2K Workstation client, in a public area and used by a dozen
or so different users.  When I join the workstation to the Samba domain,
it complains that it cannot load a roaming profile (in the W2K AD domain,
it used local profiles), and it does not create a new local profile,
instead using a temporary profile.

Obviously a permission problem somewhere.  What is the exact problem,
and what is the solution?

Mike
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Replacing a W2K Server?

2005-04-21 Thread Michael Urban
We have a Windows 2000 server with Terminal Services.  It is an Active
Directory master server for a microscopic network comprising itself and
one Windows 2000 Workstation client.  It is part of a network
consisting of Unix machines: several Solaris 8 systems, a handful of
Linux boxes, and a Mac OS X workstation.  User authentication and other
login information on this network is provided by NIS running on Solaris
- but see below.  Some of the Unix boxes are running Samba 3 to share
files to Windows workstations.

The services the W2K server provides are: file sharing to Windows
workstations (these live in a different Active Directory domain);
Windows applications for Unix users via Terminal Services and rdesktop;
and authentication for the Samba servers.  User NIS password changes
are reflected from the Unix systems to W2K using Microsoft's services
for Unix (in particular, MS provides a PAM module that sends password
changes to the W2K server), so using W2K for authentication allows
users to use their NIS passwords when connecting to Samba, rather than
some Samba-only password.

Our goal in life is to get rid of the W2K system.  We don't want to be
in the business of W2K server sysadmin, and the box running it is old
and takes up a lot of space and energy.  This would mean moving its
files to a new Samba server.

Is there a straightforward way to get the new server, as well as the
existing ones, to authenticate in such a way that its passwords
can be identical with the NIS/Unix passwords?  Does this require
some kind of Kerberos/LDAP infrastructure we do not now use?  How
would this be set up.  I have read several documents, but it seems to
me that:

1. Samba can authenticate with PAM, but this uses cleartext passwords.
2. Samba can authenticate from its own LDAP or file password database,
 but there is no obvious way to keep this synchronized with Unix passwords.
3. We could set up a Kerberos system, but I do not see any way of 
 making Samba refer to Kerberos for password authentication.

Any suggestions, please?

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Problem: Files becoming directories

2004-03-02 Thread Michael Urban

List:

I am encountering a problem with files on my samba mounted directories
accessed from Windows shares.  The shares are normally accessed from a
Windows 98 machine (but I've used XP, and the problem is still
present).   The problem: When accessing files from a samba-mounted
directory through Windows, some of the files become directories.  I
can create a text file named, say, test.txt.  At a later time, that text
file appears as a directory, named test.txt, in Windows Explorer.
Checking the file at the command line on the host system, the file has
actually become a directory...any data stored within that file is gone.
The problem is random, and checking the samba-related log files yields
no clues.

I have samba running on two different machines: 1) Red Hat 7.3, samba
version 2.2.8, and 2) HP-UX 10, samba version 2.2.3a, and the problem
appears on both machines.  Both machines connect to a Windows NT Server
(version 4, sp6a), and are using share level security.
Not sure if this is a samba-related problem, or a feature of Windows
(but I suspect the latter).

I have searched the mailing-list archives and have not found anything
similar to this problem.  Any clues on where to look would be
appreciated.

Thanks,
Mike
[EMAIL PROTECTED]

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba