I have three Dell XPS desktops (two 8700 and one 8300) and two Buffalo NAS units connected to my home network. When I run Buffalo NAS Navigator V 2.82 (the latest version) on one of the 8700s is see the following communication errors from both NAS units (the other 8700 desktop shown no errors):
When they errors are expanded they are "drive info not returned" and "error info not returned." I can browse the shares on both units, both through Navigator and my Windows 10 PC with no problems. I can create and delete files just as I always have and I can log into then through the browser function and no errors are reported. Clearly both units are operating correctly, or so it would appear. I've uninstalled NAS Navigator and reinstalled but the communication error notices persist. I have the latest version of Navigator (2.82) and the firmware on both NAS units is current. The last time I used NAS Navigator on 4/13 there were no communication errors. I'm running Win 10 V 10586.218 on both desktops. Any thoughts about what might be causing this on one desktop and not the other and how I mighty be able to fix it?
Update: I found this event log entry from the first failure of NAS Navigator. Anyone with any additional ideas?
The latest version of NAS Navigator I have installed is 2.83.
However I am using Windows 10 x64 Pro build 10586.240
Thanks pbcopter. I downloaded 2.83 an I'll try it tomorrow morning. Maybe that will help.The latest version of NAS Navigator I have installed is 2.83.
However I am using Windows 10 x64 Pro build 10586.240
I hope it helps.
Just tried it - no joy! Dang!I hope it helps.
It must be something with the network protocols that changed after I last used it on 4/13. Odd that I have no problems with the other Dell 8700 and 8300 on the same network. I suspect the KB3147458 that was installed on the problem PC on 4/13 is the culprit.
UPDATE: I discovered that the event log entry for NasNavi that I found in my first post references (0xC0000417) an invalid C-Runtime parameter. Since I've already run SFC and although it did fine corrupted files and fixed them but did not solve this problem, it look like I'm stumped. Anyone have any ideas?
UPDATE: After doing a little more research I thought it might be a problem with the C++ Redistribution Packages so I did a repair of the 2012 and 2013 (x86 and x64) installations. That did nothing. I also have the 2008 and 2010 Redistribution Packages but there is no repair options on those.
Please keep us updated if you find a fix. I have the exact same thing happening to me. Oddly enough mine also started doing this on Monday.
Hi mrf5022. I've discovered a solution that worked for me:Please keep us updated if you find a fix. I have the exact same thing happening to me. Oddly enough mine also started doing this on Monday.
- Open Task Manager.
- Select the Startup Tab
- Find "NASNavigator" and if it is Disabled then set it to Enabled
- Do the same with "NAS Function Scheduling Application" It might not be necessary to enable this but I just did it to be consistent.
- Restart windows
NAS Navi should now find the NAS unit(s) more quickly and without experiencing error communication problems. I now remember disabling several startup items some time ago to speed up boot time. I probably never tested this one to see if it had any impact. Needless to say I'll be more carefull next time. Let me know if this works for you.
