Noob Centos Admin wrote:
> I was back onsite and trying it again, in vain. Copied the conf from
> another site's working setup and dumped directly, recreated with the
> same names and all. No go.
>
> So again removed and install samba again, made a blank conf file, fire
> up SWAT and did the most basic config.
>
> Even chmod 777 the directory.
>
> Conf file
> [global]
> workgroup = MKSC52
> netbios name = MKSC52
> security = SHARE
> log level = 2
> os level = 35
>
> [staff]
> comment = Staff Share
> path = /home/staff
> valid users = jackie @staff
>
>
> I've changed one of the Windows machine workgroup to a fresh one as
> above, in case the existing WIndows 2000 domain controller was somehow
> interfering. The pc name was also changed to the user's name. But no
> joy either.
>
> But at least Samba is logging something after that
>
> # [2009/03/06 17:38:31, 2] smbd/reply.c:reply_special(324)
> netbios connect: name1=MKS2009C52 name2=JACKIE
>
> [2009/03/06 17:38:31, 2] smbd/reply.c:reply_special(331)
> netbios connect: local=mks2009c52 remote=jackie, name type = 0
>
> [2009/03/06 17:40:31, 2] smbd/process.c:timeout_processing(1363)
> Closing idle connection
>
> On the windows side, there was a brief pause before Windows tells me I
> have no permission to access the network resource. No prompt for
> password.
Try adding
guest ok = no
in the global section. If security = share doesn't work like it used
to, you may be required to authenticate before seeing the shares and if
guest is permitted you can be silently mapped to a user with no
permissions. All linux permissions continue to apply, all the way down
the path, so you must be able to log into linux as the user (or su to)
and access the directory/files. Then you need to make sure samba
connects as the correct user.
--
Les Mikesell
lesmikesell at gmail.com