The following lines were added (+) and removed (-):
# Ensure settings correct. Works best if windows share has a password that is alpha numeric. Some special characters cause trouble. Did you recently change your SMB password?# If that fails and if you have the luxury of owning a root'd device you can manually clear the cache folders (see above.)# If that fails and if you have the luxury of owning a root'd device you can manually clear the cache folders ''(see above: data/data/com.estrongs.android.pop/tmp)''# Finally if all else fails, the issue could be with network discovery on the LAN itself. (details below) # Finally if all else fails, the issue could be with network discovery on the LAN itself. ''(details below)'' ==== ES File Explorer and Network Discovery ====ES File Explorer keeps spinning due to Network Discovery issues on your Microsoft / CIFS network. Network Discovery is the mechanism that enables machines or devices with shares to be visible in the Network Resources (Network Neighborhood or My Network Places.) Works best if windows share has a password that is alpha numeric. Some special characters cause trouble. Did you recently change your SMB password?Network discovery is not a single thing. In general terms it is the process of gathering information about the Network resources near you. It consists of a group of protocols that all report to the Function Discovery platform. Probably the most well-known protocol is NetBIOS Browsing, but it also includes WSD, UPNP, SSDP, and back in the day WINS.ES File Explorer is very picky when it comes to accessing a CIFS or SMB share. If there are any problems with network discovery or the various protocols involved on your network, due to misconfiguration, or another resource related issue, ES File Explorer will fail to access shares that are otherwise accessible to a Windows PC. For example, on some NAS devices after extended uptime network discovery will become problematic to where the server is no longer visible in the Network Resources, however, still directly accessible by CIFS, Samba, and Microsoft PCs. In this condition the problem may go unnoticed so that it is assumed that ES File Explorer is suspected as suddenly broken. In short, try to reboot the NAS or the machine with the share. Troubleshoot the share, although it might be accessible via the LAN using another PC, a minor glitch with Network Discovery can make ES File Explorer refuse to load from the share. It is a confirmed fact that the visibility of the directly accessible share in "My Network Places" is directly related to the problem ES File Explorer may have in accessing the share: ES File Explorer just keeps searching / spinning / hangs.