?
Dave
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Lemire, David
> Sent: Wednesday, March 19, 2008 3:01 PM
> To: samba@lists.samba.org
> Subject: Re: [Samba] CentOS 5 client in W2K3 AD Domain,
> getent on
I decided to start over on my configuration, and this time I used the
GUI tools available in CentOS for configuring Samba, Winbind, etc. As a
result I've made considerable progress. I can:
- login using network credentials authenticated
by the domain controller
- automatically generate hom
netmasks: files
networks: files
protocols: files
rpc:files
services: files
netgroup: files
publickey: nisplus
automount: files
aliases:files nisplus
= nsswitch.conf (end)
-Original Message-
From: [EMAIL PROTECTED] on behalf of Lemire, David
Se
ES or HAVE_LDAP_DOMAIN2HOSTLIST are showstoppers for me.
Dave
Lemire, David wrote:
Try comparing what you did to these articles. They worked very well
for me on a W2K AD domain.
To me, they're more easily understood than the official docs.
http://www.enterprisenetworkingplanet.com/netos/a
shouldn't just one or more pieces of this puzzle (starting
w/samba).
I need to double-check my samba build include the DOMAIN2HOSTLIST
component; I can't check at the moment, but IIRC, that might not have
been in the list when I checked before. Would missing that account for
my wi
I'm trying to integrate a Linux machine into our
Win2K3 ADS-based network. The machine must
primarily serve as a user workstation (i.e., a
Samba Client), although it also needs to serve at
least one share for backup purposes. I'd like to
emulate the behavior of our WinXP machines in that
any user
