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 machi
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
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
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
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 W
