Created attachment 84136 [details] sample of autofs NAS shares found by mint13-GNOME Nautilus User is unable to auto mount CiFS shares in mint16 that are readble /accessable using Mint16-petra-KDE out of the box-ISO (go-Live-CD) Previous version using mint13-GNOME Nautilus file manager works fine. this appears to be an autoFS issue or a failing daemon. when mounted using go-LIVE mint13 CD with GNOME Nautilus the following mounts appear >mount binfmt_misc on proc/sys/fs/bin/fmt-misc (rw,no exec,no suid, nodev) gufs-fuse-daemon on /home/mint.gvfs type.gvfs-fuse-daemon, crw, nosuid, nodev, user=mint. Dolphin-KDE does not auto mount NAS shares. Changing SMB-Samba.cfg workgroups to localworkgroups has no effect. runing local smb tools produces these reports showing available shares. lee@SAM275E5E-mint16:~ > smbtree Enter password: TIGERGROUP \\SHAREDSTORAGE DNS-320-NAS \\SAM275E5E-MINT1 SAM275E5E-mint16 server (Samba, Linux Mint) \\PEARLINGTON WORKGROUP \\MINT13X32-ASPIRE mint13x32-Aspire-4349 server (Samba, Ubuntu)
Created attachment 84137 [details] example of autofs cifs mounted shares on NAS box. Using mint13-GNOME Nautilus to access shares on Dlink NAS box. -ATP
Thanks for the bug report, but I'm not sure if I understand what you mean when you say "Dolphin-KDE does not auto mount NAS shares.". Could you please describe in detail what exactly you did, what you expected to happen, and what happened instead? Maybe a screenshot might help as well (if the problem is, e.g., that some device is not being shown in the Places Panel). Thanks.
I tried to get back to the user community about this bug, but could not log back in for some reason. Here is what's wrong with kde-networking. "zero config" doesn't seem to work for my wifi and the RJ45 LAN plug has to be reconfigured to use a subnet mask to pick up my windows shares. The KDE-network config doesn't allow sufficient GUI-user control to change workgroups, dns, and IPA-subnets. I provided user data in my orginal bug report that explains how I am configured. All I know is that when I use Mint16-Petra-Xfcex64 the windows shares start automatically with "zero-config" on the wifi and with some tweaks to IPV4 to add my subnet of 255.255.0.0 If doesnt work at all with Mint16-Petra-KDE-x64 using the3 same hardware interfaces. Sorry guys I moved back to MINT13 until this version is stable. if you need more calcification please call me? -- LEE click here.....*David Lee Berry*<http://www.linkedin.com/profile/view?id=41063359&trk=tab_pro> p:+1(619)312-4815 *Website*: *http://wp.me/P3GGHo-1 <http://wp.me/P3GGHo-1>* *twitter: *@LeeWhiteTiger On Tue, Dec 17, 2013 at 5:50 PM, Frank Reininghaus <frank78ac@googlemail.com > wrote: > https://bugs.kde.org/show_bug.cgi?id=328892 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report, but I'm not sure if I understand what you mean > when > you say "Dolphin-KDE does not auto mount NAS shares.". > > Could you please describe in detail what exactly you did, what you > expected to > happen, and what happened instead? Maybe a screenshot might help as well > (if > the problem is, e.g., that some device is not being shown in the Places > Panel). > Thanks. > > -- > You are receiving this mail because: > You reported the bug. >
Frank please see attachments i submited with the bug report. If u cant read them let me know by phone. LEE On 17 Dec 2013 17:50, "Frank Reininghaus" <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=328892 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report, but I'm not sure if I understand what you mean > when > you say "Dolphin-KDE does not auto mount NAS shares.". > > Could you please describe in detail what exactly you did, what you > expected to > happen, and what happened instead? Maybe a screenshot might help as well > (if > the problem is, e.g., that some device is not being shown in the Places > Panel). > Thanks. > > -- > You are receiving this mail because: > You reported the bug. >
Created attachment 84333 [details] testcase smbtree fails to automount NAS Network Shares Frank I appologize for the criptic remarks about this bug in KDE. i went back and retested it with smb-samba smbtree and that fails to produce any open shares on my NAS network. smbtree also fails to show any print shares. I really dont think it is a Samba problem because shares connect without any user intervention (i.e edits to /etc/samba/smb.conf It appears to be a network problem that is related to establishing public shares for subnets. i have attached 2-text documents showing output from "smbtree" on petra-kde and a working copy from Petra-XFCE. By compairing these 2-outputs you can see that network shares are not active. Starting and stoping samba did not fix the problem. I am also trying to include snapshots of networking folders using file managers. KDE-Dolphin XFCE-Natilus.
Created attachment 84334 [details] working test case smbtree with Petra-XFCE-Thunar active sub-directories. This test case shows that shares are available for whitetiger NAS storage.
Created attachment 84335 [details] Test case for petra-KDE -fails to show sub-directory folders. The test case was run agains go-live CD for Petra-KDEx64 without any changes to smb.cfg.
Created attachment 84336 [details] smbtree has no output. when tested against a live network. #testcase smbtree No command 's0btree' found, did you mean: Command 'smbtree' from package 'smbclient' (main) s0btree: command not found [127]mint@mint:~ > smbtree Enter mint's password: TIGERGROUP \\SHAREDSTORAGE DNS-320-NAS \\PEARLINGTON mint@mint:~ > # This is a goLive_CD of Petra-KDE-x64 # No print shares show when printer is installed and shared. # No NAS Server shares show when connected to wifi-whitetiger # no Auto mount appear for any printers on the network. Expected result should be same as for Petra-XFCE-x64 GoLive cd. Shown below Testcase: lee@mint16-xfe-4349 /etc/samba $ smbtree WORKGROUP \\MINT16-XFE-4349 mint16-xfe-4349 server (Samba, Linux Mint) \\MINT16-XFE-4349\Samsung-SCX-4200-Series Samsung SCX-4200 Series \\MINT16-XFE-4349\print$ Printer Drivers \\MINT16-XFE-4349\IPC$ IPC Service (mint16-xfe-4349 server (Samba, Linux Mint)) TIGERGROUP \\SHAREDSTORAGE DNS-320-NAS \\SHAREDSTORAGE\lp USB Printer installed (SCX-4200) \\SHAREDSTORAGE\IPC$ IPC Service (DNS-320-NAS) \\SHAREDSTORAGE\cdr-image HD-camera \\SHAREDSTORAGE\scx4200-xp-setup-cdr xp-linux-drivers \\SHAREDSTORAGE\image-hp1020-setup-w32x install-hp-print-driver \\SHAREDSTORAGE\hp-2400-scanner setup hp scanner \\SHAREDSTORAGE\XP_HOME TGCTTX3DK9YCMX6646W2P34MW \\SHAREDSTORAGE\dns320-setup-cdr D-link-DSL320-setup \\SHAREDSTORAGE\ms_gold MYHVTWQ49MQRPVFV86FCP3R8Y \\SHAREDSTORAGE\Windows 8 Final Professional win8 pro \\SHAREDSTORAGE\Volume_2 \\SHAREDSTORAGE\win7-drivers-archive-cd1 unreadable disk locked \\SHAREDSTORAGE\Volume_1
Created attachment 84338 [details] working copy of windows Cifs shares in mint13 This is the expected result for connecting to CIFS shares on NAS storage device. User is required to login to acess the subfolders first. In the GUI network test the Storage Server does not appear and the shares are not viewable as they are in this screensnap.
Created attachment 84340 [details] Thunar fails to connect to active NAS live CIFS shares. In this test case a different file mgr was used to check if the GUI was broken. Thunar version 1.6.3 was used to connect to NAS SHAREDSTORAGE. Output from smbtree shows shares are active but clicking on the icons for "Windows Network" produces no results. test failed.
Thanks for the additional information. To be honest, I have never used smb and have zero knowledge about how it works (the access to smb shares is provided by a kioslave, which is not part of Dolphin itself). I'll reassign to kio/smb, in the hope that someone who knows more about smb can say something useful about your problem.
Frank I don't think the problem has anything to do with smb samba. I was only using smb to only test network connectivity. Outside of modifying the workggroup name changed to TIGERGROUP. I have no special requirements for Samaba. In other Mint version I only had to specify workgroup name and Static IPA-address, subnets to be able to connect. I was reporting that KDE networking doesn't work out of the box using CIFS windows shares on NAS storage. All is well with Petra-XFCE so I'm using that for now. Have a great day. On 1/3/14, Frank Reininghaus <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=328892 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEEDSINFO |UNCONFIRMED > CC| |frank78ac@googlemail.com > Component|panels: folders |smb > Version|4.11.2 |4.11.3 > Resolution|WAITINGFORINFO |--- > Assignee|dolphin-bugs-null@kde.org |unassigned-bugs@kde.org > Product|dolphin |kio > > --- Comment #11 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the additional information. To be honest, I have never used smb > and > have zero knowledge about how it works (the access to smb shares is provided > by > a kioslave, which is not part of Dolphin itself). > > I'll reassign to kio/smb, in the hope that someone who knows more about smb > can > say something useful about your problem. > > -- > You are receiving this mail because: > You reported the bug. >
(In reply to comment #12) > Frank I don't think the problem has anything to do with smb samba. I didn't mean that there is a problem with Samba itself, but possibly with the KDE code that is used to interact with smb/cifs shares. I really cannot say more about this issue - sorry about that. I hope that someone else who has more insight into these issues can help to resolve the problem.
Created attachment 84505 [details] attachment-31446-0.html I was able to resolve the issue and install NAS shares using "brute-force" method. You could close this BUG report and reschedule it as a feature enhancement for adding-network shares. Adding short-cuts to network shares is not covered in the user-manual on about page-32 would be a good place to add it. I'd like to clarify that Samba does not install with the "golive CD-ISO," and is therefore out of the picture. Here is what I did to get CIFS-windows NAS Shares to work on my home server. I tested this in both the x32-bit and x64bit version of Petra-KDE goLive CD. "Brute-force method" 1) "Add a Network Folder" and 2) edit the network configuration file using Dolphin-GUI Tools. 3) Manually input the Server-host name and the IP-Address. "Unlike XFE you do not have to add the IPA to the network-config-eth0. for private VPN" 4) When the server is connected the host login menu will appear. >>enter your name and password. 5) The NAS share name should now appear under the Dolphin Network folders as in my example. 6) You can also verify that the NAS network connection is up using smb. cr=carriage return. In the console window enter>> smbtree (cr) You should be able to access all Windows shares now with read/write capability without the need to install Samba. If your having network trouble then try installing a shared printer using CUPS. I did not have to install printers to get NAS shares up. -- LEE On Mon, Jan 6, 2014 at 7:23 PM, Frank Reininghaus <frank78ac@googlemail.com>wrote: > https://bugs.kde.org/show_bug.cgi?id=328892 > > --- Comment #13 from Frank Reininghaus <frank78ac@googlemail.com> --- > (In reply to comment #12) > > Frank I don't think the problem has anything to do with smb samba. > > I didn't mean that there is a problem with Samba itself, but possibly with > the > KDE code that is used to interact with smb/cifs shares. I really cannot say > more about this issue - sorry about that. I hope that someone else who has > more > insight into these issues can help to resolve the problem. > > -- > You are receiving this mail because: > You reported the bug. >
Created attachment 84506 [details] attachment-31446-1.dat
Created attachment 84507 [details] nas-network-up-show-all-volumes.png
Created attachment 84508 [details] dolphin-add-windows-network-drive.png
Created attachment 84509 [details] dolphin-Folder-settings-info.png
KDE does not mount remote filesystems like gnome does so auto mounting never happens unless the distro of your choice set that up using some other means, e.g. autofs.
Created attachment 91821 [details] attachment-7327-0.html Work-around: I have to assign a folder to Dolphin and then assign a Samba share to the external media server disk to it using the disk. Gnome/Thuar picks this up automatic as a cifs-share. smb://sharedstorage-1.local>Vol1 smb://sharedstorage-1.local>Vol2 I have to remember to set this up again with each new release. Please help to automate it? Lee Berry @LeeWhiteTiger P: +1(619)312-4815 M: +6(016)880-6694 F; #David.Lee.WhiteTiger On Wed, Oct 1, 2014 at 8:56 PM, Dawit Alemayehu <adawit@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=328892 > > --- Comment #20 from Dawit Alemayehu <adawit@kde.org> --- > KDE does not mount remote filesystems like gnome does so auto mounting > never > happens unless the distro of your choice set that up using some other > means, > e.g. autofs. > > -- > You are receiving this mail because: > You reported the bug. >