Steve, On Sat, Jun 13, 2015 at 05:02:12PM -0400, Steve Ankeny wrote: > The suggestion above was to "create a blank smb.conf in /etc/samba, then > purge and reinstall samba" > During the upgrade, it suggested I keep my current 'smb.conf' I currently > have the 'dcerpc' lines commented. Perhaps, I should uncomment those since > they call the OpenChange and 'mapiproxy' functions? > I inserted the 'dcerpc' comments as I was unable to login after a reboot > of my 'samba-ad-dc,' and the problem was perceived to be the calls to a > 'broken' OpenChange (which applies to OpenChange before this upgrade) > Using a blank 'smb.conf' might not find my domain parameters to complete > the configuration. > If I purge my 'samba' db, will it delete all my user and machine accounts? > That's a worry! > Another suggestion might be to install an upgrade between my current > 'samba' file and the Inverse package. I've been concerned about the > installed version since before starting this upgrade to Samba 4.1.18 > Are there any suggestions? Has anyone else ran into this situation? > Should I ask the Samba list?
If this is a fresh install of a machine and this is happening then it all depends on where your apt sources point to. Check if you have standard apt-sources or more specific ones. If there's data you don't want to mess with, sping up a Digital Ocean droplet for a few hours ($0.50) and test it and see what's different. https://grmbl.net/digitalocean B -- [email protected] https://inverse.ca/sogo/lists
