can you be more specific about your problem?

Well am not so good in linux but after seeing your configuration file OK if you try uncommenting the OS level and then increase it value up to at least 256 i think your problem will be solved. Sorry for any inconvience

Cheers Fofana

Hey in addition to what i said earlier that's uncommenting the OS level and using a value of at most 255, you also need to uncomment both the local master and preferred master and assign them yes. Uncomment security and assign it "share" instead of "user"

You can holla me at dute105@gmail.com

Dute105

This work but I need the local and preferred browser because my server is running like PDC

thanks for your help

In that case i guess you might need another box. From experience i think what you need is only possible with an NT box that's being both PDC and local browser

I don't know if this is relevant or not but this Samba thread from Bugzilla might proove informative;

bugzilla.redhat.com bugzilla show_bug.cgi?id=133478

I was totally wrong about this bit - the replies don't come in on UDP port 137, but on a random high numbered port. Alex's ip_conntrack tracks outgoing packets on UDP port 137 and allows replies to them on high numbered ports within a timeout.

So, without Alex's module, you can't get SMB browsing to work on the client just by opening UDP 137 - you need to totally disable the firewall.

That bug doesn't appear to be relevant to his issue, some guy with a similiar problem just tried to hijack it. Aside from the attempted hijacking, you don't need to open high ports to get SMB replies, the default ip_contrack module for netfilter figures out that replies with source port 137 fall under the "established,related" catagory even if they come back on a high port.

Your issue appears to be with the way that Nautilus handles $IPC connections. To verify that, try this. Say you have a machine called XPBOX with a share called SHARE, try to open the share directly as smb:\\XPBOX\SHARE in Nautilus and see if it works. If that works but trying to get a list of shares on the same computer does not, you are probably dealing with an $IPC connection problem.

As for the OS Level, Local Master, Preferred Master, and Security settings in your smb.conf, I would not suggest changing them from what they were before. If you can actually see the other computers in the Nautilus browser, even if you can't see their list of shares, these settings aren't broken. You could also break your network browsing if there is an existing domain controller on the network or if the linux box isn't always booted up by tweaking these settings.

The only thing I see in your smb.conf that could be causing the problem is this section:
which you could just comment out:
unless it was configured that way by you or an administrator to connect to your windows network.