Doug,
Has anything changed on your DCs?
When we had a similar sounding issue it took us about a month to connect that
a) a Windows domain controller had its IP address changed with b) the old IP
address was still lurking in DNS that was managed by the DC. Once the obsolete
addressing was
Hi Rama,
Assuming that your 3.0.28 is the Solaris-provided Samba, install the various
Samba patches per the Oracle site. This error is well known and is resolved in
Samba 3.5 and onward in the 3. series. All that was easy for me to say. I can
also appreciate that you are now under the gun to
Perhaps it's already there from the domain join for the first server.
This is supported by the identity of the smb.conf files.
Andy Colb
ICI
-Original Message-
From: samba-boun...@lists.samba.org
[mailto:samba-boun...@lists.samba.org] On Behalf Of Seldon, Adrian (ES)
Sent: Wednesday,
If the credentials are managed by AD and the Samba share remained joined
to the domain throughout the Solaris reinstall/upgrade process, a good
start is to kill smbd, take the Samba server out of the AD domain (new
to Samba 3.5.5 is net leave command; or delete the Samba server entry
directly
Comm command is ideal; it was built for this type of text processing
problem. It requires sorted (collated) input lists.
cut -d: -f1 /etc/passwd | sort pass_f1 # provide sorted list of the
first field in the passwd file
cut -d: -f1 /etc/samba/smbpasswd | sort smbpass_f1 # provide sorted
