smb:/ mostly does not work (XP machine gets a broadcast, why?)
Hello everybody, in short my problem is that smb:/ does not work anymore. I suspect that this is because of a XP machine on the network that I send a broadcast to right after I sent it to ...255 and I do not know why? Since I installed Suse 9.0 smb:/ is hardly usable. When I enter smb:/ it mosly does not work, sometimes it does and I can see the workgroups on the network, but only browse those without any XP machines in them. If I enter smb://workgroup manually I can browse the ones without XP machines, even if smb:/ does not work. Once I could even brwose those with XP in them. In Suse 8.2 everything worked fine using KDE 3.1.4, i.e. the same. The failure-message states that libsmbclient terminated with an error without specifying what it was. Having a look at the tcpdump just shows me that: 15:16:56.966616 username.workgroup.32881 > 192.168.20.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 15:16:57.236219 username.workgroup.32883 > 192.168.20.157.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST (DF) Why do I send second broadcast to 192.168.20.157? That machine is a XP machine. Does that one act as master browser or something and then refuses me? After the second broadcast there is nothing coming back to me. When I use linneighborhood I can at least enter the workgroup but get something like: connecting to 192.168.20.157 at port 139 Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- Error returning browse list: NT_STATUS_ACCESS_DENIED As it worked in 8.2 I thought that there might be something different. KDE is the same, my username, my workgroup and the installation of the other machines is the same. The only thing I noticed it that libsmbclient3 is installed and not libsmbclient. So I tried to add that package but no difference. Removing libsmbclient3 package is not possible without removing all samba related KDE-packages. Another thing that was not there in 8.2 was the samba Yast2-module, but I entered the same workgroup, so this should not be the source for the problems. I looked on google and the SDB for some help and there were similar problems but only for KDE <= 3.1.2 and nothing related to 3.1.4 or Suse 9. Other people have reported that it did not work for them in 8.2 and now it does, so I guess the XP machine 192.168.20.157 is the problem, but why? And why does it sometimes work? Thanks for your help! Sven
Sven Burmeister wrote: I had same type of probems with Win2K network. I did find out that it will not work at all with SuSEfirewall2 running. I have given up and I got no input from the suse mail list, so guess not too many people are running samba client. File bug reports to the SuSE Feedback website. Art
Hello everybody,
in short my problem is that smb:/ does not work anymore. I suspect that this is because of a XP machine on the network that I send a broadcast to right after I sent it to ...255 and I do not know why?
Since I installed Suse 9.0 smb:/ is hardly usable. When I enter smb:/ it mosly does not work, sometimes it does and I can see the workgroups on the network, but only browse those without any XP machines in them. If I enter smb://workgroup manually I can browse the ones without XP machines, even if smb:/ does not work. Once I could even brwose those with XP in them. In Suse 8.2 everything worked fine using KDE 3.1.4, i.e. the same. The failure-message states that libsmbclient terminated with an error without specifying what it was. Having a look at the tcpdump just shows me that:
15:16:56.966616 username.workgroup.32881 > 192.168.20.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 15:16:57.236219 username.workgroup.32883 > 192.168.20.157.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST (DF)
Why do I send second broadcast to 192.168.20.157? That machine is a XP machine. Does that one act as master browser or something and then refuses me? After the second broadcast there is nothing coming back to me. When I use linneighborhood I can at least enter the workgroup but get something like:
connecting to 192.168.20.157 at port 139 Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Sharename Type Comment --------- ---- ------- Error returning browse list: NT_STATUS_ACCESS_DENIED
As it worked in 8.2 I thought that there might be something different. KDE is the same, my username, my workgroup and the installation of the other machines is the same. The only thing I noticed it that libsmbclient3 is installed and not libsmbclient. So I tried to add that package but no difference. Removing libsmbclient3 package is not possible without removing all samba related KDE-packages. Another thing that was not there in 8.2 was the samba Yast2-module, but I entered the same workgroup, so this should not be the source for the problems.
I looked on google and the SDB for some help and there were similar problems but only for KDE <= 3.1.2 and nothing related to 3.1.4 or Suse 9. Other people have reported that it did not work for them in 8.2 and now it does, so I guess the XP machine 192.168.20.157 is the problem, but why? And why does it sometimes work?
Thanks for your help!
Sven
Art Fore wrote:
Sven Burmeister wrote: I had same type of probems with Win2K network. I did find out that it will not work at all with SuSEfirewall2 running. I have given up and I got no input from the suse mail list, so guess not too many people are running samba client. File bug reports to the SuSE Feedback website.
Hi, I do not have any Firewall activated. I did so with Yast and then smb:/ gives the failure message that no workgroups could be found. However when deactivating it, the error message displayed by konqueror is a bit different. Internal Error please send a bug report to: http://bugs.kde.org libsmbclient reported an error, but didn't specify what the problem is. This might indicate a severe problem with your network - but also might indicate a problem with libsmbclient. If you want to help us, please provide a tcpdump of the network interface while you try to browse (be aware that it might contain private data, so don't post it if you're unsure about that - you can send it privately to the developers if they ask for it) Sven
Sven Burmeister schrieb:
in short my problem is that smb:/ does not work anymore. I suspect that this is because of a XP machine on the network that I send a broadcast to right after I sent it to ...255 and I do not know why?
It seems that I solved the problem by installing the libsmbclient 3.0.1 pre2 and renaming it to libsmbclient3.so... Sven
participants (2)
-
Art Fore -
Sven Burmeister