Can only access some shares through wired connection, not wireless

I'm running Windows 10. A few days ago, I enabled Hyper V on it and I've had some networking problems ever since. I've subsequently disabled Hyper V but the problems persist.

I think it's just one root problem but there are two symptoms:

1. I have a WD My Cloud device on my network. It's name is WDMyCloud. Up until now, I've been able to access it by going to \\wdmycloud. But now when I try that (I have a desktop shortcut that I normally use), I get an error: "Windows cannot access \\wdmycloud" and the details say "Error code 0x80070035. The network path cannot be found." However, I CAN access the device by its IP address ... just not by its name.

2. My iPad cannot see the shares on my computer.

When I disable the wireless network and plug a network cable in, both problems go away. But as soon as I'm back on wireless, I have the problems again.

I notice that on my wireless network card status, NetBIOS over Tcpip Enabled is No. Even if I go into the properties of the card and change that to Yes, it still says No in the status.

I've tried flushing the DNS cache, re-installing the network adapter, updating the network adapter, and a network reset but the problems persist.

The problems are the same on both my home network and my work network and there have been no changes to the router setup in either location.

Any suggestions would be greatly appreciated.
jrmcanada2Asked:
Who is Participating?
 
Dr. KlahnPrincipal Software EngineerCommented:
I get an error: "Windows cannot access \\wdmycloud" and the details say "Error code 0x80070035. The network path cannot be found."

Suggest looking at the share properties.  Unless it was explicitly configured for a static IP on your LAN, the WD probably uses DHCP.  It would not be unusual for it to lose its lease at some point, request a new one, and could now be on some other IP address.

When I disable the wireless network and plug a network cable in, both problems go away. But as soon as I'm back on wireless, I have the problems again.

Carefully compare all settings on both the hardwire interface and the wireless interface, including the advanced settings.  There is going to be a difference somewhere.  It might be a missing protocol, missing service or missing client, and it is easy to overlook these as they do not show up in TCP/IP settings.  For example, in the configuration shown below, Microsoft File and Printer Sharing is not enabled on the "Giant Toad" interface and there is no way that machine could use a shared device on that network, even if the device is present and working 100%.

Configuration missing MS Networking
0
 
jrmcanada2Author Commented:
It worked
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.