network not showing nas drives

Check the NAS for any settings like WINS Server and turn that on. Another setting that might also help is upnp.

If that doesn't help, add the NAS' IP's to the hosts files of your PC's.

Hello,

The Macs use either SMB or AFP to see other devices on the network I believe.  The Macs should be in the same workgroup or domain as the Windows PCs.  Also, the file sharing services need to be turned on for the Macs to be visible as well.

On the Macs, under System Preferences, go the Sharing page.  You may have to enter admin credentials to do this part.  Highlight File Sharing and check the Box for it.  Then on right, click Options, and then check the box for Share files and folders using SMB (and maybe AFP too).  At the bottom of that window, there should be a checkbox next to the account that will be shared.

To access this share from windows, you will need to enter the password for the Mac account.

As for the NAS, it should too be in the same workgroup or domain as Windows PCs.

Same workgroup.  AFP and SMB turned on.  Folders are shared.

I used to be able to see everything on pcs.  I install some software from WD for cloud NAS.  ever since then the network hasn't shown the drives.

Mac has file sharing on and shared with the accounts setup on pcs.

If I type //rt-ac66u  or //ls-cloud or //nas-backup in the windows start button search box.  I can access these drives.  It is just annoying that they aren't listed.  You can see that I mapped them.  I can access the macs if I point to their ipaddress.

I have turned off the firewall on PC and router to see if that helps but it doesn't

I am also having trouble accessing Logitech media server from outside the pc.  either by iphone app, or Logitech receiver  both of these used to work as well.  I get message that I can not connect to pc.

iphone connected after turning off firewall, but Logitech receiver still doesn't connect.  I might have to forward some ports.

Ok so sounds like the key here is the WD Cloud NAS software.  Router firewall shouldn't have any affect so be sure to leave that on.  If you uninstall it, will the drive visibility return to normal?  Which computers have this NAS software installed?

I uninstalled it and returned it. It was only on one computer I removed any registry reference to it. But I suspect it made some change on registry that I can't find that is affecting this. But then why don't the other computers see the nas drives.

This is strange.  The only other thing I can think of, on all the Windows PCs, open elevated command prompt and type

ipconfig /flushdns
ipconfig /registerdns

Select allOpen in new window

Then ping the NAS by it's hostname (ls-cloud) and see if it resolves to the correct IP.  If so, then refresh the network page to see if it has become visible.

Very Strange.  Thanks but no luck with that. either.

Did you, as I suggested, look for the wins setting on the NAS, and if there isn't such a setting, add it's IP to your hosts file?

there is no wins setting on NAS drives.  and I added it to host file.  made no difference.  

The question is where does windows explorer get it's information for the network.  I have ip scanners that have no problem finding everything on the network.  buffalo NAS navigator has no trouble finding the NAS drives.  So how does the network portion of windows explorer work.  

That it seems to me in the problem.  Then how do I fix it.

To my understanding In the old days, it was NetBIOS and WINS along with existing file shares that made devices visible in network neighborhood.

This may be a long shot, but it is the last thing I can think to try, on the Windows machines, turn off network discovery in the network and sharing center, reboot, then turn network discovery back on.

On win 7 link-layer topology discovery mapper 1/0 driver I believe.
I uninstalled it and reinstalled it

Well actually what I was thinking was the option for just network discovery.  This is a radio button in the network and sharing center from control panel.

I've done that with no help.

I see.  Well I am out of ideas, sorry I could not help.

Interesting.  So they had to be powered down instead of reboot?  Either way, glad you got it resolved.

It was the solution.  I was able to solve the problem on my own.