NAS drive showing empty folders after PC reboot

Jeremy Johnson
Jeremy Johnson used Ask the Experts™
on
Recently our Buffalo Linkstation NAS drive is showing empty folders after PC restart, the only fix seems to be to disconnect then re-map the network shares.

Buffalo has suggested using the IP instead of host name but the hasn't helped.

Issue occurs on Windows 7 and 10, began about 2 weeks ago. No prompt to enter username/password or error message.

Any suggestions most welcome.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Paul MacDonaldDirector, Information Systems

Commented:
How are the drives mapped?  Script?  AD GPO?  Does a script run after every reboot?

Author

Commented:
Hi Paul,

Thanks for your response.

2 'shares' mapped from 1 drive, done manually through widows explorer. No scripts or active directory.

Been working find for years until recently.

Thanks,
Jeremy

Commented:
Do they stay empty or do the eventually fill?  

I have seen this on my Buffalo Linkstation NAS as well right after booting the PC but seems to go away after a short time. Given all the crap Windows goes through it may just need some time.

I have also found that if I put a shortcut link to the drives on the desktop, and just right click the shortcut to bring up its menu (don't have to click anything), the drive folders fill quicker.  It is annoying.

If you open a new desktop file window and type \\MyNAS\Share\ using the name or the IP, does that window show filled?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Paul MacDonaldDirector, Information Systems

Commented:
As Owen suggests, I wonder if this isn't just a timing issue.  It may be your network connection is taking a little longer to start (for whatever reason - firewall, anti-virus, driver, etc); and because the NAS won't be available until the network connection is finalized, the shares may appear empty or broken for a short while after booting.

Does it help to wait 60 or 120 seconds after you boot before trying to access the shares?  You could certainly create a script that re-maps the shares each time you boot, but - as you say - that seems like it should be unnecessary.

Author

Commented:
Thanks for the suggestions.

Waiting doesn't seem to help, neither does the desktop shortcut.

\\MyNAS\Share\  - this does bring up the prompt to enter username/password and then the folder contents can be viewed but the mapped Network Location links still show blank after this and need to be disconnected and re-mapped again each time.
Paul MacDonaldDirector, Information Systems

Commented:
Is it possible the "permanent" maps use a username or password that is no longer valid?

Commented:
Question: Is the NAS rebooting as well? Or just the PC?

Also, have you mapped the folders as a network drive, or just do an mount?

I solved this on mine by mapping each folder as a network drive. These do remount and connect at startup.  (I am assuming you have seen this: https://www.buffalotech.com/knowledge-base/mapping-a-drive-to-a-buffalo-nas-in-windows)

Author

Commented:
Thanks, I suppose it could be invalid passwords but strange that it keeps happening with every PC reboot.

Haven't been rebooting the NAS drive. The folders were mapped as network drives.

I've actually found a potential solution is from Computer, right click > Add a network location, then add as a custom network location using the IP and now it seems to prompt for password after each reboot!

Commented:
If you think bad password, disconnect the network drive point, and add them back again. That should fix that problem if it is a problem.
Disconnecting hasn't helped with the mapped network drives. I've tried also removing the saved passwords from windows Credential Manager but still the same issue.

The work around of using custom network locations seems to be the best solution I have found, still a mystery as to why this have started happening.

Thank you both for your suggestions.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial