On 4/11/11 2:47 PM, John Andersen wrote:

On 4/11/2011 11:51 AM, Jim Flanagan wrote:

...

I think this is a different issue than the Samba/AppArmour one. My desktop fails to find any Samba shares on the local network. I open My Computer>Network Folders>SMB>"workgroup"> the system looks but times out finding any shares. It sees the workgroup, but no shares under that. If I type smb://"computername" it will show the share. It just can't seem to show them by browsing. All other computers on the local LAN find the shares with no problems, including the share on the 11.4 install which can't find them. This happens on both a 32 bit and a 64 bit install. An older opensuse 11.0 install shows them all, as does my macbook, as does Windows 7.

Basic clean install (both 32bit and 64 bit) KDE. (AppArmour is disabled in Yast).

Thanks for any assistance.

Jim F Try shutting off the susefirewall as a test. (not recommending you leave it off). Seeing shares on the network isn't really a samba function. (Samba provides shares).

By the way, it is not necessary to shut down AppArmor to get Samba working. You just need set up samba, fire it up, and then run the AppArmor update profile wizard. It will list things that Samba tried to access but which were blocked by apparmor. Use the right hand button on the bottom to ALLOW all of these, then finish.

Test samba again, rinse repeat a few times. Each test gets a little farther and accesses more control files. (Its sad apparmor doesn't have a proper profile for samba that gets installed right off the bat, but the wizard does a good job).

Finally samba will run. Then as your Virtual Machines or Network users try to access the samba shares they will get trapped by apparmor too.

Run the wizard again, and when you come across an entry that points to your data files use the glob button before using the Allow button.

For instance:

Assume you are using Samba to Share /data sub-directory. A user might try to access /data/documents/family/pictures/auntlucy.jpg You certainly don't want to create a Apparmor ALLOW rule for every friggin file. GLOB will take off each node, (One node for each press), so that you end up after 4 presses of Glob with just /data. Then press Allow, and bob is your brothers uncle.

There is no reason to shut down apparmor totally. Keep it running and use the wizard to teach it what is allowed.

I have the firewall off too. Other machines on the network can see the shares, but this box is having problems seeing smb shares, including its own. Funny thing though. Just this morning I decided to try opening Konqueror thru its own launch icon, not by My Computer. I typed in smb://workgroup, and it did show the shares! So I closed Konq, then opened My Computer>Network Folders>SMB, and it also showed the shares. Can't figure that. I've been opening it this way for 2 weeks and this is the first time it didn't time out trying to find/show shares. The only thing that has changed on the network is one computer is currently powered off. No other changes. ??? Will try it again this evening to see if its still working. Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 04/12/2011 01:58 PM, John Andersen wrote:

...

The only thing that has changed on the network is one computer is currently powered off. No other changes. You might want to figure out which computer is the browse master on your network. Sometimes SAMBA (nmdb portion) dies or becomes confused. This is especially true for

On 4/12/2011 11:44 AM, Jim Flanagan wrote: those machines running on wifi, or switching from wifi to wired connections. Then its hard to find shares. Sometimes a horribly out of date windows machine becomes browse master and you end up having to reboot lots of computers till you find out which one it was.

I always find pick a linux machine that is going to be on all the time (my server) and which will never go into power saving mode. In that machine I set OS LEVEL = 65 in /etc/samba/smb.conf. This makes it win all browser elections. From then on its very reliable.

I've ofter wondered about that. The way a certain machine decides to be browser master seems pretty nebulous. Great tip, thanks. Do I need to find out which one is currently browser master, or just set my linux server, and the old current master which ever one that is will relinquish? Thanks for the advice on AppArmour by the way. I've not felt the need to run that before, small home network. But I do beleive in having additional layers of security where possible. After I get things stabilized here I'll turn it back on and give it a try. Best, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org