1. Joined : Sep 2015
    Posts : 2
    Windows 10
       12 Sep 2015 #1

    W10 won't see Linux server by name, only by IP Address


    For several weeks I have been using W10 with two Linux servers, B767 and B777. Until an hour ago, Windows Explorer saw both of them just fine and everything worked as expected.

    After a brief hiatus, I came back to the computer and it showed big red Xs next to the mapped drives on B777. Windows explorer showed everything just fine for B767.

    When I click on B777 in the network section of Windows Explorer, it responds (after running the green bar through the address area) with "Windows cannot access \\B777" and an error code of 0x80070035 (The network path was not found).

    When I click on B767 in the network section of Windows Explorer, it responds by showing the shared folders properly.

    I have a Linux workstation and a W10 laptop that both see B777 by name just fine.

    When I use an IP address to get to B777, I can see and map the shared folders.

    I can ping B777 by name just fine.

    I have rebooted both the server and the workstation and disabled anti-virus and firewall to no avail.

    I need some help from someone smarter than me.

    Thanks
      My System SpecsSystem Spec


  2. Joined : May 2015
    Central IL
    Posts : 3,079
    EL Capitan
       13 Sep 2015 #2

    There is a registry fix for Windows 8 & 10, because of changes Microsoft made with SMB, that it does not play well with Samba. You are going to be best at asking on the forum for the Linux Distro that you are using, since it is a Samaba problem. Most times it is an incorrectly created smb.conf.
      My System SpecsSystem Spec


  3. Joined : Sep 2015
    Posts : 2
    Windows 10
       13 Sep 2015 #3

    Thanks, but I don't understand how that explains why (1) it worked just fine for weeks (2) it works fine on another W10 computer, and (3) The other Linux server is recognized just fine.
      My System SpecsSystem Spec


  4. Joined : May 2015
    Central IL
    Posts : 3,079
    EL Capitan
       13 Sep 2015 #4

    delpi767 said: View Post
    Thanks, but I don't understand how that explains why (1) it worked just fine for weeks (2) it works fine on another W10 computer, and (3) The other Linux server is recognized just fine.
    Because of updates. I have had Samba break right after applying updates to a unit.

    The other problem can be the Windows machines Firewalls. There is a KDE tool to allow you to set up folder shares and also allow you to set up usernames. In reality, Samba is best for a Domain environment than a Workgroup.

    Do a search for "Samba Black Book." It is dated, but the best resource out there, same as with the info at Samba.org.
      My System SpecsSystem Spec


  5. Joined : Oct 2014
    Posts : 1,309
    win 10 Insider
       14 Sep 2015 #5

    I agree with bro67. I had the same error on one win 10 comp caused by SMB version incompatibility. It used to work then it didn't after an update. My comp had an old registry entry locking SMB to ver 2. My other comps never got answers from requests for shares to be displayed so they responded with the path not found error. And, like yours, you could ping and access via IP no.

    I am not pretending to know about Linux but just thought I would add these comments.
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
Windows Upgrade Won't start - Windows Server Update Server installed
Hi All, I've tried to run the upgrade from Windows 7 to 10. It fails with the pre-requisite as I had the WSUS 3.0 SP2 admin console installed. I uninstalled this and tried to resume but it still thinks it's installed and won't progress. I've...
Installation and Setup
BSODs in windows 10 (and 8) but not 7. (always same address?)
I never had an issue in windows 7, but when I installed windows 8 a year ago to try it out, it kept giving me BSODs, so I simply reverted to windows 7. Now with windows 10, I'm getting the same issues. Problem is, windows 10 is nice :092:. It...
BSOD Crashes and Debugging
Solved Yes, you *can* still register an email address as an Insider
I've seen a couple of comments saying you can't register as an Insider, but I just wanted to say I've done it today and it still works, just in case it helps someone. What you can't do (well not officially; I imagine there are workarounds) is...
Windows Insider
Windows Server 2016 leaks reveal Nano Server, protected VM role plans
Read more: Windows Server 2016 leaks reveal Nano Server, protected VM role plans | ZDNet
Windows 10 News
Verify your email address
When I try to download any app, "I get the prompt "Verify your email address." I originally submitted an email address and password when I set up windows 10. Now, I am sent a link directing me to a website to verify my password. The password (which...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:26.
Find Us
Twitter Facebook Google+



Windows 10 Forums