Fwd: [Samba] RHEL4 and samba
phwashington at comcast.net
Wed Dec 14 21:42:39 GMT 2005
> Begin forwarded message:
>> From: Margaret_Doll <Margaret_Doll at brown.edu>
>> Date: Wed Dec 14, 2005 1:09:24 PM US/Eastern
>> To: samba <samba at lists.samba.org>
>> Subject: [Samba] RHEL4 and samba
>> I brought over the /etc/samba directory from a RHEL3 system to a
>> RHEL4 system.
>> I disable selinux in case there was a problem with a port being blocked
>> iptables has port 139 and 445 enabled.
open ports 137 and 138, I forget which one, but the announcement
is on one of these ports, you also need to check your protocols tcp udp
as far as iptables is concerned.
Usually in this cases I open up all protocols and the ports
needed(check the protocols udp and tcp on 139 445 also) and then start
DROP ing or REJECT ing ports-protocols until it breaks.
selinux should not be an issue with this.
>> I can see the server in the Windows Network Neighborhood but the user
>> cannot connect because they are unauthorized to attach from their
>> Most of the test in the samba documentation work except.
>> smbclient -L server -N
>> shows no computers, but does show the shares and
>> SERVER COMMENTS
>> myserver server comments
>> Workgroup Master
>> 2nd workgroup master2
>> 3rd workgroup master3
>> nmblookup -B myserver __SAMBA__
>> querying __SAMBA__ on correct ip address
>> name_query failed to find name __SAMBA__
>> nmblooup -M myworkgroup
>> querying myworkgroup on mysubnet
>> ip address of a client myworkgroup<1d>
>> "netstat -a" show netbios-ns
>> What do I have set up incorrectly?
> I found that from the computers I cannot attach to the server through
> the network neighborhood. I can, however, log into the server
> if I do a search on the computer. So the server is not "announcing"
> How do I fix this problem? Is this a firewall problem?
More information about the samba