Version: (using KDE 4.3.4) OS: Linux Installed from: Ubuntu Packages Dolphin creates large amount of connections to the machine i'm browsing filling up the session count on the sever side. XP desktop install has 10 sessions limit. It seems to create a session per share,even if I don't try to browse it so on machines that have 6 or seven shares actually using the shares becomes impossible. Browse requests get denied because session setup fails with STATUS_REQEST_STATUS_DENIED. This status is ignored and the client continues to do tree connect that fails. There really should be just one, 3 tops authenticated sessions per machine, not gazzilion.
ps: My information was derived from watching what is going on on the packet level with wireshark.
The ignored status is STATUS_REQUEST_NOT_ACCEPTED. Sorry about the error in original bug post.
This bug still exists in KDE 4.4.1, Dolphin is still unable to authenticate an smb share.
You wont see this issue when communicating with a samba host or XP host with just one share. Also, its sort of a 2 in 1 bug. First, that an error status is ignored, and second that there are simply unreasonable amount of connections made, tripping the desktop windows limit.
This bug still exists in KDE 4.4.3.
This bug still exists in KDE 4.4.4, Dolphin 1.4 With one smb connection Dolphin opens 4 sessions. As soon as the 10 XP sessions are reached, no error message occurs. dolphin just pretends that I entered a wrong username / PWD When closing Dolphin the sessions are not closed.
I can confirm that dolphin makes too much connections when browsing samba shares. Dolphin uses to access (then download) files when some events occur on them (cursor/focus on a filename). Then it seems to download the entire file, even after the end of the event. I think that the solution is to disable this behavior, or at least to let one disables it. Notice this reduces transfer rate by monopolizing network ressources, and may damage hard disk by searching multiple files at different physical places. It is a serious bug. I guess those following bugs are also related to this same cause: https://bugs.kde.org/show_bug.cgi?id=252550 https://bugs.kde.org/show_bug.cgi?id=221455
The scheduler that controls all the IO slaves was rewritten for KDE 4.5.0 and as such there is a hard limit on the number of ioslaves that are started per host. Actually the smb.protocol file was missing a proper setting of the values that control this until KDE 4.7.4 release and caused the number of connections made to be in the other extreme. Too few, more specifically only one! Anyhow all of that should be resolved since KDE 4.7.4. If you still experience this issue with 4.7.4 or higher, feel free to reopen this ticket.
*** Bug 228569 has been marked as a duplicate of this bug. ***