The problem is SE Linux.
I finally found the solution to this problem on Google by adding more search terms http://readlist.com/lists/redhat.com/fedora-list/14/73268.html
This two services was working OK before my update from FC3
I think that it was having something to do with SE, because to solution this I had to turn off SE, reboot, then turn on SE & reboot again, this (I think) relabeled the entire file system & after this; no more problems with the smb & ppp0 services getting working ok.
I booted after turning off SE, and it works - after many frustrating hours of looking for the problem in Samba.
Dan Martin wrote:
I have been playing with Samba 3 on FC4 for over 3 days now, and it's starting to get not fun.
Samba appears to be up and running and the network is functional. When I browse the network on my Windows machines (one is Win 2000 pro the other is NT4) I am prompted for a username/password, then the server shows on the network. I can open its folder, and I can browse a tmp share inside (path /tmp) subject to the permissions of the subfolders.
When I try to access the home folder named "user" I get the error \Linuxserver\user is not accessible. The network name cannot be found.
It appears that authentication is working, as I can login at the prompt, and the subfolder representing the home directory is named after the user. Permissions under Linux should not be an issue, since I have granted universal access to /home and all subdirectories. If I try to browse folders that I do not have access to, I get a different error - access denied.
Since the default mapping of the [homes] share did not seem to work, I have even tried setting the smb.conf parameter path=/home/%S to no avail.
I have tried numerous other things, and a Google search turned up dozens of dead ends.
Does anyone have ideas re
- the above problem
- how to 'flush the cache' so that I don't have to log on and off on
Windows every time I try a change in Samba 3) how to determine on the Linux machine which windows user is accessing from the network so I can confirm authentication is correct (like a 'who' command for Samba)