Page 1 of 4 123 ... LastLast
  1.    18 Feb 2017 #1
    Join Date : Feb 2017
    Posts : 11
    Windows 10

    Unable to See Samba Share


    Hi everyone,
    I'll try to keep it short. I have a headless ubuntu server that has a samba server. It's connected to the network with a cable (not wifi) and has a static IP. My desktop (also wired with static IP) is unable to see the samba share at all: not when I go to the network page and not when I type the IP address in. I am able to ping the ubuntu server from the windows machine and it responds.

    I have two other windows 10 PCs that can see and interact with the samba share just fine. I also have a raspberry pi that has the samba share in question automounted and it works perfectly.

    I have googled and researched this issue for hours and hours. I have tried a million things from editing my registry to turning on windows features and nothing helps. I finally re-installed windows for a fresh start and it still doesn't work!

    I'm pulling my hair out and as a hail mary I thought I'd ask if anyone could help me out,
    Thanks a million in advance.
      My ComputerSystem Spec
  2.    18 Feb 2017 #2
    Join Date : Nov 2014
    The Netherlands
    Posts : 628
    Win 10 Pro x64 1607 (Build 14393.953)

    Unable to See Samba Share


    Did you check the settings in Credential Manager - Control Panel - in Windows for your ubuntu server?
      My ComputerSystem Spec
  3.    18 Feb 2017 #3
    Join Date : Feb 2017
    Posts : 11
    Windows 10
    Thread Starter

    I remember fiddling around with that at some point in the last few weeks but don't really remember specifics. I'm willing to try pretty much anything at this point. If you tell me what to do, I'll do it
      My ComputerSystem Spec
  4.    18 Feb 2017 #4
    Join Date : Nov 2014
    The Netherlands
    Posts : 628
    Win 10 Pro x64 1607 (Build 14393.953)

    Unable to See Samba Share


    1. Go to CM and check if your server is present.
    2. If not, create a new windows credential for the server with the appropriate - exact - username and password to connect to it.
    3. For assurance reboot your PC.

    EDIT: use either static ip or the WORKGROUP name of your sever.
      My ComputerSystem Spec
  5.    18 Feb 2017 #5
    Join Date : Feb 2017
    Posts : 11
    Windows 10
    Thread Starter

    I created the "Windows Credential" with the exact name and password and I get this error when I try to connect:
    Click image for larger version. 

Name:	2017_02_18_21_49_011.png 
Views:	25 
Size:	13.0 KB 
ID:	121862
    On both of the other Windows PC's they don't have a Windows Credential and can see it just fine (weird).
      My ComputerSystem Spec
  6.    18 Feb 2017 #6
    Join Date : Nov 2014
    The Netherlands
    Posts : 628
    Win 10 Pro x64 1607 (Build 14393.953)

    Is the server set to be part of WORKGROUP like your PC's?
      My ComputerSystem Spec
  7.    18 Feb 2017 #7
    Join Date : Feb 2017
    Posts : 11
    Windows 10
    Thread Starter

    Yes, 100% yes. Just to be clear my workgroup name is LEDESMA but it's LEDESMA in the samba config and on ALL the PC's in the house, including my desktop that can't see it. I just checked spelling and it's the same.
      My ComputerSystem Spec
  8.    18 Feb 2017 #8
    Join Date : Nov 2014
    The Netherlands
    Posts : 628
    Win 10 Pro x64 1607 (Build 14393.953)

    Give me a sec, I'll hop over to my Desktop too!
      My ComputerSystem Spec
  9.    18 Feb 2017 #9
    Join Date : Nov 2014
    The Netherlands
    Posts : 628
    Win 10 Pro x64 1607 (Build 14393.953)

    Quote Originally Posted by noxsoldier View Post
    Yes, 100% yes. Just to be clear my workgroup name is LEDESMA but it's LEDESMA in the samba config and on ALL the PC's in the house, including my desktop that can't see it. I just checked spelling and it's the same.
    Like this?

    Click image for larger version. 

Name:	ScreenCap 2017-02-18 at 23.05.53.jpg 
Views:	24 
Size:	32.0 KB 
ID:	121867
      My ComputerSystem Spec
  10.    18 Feb 2017 #10
    Join Date : Feb 2017
    Posts : 11
    Windows 10
    Thread Starter

    The name of the Workgroup is LEDESMA.
    The location of the server is \\LEDESMA-SERVER

    I setup a WC for \\LEDESMA-SERVER and it didn't work. Then just to be thorough I setup one for \\LEDESMA but it didn't help

    I also enabled guest logins on the samba config file and it didn't do anything.
      My ComputerSystem Spec

 
Page 1 of 4 123 ... LastLast


Similar Threads
Thread Forum
Creating a samba share in windows 10
I've been using unauthenticated samba share on my computer for well over a decade using windows 7, vista, and XP (and maybe even further back) to network with various devices in another room via an ethernet cable. I believe Microsoft removed...
Network and Sharing
Issues seeing Samba share from Kubuntu server under Windows 10
All, In my home network I have several computers. A Kubuntu Linux server, a windows 10 laptop and a window 8.1 desktop. Under Kubuntu I have setup several Samba shares for things like videos/photos/music, etc. From the Kubuntu side everything...
Network and Sharing
Win10ProN cannot connect to samba network share
Hey folks, I've got an issue that's been bugging me since windows 7. I've got a debian server on my network running samba and plex. I usually add media to it through samba from my windows computers. Only now with my laptop, I'm having a strange...
Network and Sharing
Samba share doesn't work
Hi, I have Vbox with Ubuntu Server 14.04 LTS installed on it. My host is Win 10 (Version 10.0.10240 Build 10240). I've tried to get my samba share working for the whole day. I asked in #Windows, #ubuntu, #samba, #php, everywhere. I've googled...
Network and Sharing
BSOD mounting ISO natively from samba share
To reproduce: 1) You need a network share drive on another device that is mapped locally as a drive. 2) Place an ISO image of some kind in a location on that shared drive. 3) Attempt to open the ISO natively (double-click or right click->...
BSOD Crashes and Debugging
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 17:08.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums