making Samba work
Bill West
bill at westsolutions.net
Tue Aug 2 19:36:05 UTC 2005
I had a similar problem and the culprit was SELinux policy. If SELinux
is running on your box, check the Samba section. I think by default
Samba is disabled.
Bill
Claude Jones wrote:
>Samba is driving me crazy:
>My scenario:
>Linux box connected to the net, firewalled with FWBuilder
>Firewall blocks all connections to the box by default
>Lan consists of four Windows machines - traffic from the Lan through the
>firewall to the net is permitted, and replies to requests from the Lan from
>the net are permitted.
>
>I've opened up ports for Samba to the lan;
>
>
>>>137 tcp/udp
>>>138 tcp/udp
>>>139 tcp
>>>445 tcp/udp
>>>
>>>
>
>My smb.conf
>[global]
> netbios name = viewridgeproductions2
> ldap ssl = No
> restrict anonymous = no
> server string = Samba
> max protocol = NT
> workgroup = WORKGROUP
> os level = 20
> server signing = Auto
> interfaces = 192.168.2.1
> domain master = no
> security = share
> preferred master = no
> bind interfaces only = yes
>
>[CJ home]
>case sensitive = no
>guest ok = yes
>msdfs proxy = no
>read only = no
>path = /home/cj
>
>smbd and nmbd are running and set to run at startup
>
>I've also configured the LISa protocol and it, too is running
>
>This is my current configuration, but I've tried many different things along
>this journey - I'm sure I've overlooked something obvious, or screwed
>something else up, but I can't for the life of figure out what. I"ve tried a
>half dozen internet HOWTO's on the subject, and I've even printed out the
>1100+ page Samba manual from their website.
>
>I can't see my Windows machines from the Linux box at all. One Windows machine
>sees the Fedora box, but can't access it - just get a 'denied' message.
>Windows boxes are properly configured and networking with each other just
>fine.
>
>To paraphrase another ongoing thread: "Help, I need a sherpa!"
>
>
--
Don't take Life too seriously, you will never get out alive - Van Wilder
More information about the fedora-list
mailing list