Hello
I’m running opensuse 11 with GNOME …
My machine is connected wirelessly to a windows network. I have the samba packages installed on my machine, but when I navigate to smb:///, I can only go down one more level to “Windows Network.” None of the XP machines (with windows shared folders) appear. I seem to remember needing to log in (in KDE, a while back), but there doesn’t seem to be a way to do so in Nautilus. Is there some configuration (YaST, perhaps) that I have neglected?
Thanks
amontonarpapeles wrote:
>
> Hello
>
> I’m running opensuse 11 with GNOME …
>
> My machine is connected wirelessly to a windows network. I have the
> samba packages installed on my machine, but when I navigate to smb:///,
> I can only go down one more level to “Windows Network.” None of the XP
> machines (with windows shared folders) appear. I seem to remember
> needing to log in (in KDE, a while back), but there doesn’t seem to be a
> way to do so in Nautilus. Is there some configuration (YaST, perhaps)
> that I have neglected?
>
> Thanks
>
>
amontonarpapeles;
P. V.
“The entropy of a closed system can never decrease”, 2nd Law of Thermodynamics
Still nothing.
open a console and make a few checks – first su to get rootly powers
Check the firewall is running: rcSuSEfirewall2 status should return “running”
Check the firewall is open for Samba:
cat /etc/sysconfig/SuSEfirewall2 | grep FW_SERVICES_EXT_UDP="
should return: netbios-ns netbios-dgm
cat /etc/sysconfig/SuSEfirewall2 | grep FW_SERVICES_EXT_TCP="
should return: netbios-ssn microsoft-ds
cat /etc/sysconfig/SuSEfirewall2 | grep FW_SERVICES_ACCEPT_RELATED_EXT="
should return: 0/0,udp,137 or similar
Check the workgroup name is the same as windows:
cat /etc/samba/smb.conf | grep workgroup
should return the workgroup name to check against windows
Check you have entered your network name for SuseBox into the Samba configuration
cat /etc/samba/smb.conf | grep ‘netbios name =’
should return the name you chose for the computer on the network
#cat /etc/sysconfig/SuSEfirewall2 | grep FW_SERVICES_ACCEPT_RELATED_EXT=
FW_SERVICES_ACCEPT_RELATED_EXT=""
It doesn’t do what you say it should.
GoTo Yast –> Security and Users –> Firewall –> Broadcast –> Accepting the Broadcast reply –> add:
In the “Add” window, the settings are External Zone, Samba Browsing, and replace 0/0 by your network range. The network range is your IP address with the last integers replaced by “0/24”. For example if your IP address is 10.33.200.77 then use this: 10.33.200.0/24. You can discover your IP address with this command entered in a console:
sudo /sbin/ifconfig | egrep ‘Ethernet|Bcast’
OK so that should fix the Samba Broadcast response feature. What about the other ones I mentioned? Did they return satisfactory replies?
Yes they did.
Thank you. it is working now.
Glad for you.
Interesting that this brand new feature is completely unknown, is not set by default and is important for Samba to work OK. This is the first I’ve written about it IIRC. So do Samba usres just turn the firewall off in 11.0 out of frustration? Probably.
Swerdna,
In response to your question, yes they just turn it off and sometimes even then it does not work. In our shop we have a file-server running 10.3 and 4 workstations, also running 10.3 and 5 Windows XP machines. My standard order of business has been to follow your excellent Samba instructions as I set up a new machine but even that has not worked this time. We have built an 11.0 test machine and it does not play well. All of the other machines work perfectly but the 11.0 machine tells me “could not connect to host for smb://smb-network/” when I use either Konqueror or Dolphin to look at the network. This is the same whether the firewall is on or not. All other machines see the 11.0 machine in workgroup computers but connections are refused. Only the 11.0 machine is having issues, all others work perfectly.
There’s a theme running through openSUSE 11.0 with KDE4.0: not good with Samba. Ver 11.0 with KDE3.5.9 is good with Samba. And 4.0 fails in many other ways – it’s only experimental.
The upshot is that KDE4.0 should not be used for serious work, strictly only to experiment.
swerdna wrote:
>
> sheininger;1862885 Wrote:
<snip>
> All other machines see the 11.0 machine in
>> workgroup computers but connections are refused.
<snip >
This should not depend on KDE. If other machines are not able to connect to OS
11, there is an error in smb.conf or firewall.
> There’s a theme running through openSUSE 11.0 with KDE4.0: not good
> with Samba. Ver 11.0 with KDE3.5.9 is good with Samba. And 4.0 fails
> in many other ways – it’s only experimental.
>
> The upshot is that KDE4.0 should not be used for serious work, strictly
> only to experiment.
>
>
–
P. V.
Cogito cogito ergo cogito sum.
But of course you are correct, smb.conf and firewall should be examined.
Even so KDE4.0 and Samba don’t play well together.
It’s just that the network browsers available in KDE4.0 don’t work for me even though CLI commands like “smbtree -N” work fine.
The comment of @sheininger I took to be conversational rather than a question about what’s wrong.
Connecting to Samba via Gnome has been a pain as well. I think it has to do with the firewall. I’ve been going crazy trying to access my shares. I’ve set up samba before and I’ve never had it be so difficult.
It isn’t just KDE or Gnome that has problems in 11.0. I’ve turned in several other reports including items that are entered in Yast2 (such as IP ranges for the local network)and don’t show up in the associated .conf, etc. files. I have other Samba issues also. 11.0 isn’t ready for prime time quite yet, that’s why my shop puts up test machines and plays before using a new release in production. I’m pretty excited about some things in 11.0 and like what I see and I am anxious to get it up, but we will definitely let a few more bugs get fixed before it becomes the production environment.
necrolin wrote:
P. V.
Cogito cogito ergo cogito sum.