Topic: Samba does not start up in SME5

[Rick]

Here's the situation:

I upgraded e-smith 4.1.2. to SME5. The server acts as a PDC. Since the upgrade Samba does not start anymore. I tried the startupscript in /etc/rc.d/init.d/smb but nothing happens when I do that.

Can anyone help?

[Greg Zartman]

You need to upgrade to samab 2.2.1a.  Have a look at this site.  www.myezserver.com in the howtos section for step by step instructions

Greg

[Dan Brown]

Had you upgraded your samba to 2.2.1a under 4.1.2?  If so, it's possible that some of the directives in your smb.conf file are breaking things.  In my case, redoing the 2.2.1a upgrade seemed to fix this problem.

[Blake]

I had upgraded to 2.2.1a under 4.1.2 and when I upgraded to 5.0 it broke my Samba.  I tried to redo the 2.2.1a install as Dan Brown suggests and it failed telling me that a number of files conflicted with a number of files already on the system.  Do I need to uninstall Samba completely before reapplying the 2.2.1a upgrade.  Also, there are two versions of Dan's How-to.  Which should be used?

Thanks

[Dan Brown]

Well, you should probably use the RPMs from the second howto, as they're RedHat-supplied, and are more likely to work.  It will give conflicts with initscripts and libreadline; these are bogus and can be ignored (by using --nodeps).  However, the add user script from that howto doesn't seem to work.  I think I know why it doesn't, but I'm not yet sure what to do to make it work.

[Rick]

Before the upgrade to SME5 I installed Samba 2.2 Apperantly the upgrade to V5 broke Samba. I installed Samba 2.2 again and it works now.

[Blake]

Thanks to Dan I got Samba reinstalled using the second How-To.  All of my win 98 machines now authenticate to the domain just fine but my Win 2K machines don't.  I they come up in the same workgroup but I can't see any of the Win98 machines.  All of the Win 98 machines can see each other but not the Win 2K machines.  The Win2K machines can't see the server in Network Neighborhood either but the 98 machines can.

The Win2k machines keep telling me the domain doesn't exist when I try and set the identification properties for the machines.

Hmmmmm.

Thanks again Dan for the great How-to.

Blake