Link to home
Start Free TrialLog in
Avatar of Dean Egner
Dean EgnerFlag for United States of America

asked on

Windows 10 X64 Home can't see server shares by name when user first tries for the day.

I have a client in a non-domain Windows server environment.  Every morning, one of the workstations, running Windows 10 Home Edition X64, patched to 1803, can't see the shares on either of the two servers.  The persistent share connection returns a "Cannot access \\server\share".  I can get to the shares if I put in the IP address but not by name.  I can browse the internet with no problem.  Once I ping the servers IP, I can then get to the server shares by name.  We have verified that the ethernet card has the "allow the computer to turn off this device to save power" is disabled.
Any thoughts on what else may cause this?
Thanks
SOLUTION
Avatar of John
John
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bbao
it should be a name resolving issue.

make sure you have NETBIOS over TCP/IP enable for the network adapter in use, also make sure IPv6 is in use. you may simply run Home Group troubleshooting wizard to fix the issue.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Dean Egner

ASKER

I am planning this anyway so will push the schedule up.  Thanks for the advice!
Upgrading to Windows Pro was what I suggested in the first post here.
Hello Dean, Thanks for following up. I do appreciate you doing this.