I have configure Samba and it functions as expected if I start it from a command line using the smbd command but does not behave when started as a service.<br />
<br />
The symptom from a Windows 7 client is "Windows can not access \\server\folder" even though it can display the shares available.<br />
<br />
When I stop the "service" and start smbd by typing "smbd" on the command line, all works as expected and all folder contents is exposed consistent with security settings.<br />
<br />
This is an especially strange problem since the configuration basically works as planned unless started using "service smb start". There is no obvious difference in the running processes. It also works normally if the smbd process is launched from cron via at or crontab.<br />
<br />
There is something different in the process environment when started via service that I can not identify.<br />
<br />
I can not understand what is different in the 2 environments.
↧