[SOLVED] Help please with strange Samba problem

[broadstairs]

I am running F17 and use SMB4K and Samba to share stuff on my local Lan with Windows PCs.

When I boot up SMB4K cannot find this F17 install unless I restart nmb which is running on boot. As soon as that is done this F17 system shows up in the correct place, however I cannot then access the system to display the shares unless I go into the Samba admin app and setup the Samba users password again, note I do not change it simply retype it and save, then restart smb and all is OK I can see all the shares on this F17 system from both this system and the Windows systems on the lan and this without changing the password already saved in SMB4K.

Next time I boot this F17 PC I have to go through all this again to be able to share stuff.

Can anyone suggest why this is? For a start restarting nmb on its own is strange, then why on earth is Samba not saving the password correctly? Note I am not running the Samba 4 beta, this is the latest Samba 3.

Stuart

[psihokiller4]

hi I just installed my first fedora on my PC today
and managed to access to windows 7

I followed this procedure
http://www.youtube.com/watch?v=JqBPR9MPtTs

not everything work as I'm using fedora 17 and he uses older version but the thing is it worked

[broadstairs]

I should point out that both firewall and selinux are turned off for now.

Stuart

[broadstairs]

I have done some more investigation on this. From further testing it wold seem that nmb does indeed start and fail or at least has done on the past couple of boots. Searching around I found a thread which suggests this happens with SELinux disabled (which I have) but doing

systemctl isolate runlevel1.target
systemctl isolate runlevel5.target
reboot

seems to solve the issue of nmb failing on boot, and so far this seems to have solved this part of the problem (time will tell if it is a permanent fix).

So at present I am left with the password issue where I have to re-enter the samba user password and restart smb and all works fine. So can anyone suggest how to progress the password problem please?

Stuart

---------- Post added at 06:19 PM ---------- Previous post was at 09:47 AM ----------

Well so far after a couple more boots both smbd and nmbd are starting OK on boot. So that now looks fixed but does not explain why it needed to be done. Anyone any ideas?

Now the password problem looks sorted as well but again I know what I did which was to use smbpasswd command to change the password for the smb user but I dont understand why it now remembers the password. Setting it from the Samba gui control panel does not save it across a boot but using smbpasswd does! Explanations welcomed if anyone has any!

If this stays fixed for a couple of days I will mark the thread as solved.

Stuart

[broadstairs]

Well I spoke too soon about the password issue, this morning after booting the PC it prompted for the password again to scan the Fedora system. So there is a peculiar problem with passwords being remembered across re-boots.

Has anyone any ideas about this please?

Stuart

[broadstairs]

Well I have finally fixed this issue I believe. Eventually I found after much searching about NetworkManager-wait-online service which would prevent nmb and smb starting before the network was fully up, after enabling and starting this I have not had any more problems with nmb failing on boot and smb losing passwords.

So if you have similar issues please give that a try.

Stuart