No devices on network showing in scan

[av8ing]

Hi,

I have just finished a new build, running Windows 10. MC is not showing any devices on the network no matter what scan method I use, although windows file explorer shows all devices. I have enabled SMB1, allowed MC to pass Windows Firewall, I have enabled linked connections (verified in the registry) all to no avail.

It works on my surface pro and have exported the net settings from it, but it doesn't seem to import the xml file on the new rig (dialog box doesn't close on it's own and the scanning method doesn't change).

I can reach my 2 Synology NAS's through the command line, but not the Shield TV and next restart does not show the NAS without re-entering through the command line.

Any and all help is very much appreciated.

Thanks in advance.

[Mathias (Author)]

Windows Networking in a messy. so much can mess with it.

In Windows Explorer are they shown as network devices ? or are they other kind of device. ?
MC only find network devices that are exposed as normal network devices. If the devices require special software to be access, MC can't find it.

[av8ing]

Hi Mathias, and thank you for replying.

They are all showing in windows as network devices. I have included a screen shot of the file explorer results.

[Mathias (Author)]

Then I dont know. it should work.

As long as you can access them via a UNC path like \\server\share  then it should work

[av8ing]

Yes, I can reach the NAS's that way. I add a UNC shortcut on the task bar, but if I close MC and re-open, it's gone again. I have mapped individual folders from the NAS and MC will show those but scanning the network comes up with zero results no matter what scanning method.

I have never had this issue with MC. I've used it on 5 different computers running both Win 7 & 10 and it works flawlessly. I've tried uninstalling the latest version and installing an earlier version, same results. It's really driving me nuts.

I do want to thank you again for your replies.

[AlanJB]

@av8ing,

are you able to determine in which version it last worked correctly?

Old version installers are available here: http://multicommander.com/olddownloads

[av8ing]

Hi Alan,

It seems to be something with this new build, some setting that I just can't put my finger on. I've tried the last 4 builds with no luck. My Surface is running the most recent version and it has no issues.

[AlanJB]

@av8ing,

are there any entries in the MC logs (for example, "connection failed" or similar)?

[av8ing]

Hi Alan,

Sorry for the late response. I have been out of town the past few days. It took some searching to find the logs, but I found them. Here are the errors:

2020-01-08 21:53:14.364 Enumerating network 'Network' : Found (Microsoft Terminal Services)
2020-01-08 21:53:14.364 Cannot complete network drive enumeration, Error:259
2020-01-08 21:53:14.365 Enumerating network 'Network' : Found (Microsoft Windows Network)
2020-01-08 21:53:18.869 Cannot enumerate network drives, Error:53
2020-01-08 21:53:18.869 Enumerating network 'Network' : Found (Web Client Network)
2020-01-08 21:53:18.869 Cannot enumerate network drives, Error:1222
2020-01-08 21:53:22.387 MultiLanguage text item not found!. ( 10004,s,1 )
2020-01-08 21:53:26.823 Saving configuration file : "C:\Users\Gord\AppData\Roaming\MultiCommander\Config\FSLocal.xml"
2020-01-08 21:53:30.557 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:73796E6F-6473-6D00-0000-0011328dda97) (Not a folder)
2020-01-08 21:53:30.557 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:8323e27e-2020-f2d1-84e5-ed1f45cb0357) (Not a folder)
2020-01-08 21:53:30.558 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.WCN//4fc7cafb-24b2-556d-8b03-1100cd91317e) (Not a folder)
2020-01-08 21:53:30.558 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:73796E6F-6473-6D00-0000-001132221297) (Not a folder)
2020-01-08 21:53:30.558 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:65748354-572D-31BC-4D1C-3C1E0416F93F) (Not a folder)
2020-01-08 21:53:30.558 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:00113222-1297-0011-9712-971222321100) (Not a folder)
2020-01-08 21:53:30.558 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.SSDP//uuid:390c46cb-573f-1147-0080-0005cdf97c26) (Not a folder)
2020-01-08 21:53:34.562 Enumerating network 'Server'  : Found (::{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\Provider\Microsoft.Networking.WSD//urn:uuid:564e4233-5030-3538-3530-fc3fdb5302ee) (Not a folder)

[Mathias (Author)]

It finds a lot of "other" devices. but that are not normal network shares. (Maybe some drivers/program is missing that expose them as normal devices?)
Are you sure that you access the as normal UNC path like  "\\server\share" ?
You can try to use their IP to access them too "\\0.0.0.0"

[av8ing]

Yes, I can access through UNC path, here's a screen shot. What I just realized is that through windows explorer, it will open the device in a web browser through its IP address, not inside explorer itself. However , if the shared folder has been mapped as a network drive, it will open it in explorer and it shows in MC as a drive.

[av8ing]

Well I did find a workaround. I overwrote the Network cache file from my surface. I can now directly access all the network devices, however I still cannot figure out why MC cannot see them on a network scan. Doesn't make much sense to me.