Version: (using KDE KDE 3.1.4) Installed from: Unspecified Linux OS: Linux 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.
that's nice that you pasted the message box, but that doesn't help to fix the problem.
i have installed samba on mye linux 9.0 with the version i had no problem to install. After installation i have click the icon local network on the desktop then i have recive the message box
*** Bug 66482 has been marked as a duplicate of this bug. ***
I have same this problem , so how can i fix it ?
*** Bug 69549 has been marked as a duplicate of this bug. ***
I'm expiriencing the same Problem. Everytime I try to open up the smb:// konqueror crashes with this libsmbclient-error message. does anyone has a clue how to solve this?! anybody working on it?
I fianly got mine to work. I had to uninstall everything that had to do with smb and samba. This includes the libsmbclient3 in Yast. It will tell you there are dependicies remove them all. Then reinstall them. Then I did a system update in Yast. It all works now. That's what I did and it worked for me. If what I done had anything to do with it I don't know but it now works. I used Yast to uninstall and install everything.
Subject: Re: libsmbclient reported an error not possible to connect with local network Am Donnerstag 04 Dezember 2003 04:11 schrieb Tracy Williams: > I used Yast to uninstall and install everything. I'm not sure, but I'd guess that it was pure luck :) Greetings, Stephan
> I used Yast to uninstall and install everything. I'm not sure, but I'd guess that it was pure luck :) I think when I did the Suse update it messed up the samba client or server, So by uninstaling everthing for it and reinstaling it did the trick. I was not saying Yast had anything to do with it. Just Yast is much easier to deal with than the KDE control center. I am just trying to give somone something to start with since I could not really find any help elswhere. Thanks, Tracy
*** Bug 69675 has been marked as a duplicate of this bug. ***
thanks, i'll try reinstalling all smb related stuff.. although it doesn't satisfy me 100%.. =)
Well mine stoped working again for some reason. I think it is SuSe. This don't satisfy me at all. Making me mad. We need better help. Will search for this again and post results.
Created attachment 3648 [details] tcpdump This is a tcpdump while trying to open "local network" (smb:/ in konqueror). Konqueror crashes telling me: 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) My system is suse linux 9.0 with kde 3.1.4 with all latest patches installed. My network has a very simple setup. just 2 computers (the other one has Windows2000 installed). can anyone help me with this?
I'll build a kio_smb.so
Created attachment 3668 [details] replacement for /opt/kde3/lib/kde3/kio_smb.so Please install this file and then try again browsing and then check ~/.xsession-errors
trying to assign away from Bertrand :)
when I down loaded the file I got a attachment.cgi file. How do I install this?
This started to work for no good reason. I did nothing. It just started to work.
How i installe the attachement ?
Created attachment 3725 [details] .xsession-errors while trying to open smb:/ Hi Stephan, thanks for your help so far. i downloaded your file and this is the .xsession-erros i got. i looked at the output but couldn't figure out what it's about. :-) maybe you need some info for debbuging: workgroup: "LOOK" my linux box: linux 192.168.1.2 (static ip) other network clients heike 192.168.1.135 (windows 200, ip assigned via dhcp) digitus wireless broadband router 192.168.1.11 the broadband router works as dhcp but my box has a static ip (192.168.1.2). maybe this helps. best regards, alex.
hello all ! thank u very much for trying support me about the problem with the libsmbclient . I have deinstall the Network Icon it doesent work on mye Comupter the Network works now after i have installed manually regards vito
Subject: Re: libsmbclient reported an error not possible to connect with local network Am Dienstag 16 Dezember 2003 02:45 schrieb Alexander Look: > thanks for your help so far. i downloaded your file and this is the > .xsession-erros i got. i looked at the output but couldn't figure out what > it's about. :-) > > maybe you need some info for debbuging: > > workgroup: "LOOK" > > my linux box: > > linux 192.168.1.2 (static ip) > > other network clients > > heike 192.168.1.135 (windows 200, ip assigned via dhcp) > > digitus wireless broadband router 192.168.1.11 > > the broadband router works as dhcp but my box has a static ip > (192.168.1.2). > > maybe this helps. Many thanks for the details. The debug output shows it connected fine to 192.168.1.135, but fails to get a share listing out of it. Can you try smbclient -d 100 -L 192.168.1.135 in opposition to smbclient -d 100 -L HEIKE ? Maybe that reveals something. Greetings, Stephan
Created attachment 3888 [details] log from smbclient -d 100 -L 192.168.0.1 HI I tried your new kio_smb.so, and tried to run it with smbclient -d 100 -L 192.168.0.1, and here is the output from the console. My Network: 1 Computer WinXP, 192.168.0.1, name Jeanette 1 Computer SuSE 9.0 Professional IP from DHCP (normally 192.168.0.55), name Niclas/Linux My xsession-error looks much like the previous one. I can submit it and a tcp-dump if it could be of help. Workgroup TANNNE
Hello Stephan Kulow Reading and understanding all the stuff for a newbee is not so easy. Compressing this all, I think, is to install that file (#15, id 3668). How ? Please help me. By the way I have the tcpdump, Do you want it ? Henk
A few days ago I set up a antoher small Linux-Box Router (Debian/Woody) that is now acting as a Samba Master Browser for my network. Browsing the network works perfectly now! :-) I'm actually have no idea why this solved the problem.. I didnt change anything on the other machines (SuSE 9.0, Windows 2000, Windows XP) so it must have something to do with the new Box acting as Master Browser. Maybe this Problem is only SuSE specific? Anyway, thanks for your support so far. I will come back here regularly to see if this bug (there certainly is a bug) has been fixed. cheers, Alex.
well, the problems appears if the master browser isn't detectable reliable. So a simple change to the network setup can change that. It's no magic - it's netbios crap :)
*** Bug 71249 has been marked as a duplicate of this bug. ***
*** Bug 71796 has been marked as a duplicate of this bug. ***
*** Bug 71677 has been marked as a duplicate of this bug. ***
*** Bug 72723 has been marked as a duplicate of this bug. ***
*** Bug 73581 has been marked as a duplicate of this bug. ***
*** Bug 70380 has been marked as a duplicate of this bug. ***
*** Bug 75995 has been marked as a duplicate of this bug. ***
anyone in the CC list still having this problem and running SUSE? I have some new versions you could put some testing in.
I just installed SuSE 9.1 and I am having the same problem but with a different error: An error occurred while loading smb:\: Internal Error Please send a full bug report at http://bugs.kde.org Unknown error condition in stat: Network is unreachable Works from command-line.
The network is unreachable is a regression in samba 3.0.2a. Fixed in 3.0.4 - there will be an online update for samba on 9.1
Here it's weird. I just tried with samba-3.0.4, and even recompiled kio-smb (3.2.2). If I type: "smb://pandora/" it crashes with that internal error. If I type "smb://pandora" it hangs forever. If I type "smb://pandora/share" then it connects to the share, prompts me for my username/password combination and works.
the smb://pandora is no valid URL and the redirect to smb://pandora/ hangs - but this is fixed for 3.3 (will backport later) with what internal error does smb://pandora/ fail?
For whatever reason, I am fine if I use that kde-app - smb4k. It works fine, I just really care for it. Updated all my KDE packages, smb:\\ deal in Konqueror doesn't work.
Created attachment 5943 [details] konqsmberror.png It crashes with this error (shown in screenshot).
andreas: can you please copy over the kioslave/smb from CVS HEAD and reinstall? Then add in ~/.kde/share/config/kioslaverc [SMB] DebugLevel=100 run your test and send me your .xsession-errors output? Thanks.
Hello, I updated my system to SuSE9.1, KDE3.2.1 in the meantime, have still the same problem. Hope will not have an impact of the trouble ticket. If yes better close it to open a new one, if not see below. Can you give me more support because it's not clear for me what exact to do for: "can you please copy over the kioslave/smb from CVS HEAD and reinstall? Then add in ~/.kde/share/config/kioslaverc " Thanks and regards 66381@bugs.kde.org schrieb am 12.05.04 09:58:24: ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=66381 coolo kde org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED everconfirmed|0 |1 ------- Additional Comments From coolo kde org 2004-05-12 09:58 ------- andreas: can you please copy over the kioslave/smb from CVS HEAD and reinstall? Then add in ~/.kde/share/config/kioslaverc [SMB] DebugLevel=100 run your test and send me your .xsession-errors output? Thanks. ____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Sober.A-F! Kostenfrei fuer FreeMail Nutzer. http://f.web.de/?mc=021158
Hello, I updated my system to SuSE9.1, KDE3.2.1 in the meantime, have still the same problem. Hope will not have an impact of the trouble ticket. If yes better close it to open a new one, if not see below. Can you give me more support because it's not clear for me what exact to do for: "can you please copy over the kioslave/smb from CVS HEAD and reinstall? Then add in ~/.kde/share/config/kioslaverc " Thanks and regards 66381@bugs.kde.org schrieb am 12.05.04 09:58:24: ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=66381 coolo kde org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED everconfirmed|0 |1 ------- Additional Comments From coolo kde org 2004-05-12 09:58 ------- andreas: can you please copy over the kioslave/smb from CVS HEAD and reinstall? Then add in ~/.kde/share/config/kioslaverc [SMB] DebugLevel=100 run your test and send me your .xsession-errors output? Thanks. _____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P! Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157
Frank, #41 was directed towards andreas. I miss the time to explain to you what I meant, but I hope andreas knows. As for SUSE 9.1: I hope SUSE does a samba update soon over YOU.
Stephan, I got it and will post back my results in this ticket.
Ok,let's go. First of all, the problem I reported with my screenshot seems to be bogus: I can't reproduce it anymore. Yesterday I was doing a lot of testing with samba-3.0.4 and at one time I know I had a bogus smb.conf file (setting security=ads and domain logons=yes as well as domain master=yes while there was a win2003 pdc server in the same subnet for the same domain, I forgot to change those two "yes" to "no"). I started over with a clean install and this is my conclusion: - with samba-3.0.3, the "smb:/" url doesn't work. - with samba-3.0.4, "smb:/" starts to work like a charm. It almost immediately lists all domains/groups in my subnet. Both tests above were done without changing kio-smb (still the one from KDE-3.2.2). Browsing also started working again perfectly after I upgraded to samba-3.0.4. Sorry for the false alarm (at least for me). I just upgraded to your kio-smb version and the only side effect I saw so far is that the description shows together with the server name inside (), but it ends with a square character, like it was trying to print the terminating \0 or something. With the new kio-smb, now "smb://pandora" redirects to "smb://pandora/" and works correctly also. So, I would advise all to upgrade to samba 3.0.4 (or at least apply the libsmbclient patch referenced in that samba bug entry #429). I haven't tested applying only that patch, though.
actually it would be good if you could break your setup again and send me the debug output as described in #41. Then I could try to send the samba developers another fix, so that you get something else than "libsmbclient reported an error" :)
Created attachment 5972 [details] konqueror-samba304-newkio.log Ok, I managed to reproduce the libsmbclient error with samba-3.0.4 and the new kio-smb, but I must say I had to push it hard. Here is what I did: - fire up konqueror (samba 3.0.4 is already running localhost) - call "smb://pandora/". As expected, nothing shows up (no shares are browseable by anonymous users), but no error either - on another terminal, restart samba - shift-reload on konqueror -> the libsmbclient error appears - shift reload again: no error anymore. I'm not sure it's useful: as I said, I was pushing it hard and this is not a day-to-day situation at all.
type: "smb://computername" and see: it works! At least with a Sweex DHCP router and a XP machine. If I don't use this, thus just click the network icon, i get the bug message. So I'll wait for the suse update 9.1 Regards, Peter
*** Bug 81996 has been marked as a duplicate of this bug. ***
Hi All: I'm getting the same error message. I get it when I attempt to view my other machines (a Mac G4 Panther and a Win98 box). I've tried implementing the attachment that you offered in #15, but I'm not able to access (via "cd", "cp"ing a file, or drag/drop using file manager) the /opt subdirectories. Permissions aren't the problem. They are 755 and I'm trying it as root. So I'm stuck. Is there a patched Suse that addresses this that I can download? Thanks! :-{)] -Mark A. Morenz
Hi Again: A typo in my 'cd' command threw me. Thought I was locked out entirely. Anyway, I was able to copy your file in just fine (once I gave myself write permission, of course). Anyway, it didn't solve the problem, I'm sorry to say. Same error message. It's worth noting that I can access one of the other machines if I use the IP address, but not the hostname. When I use the hostname, I get the error message. The other machine (the Mac G4) I still can't see at all. But then again, I can't see it from the Wintel box either. So the problem may be with it. I might need to select the share again. I will access the .xsession-error that you mentioned earlier and see what I can find... This was all working fine (all machines from all directions) just a few months ago. Very frustrating... :-{)] Mark M.
Happens here too on Suse 9.1 with KDE 3.3.1 updated to the latest and greatest. Samba on the terminal is working find and I can scan and mount any share on the net. If I put in konqueror ; "smb://desktop/files" it works fine. If I put : "smb://desktop/", it crashes with the already mentioned message. I'm runnign samba-3.0.4 Regards
Happens here with Fedora Core 3, using KDE 3.3.2 when samba server is not running. Without the samba server running entering smb:/ gives the 'error while connecting to the server responsible'. Running smb:/xxx.xxx.xxx.xxx gives the more impressive internal error message. With samba server running, I get to see the hosts on the network, However I cannot browse the WinXP host. When I double click to get the browse list I get the 'internal error' message, although by the same token I can't browse with smbclient either. I'm running samba-3.0.10-4 / konqueror-3.3.2-0.2 / kde 3.3.2-0.4 / stock kernel 2.6.10.
Stephan Kulow wrote: > Fixed in 3.0.4 - there will be an online update for samba on 9.1 I can't find it! I have SuSE 9.1 Personal, I go into YaST, click "Online update", choose the main mirror (ftp.suse.com) and don't find any update for libsmb or samba... I did search for "smb" too...
See also 75995: Samba and Konqueror do not work together. This is still a problem for me. Fedora Core 5 KDE 3.5.2. Was also a problem on Fedora Core 4 KDE 3.5.1 I login to SMB shares using standard user name/password. With all Samba packages later than 3.0.14a-2.1, if I try to access SMB shares using Konqueror, the user login screen keeps re-appearing asking for my login info. If I load the old Samba packages, the user login process works flawlessly and I can see my network shares in the Konqueror window. As was the case for the person who initially reported 75995, I can access the network shares via a command line (smbclient) with no problem regardless of Samba version. Thanks.
*** Bug 133222 has been marked as a duplicate of this bug. ***