View Issue Details

IDProjectCategoryView StatusLast Update
0006530MMW v4DB/FileMonitorpublic2011-05-11 05:11
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version4.0 
Target Version4.0 
Summary0006530: Navigation of Samba/CIFS networks is very slow
DescriptionWhen the user navigates to a Windows/Samba network location (either via the My Computer node or via the Add/Scan folders node), MM takes ~20 seconds to find the network, and to open up any node within the network.

In contrast, this takes ~1 second with Windows Explorer.
TagsNo tags attached.
Fixed in build

Relationships

related to 0005953 closedLudek Combine Add/Rescan and File Monitor functionality 
related to 0006544 closedLudek Pressing 'Insert' while on a Location > Samba node doesn't transfer correct path to Add/Scan Folders dialog 

Activities

rusty

2010-10-14 19:17

administrator   ~0020773

Note: in build 1316, I cannot navigate to a cifs/samba folder at all (whether via My Computer node or via the Add Folders dialog. MM simply fails to detect the shared folders.

Ludek

2010-10-20 12:02

developer   ~0020879

Last edited: 2010-10-20 12:02

Rusty, I have just tested this in 1317 and I have no problem accessing Samba server (through VPN) at all.

It works fine:
- via MediaMonkey -> My Computer -> Network -> ...
- via Windows Explorer
- via Total Commander

Please try re-test in 1317 and keep in mind that from my experience the 20 seconds delay could be caused by VPN and usually doesn't depend on used client, but on the time when the server is accessed. Sometimes it happened to me that I tried access it through Windows Explorer -> it took 10 seconds, but after that in MediaMonkey it was immediatelly.

rusty

2010-10-20 13:13

administrator   ~0020880

Tested in 1317 using a local network (no VPN). Here's what happens:
-In explorer, the shared machines (e.g. NAS5) does not appear by browsing--not an uncommon situation with CIFS networks. Once I enter the IP address (e.g. //192.168.1.187), then all of the individual shares on the machine appear as expected.

In MediaMonkey:
a) in the My Computer node, browsing for NAS2 fails (as expected, just like in windows explorer), but unlike Windows Explorer, there's no way to enter the network path to browse!

b) In MediaMonkey's Add/Scan folders dialog, it's possible to 'Add' a path to the shared machine (e.g. //192.168.1.187), but unlike Windows Explorer, expanding the 192.168.1.187 node does not show up the child nodes).

So the issue is twofold:
a) In the tracklist view, it would be nice if there was a means to enter an address
b) In the Add/Scan folders dialog, adding a _share_ works as expected, but adding a machine name doesn't.

rusty

2011-05-10 14:04

administrator   ~0025002

Closing this issue since the bug isn't really about slow performance, but about inability to browse the network. Will re-open a new bug.