Windows 10: Cannot map Samba disk

Discus and support Cannot map Samba disk in Windows 10 Network and Sharing to solve the problem; Hi all, i think I've try everything *Smile so maybe anybody help here *Smile We have SAMBA disk under Linux, mapping disk and entering access data... Discussion in 'Windows 10 Network and Sharing' started by kyssling, Jan 28, 2020.

  1. kyssling Win User

    Cannot map Samba disk


    Hi all, i think I've try everything *Smile so maybe anybody help here *Smile

    We have SAMBA disk under Linux, mapping disk and entering access data from Windows 7, Windows 8 works without problems (from work, home ...). Under Windows 10Pro map disk now not working . (some Linux update has been finished and the access does not work - unfortunately I do not have more info yet from our external company).

    Previously, it was install SMB1 support in Win10 and mapdisk worked normally, now it appears after entering the access data: error code 0x80070035 - The network path was not found.

    I tried to disable FW, AntiVir, uninstall and reinstall SMB1 support, and then on the lab : (NTLM authentication change, Enable Insecure Guest Logons, Netbios over TCPIP ... everything from here Windows OS Hub | IT knowledge base for system administrators error-code-0x80070035-network-path-not-found-windows-10 /).

    I found a single record in the SMB log ... I changed IP numbers:
    SMB client log (Microsoft-Windows-SMBClien
    Could not establish network connection.
    Error: I / O request was canceled.
    Server name: 37.AAA.BBB.CCC
    Server address: 37.AAA.BBB.CCC: 445
    Instance name: \ Device \ LanmanRedirector
    Connection Type: Wsk

    Do you have any tips for try ? Thank you!

    :)
     
    kyssling, Jan 28, 2020
    #1

  2. Windows 10 Pro no longer connects to Samba Share on Linux Workstation

    Hello Simon,

    To better assist you, kindly provide the following information:

    • What version of Samba Share are you using?
    • What troubleshooting steps have your done so far?
    We look forward to your response.

    Thank you.
     
    Kenneth Mon, Jan 28, 2020
    #2
  3. Disk management console view is not up-to-date

    i dont know how to fix your disk management, but i can fix your partition problems...




    open up Command Prompt with admin rights. (Right click, run as admin)


    enter in
    DISKPART
    list disk

    then find the Disk number for your Raid array... lets call it number 7 ( you can tell what disk is what by the total size)
    type in

    Select Disk 7
    List Partition (will give you a list of all the partitions..)
    Select Partition 1 (im assuming you only have 1 partition on Disk 7) repeat this step if you have more partitions.
    ASSIGN


    that should get the array up and running ready to use.


    EDITED.

    any problems, post back ^^


    Still EDITING *Stick Out Tongue Cannot map Samba disk :p

    side question, have you tried restarting the PC?
     
    slyfox2151, Jan 28, 2020
    #3
  4. Cannot map Samba disk

    Setting up SAMBA

    For some reason my windows server will not connect to my linux server running centos6.3

    Here is what it does:


    Cannot map Samba disk screen%20cap.png


    and here is my samba share config

    Code: cat /etc/samba/smb.conf |less # Make sure not to do that on system directories as they may already have # been marked with othe SELinux labels. # # Use ls -ldZ /path to see which context a directory has # # Set labels only on directories you created! # To set a label use the following: chcon -t samba_share_t /path # # If you need to share a system created directory you can use one of the # following (read-only/read-write): # setsebool -P samba_export_all_ro on # or # setsebool -P samba_export_all_rw on # # If you want to run scripts (preexec/root prexec/print command/...) please # put them into the /var/lib/samba/scripts directory so that smbd will be # allowed to run them. # Make sure you COPY them and not MOVE them so that the right SELinux context # is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts # #-------------- # #======================= Global Settings ===================================== [global] # ----------------------- Network Related Options ------------------------- # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = HORSLEY server string = Samba Server Version %v netbios name = Mediaserver : ; interfaces = lo eth0 10.0.1.1/2 ; hosts allow = 127. 192.168.12. 192.168.13. # --------------------------- Logging Options ----------------------------- # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/log.%m # max 50KB per log file, then rotate max log size = 50 # ----------------------- Standalone Server Options ------------------------ # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = user passdb backend = tdbsam # ----------------------- Domain Members Options ------------------------ # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job # # Domain Logons let Samba be a domain logon server for Windows workstations. # # Logon Scrpit let yuou specify a script to be run at login time on the client # You need to provide it in a share called NETLOGON # # Logon Path let you specify where user profiles are stored (UNC path) # # Various scripts can be used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts # ; security = user ; passdb backend = tdbsam ; domain master = yes ; domain logons = yes # the login script name depends on the machine name ; logon script = %m.bat # the login script name depends on the unix user used ; logon script = %u.bat ; logon path = \\%L\Profiles\%u # disables profiles support by specifing an empty path ; logon path = ; add user script = /usr/sbin/useradd "%u" -n -g users ; add group script = /usr/sbin/groupadd "%g" ; add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /n ohome -s /bin/false "%u" ; delete user script = /usr/sbin/userdel "%u" ; delete user from group script = /usr/sbin/userdel "%u" "%g" ; delete group script = /usr/sbin/groupdel "%g" # ----------------------- Browser Control Options ---------------------------- # # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply # # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable # # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; local master = no ; os level = 33 ; preferred master = yes #----------------------------- Name Resolution ------------------------------- # Windows Internet Name Serving Support Section: # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both # # - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server # # - WINS Server: Tells the NMBD components of Samba to be a WINS Client # # - WINS Proxy: Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. # # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. ; wins support = yes ; wins server = w.x.y.z ; wins proxy = yes ; dns proxy = yes # --------------------------- Printing Options ----------------------------- # # Load Printers let you load automatically the list of printers rather # than setting them up individually # # Cups Options let you pass the cups libs custom options, setting it to raw # for example will let you use drivers on your Windows clients # # Printcap Name let you specify an alternative printcap file # # You can choose a non default printing system using the Printing option ; load printers = yes ; cups options = raw ; printcap name = /etc/printcap #obtain list of printers automatically on SystemV ; printcap name = lpstat ; printing = cups # --------------------------- Filesystem Options --------------------------- # # The following options can be uncommented if the filesystem supports # Extended Attributes and they are enabled (usually by the mount option # user_xattr). Thess options will let the admin store the DOS attributes # in an EA and make samba not mess with the permission bits. # # Note: these options can also be set just per share, setting them in global # makes them the default for all shares ; map archive = no ; map hidden = no ; map read only = no ; map system = no ; store dos attributes = yes #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes ; valid users = %S ; valid users = MYDOMAIN\%S ;[printers] ; comment = All Printers ; path = /var/spool/samba ; browseable = no ; guest ok = no ; writable = no ; printable = yes # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /var/lib/samba/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ; [Profiles] ; path = /var/lib/samba/profiles ; browseable = no ; guest ok = yes # A publicly accessible directory, but read only, except for people in # the "staff" group ; [public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; writable = yes ; printable = no ; write list = +staff [Movies1] path = /Movies1 writeable = yes browseable = yes valid users = administrator [Movies2] path = /Movies2 writeable = yes browseable = yes valid users = administrator [Movies3] path = /Movies3 writeable = yes browseable = yes valid users = administrator [Movies4] commnet = Public Storage path = /Movies4 browseable = yes guest ok = yes writable = yes printable = no[/quote] What am I doing wrong? I've setup an administrator user ( I think) but it will not connect to the share, they show up but no access. Any ideas?
     
    freaksavior, Jan 28, 2020
    #4
Thema:

Cannot map Samba disk

Loading...
  1. Cannot map Samba disk - Similar Threads - Cannot map Samba

  2. Samba Share/ Legacy Drive Mapping not staying Connected

    in Windows 10 Gaming
    Samba Share/ Legacy Drive Mapping not staying Connected: Hello All, I have an issue where we need to map a network drive to Windows 10/11 Pro Laptops. For the Windows 10 Pro laptops, I can successfully Map the Drive letter Q: to the machine useing a net use cmd script as such. net use Q: \\192.xxx.xx.x\etc\etc /user:uname pw...
  3. Samba Share/ Legacy Drive Mapping not staying Connected

    in Windows 10 Software and Apps
    Samba Share/ Legacy Drive Mapping not staying Connected: Hello All, I have an issue where we need to map a network drive to Windows 10/11 Pro Laptops. For the Windows 10 Pro laptops, I can successfully Map the Drive letter Q: to the machine useing a net use cmd script as such. net use Q: \\192.xxx.xx.x\etc\etc /user:uname pw...
  4. Samba Share/ Legacy Drive Mapping not staying Connected

    in Windows 10 Network and Sharing
    Samba Share/ Legacy Drive Mapping not staying Connected: Hello All, I have an issue where we need to map a network drive to Windows 10/11 Pro Laptops. For the Windows 10 Pro laptops, I can successfully Map the Drive letter Q: to the machine useing a net use cmd script as such. net use Q: \\192.xxx.xx.x\etc\etc /user:uname pw...
  5. Mapped Samba drive does not reconnect

    in Windows 10 Network and Sharing
    Mapped Samba drive does not reconnect: Out of the 15 computers i have in our office, 4 do not reconnect to our UNIX server via Samba upon log on I have SMB 1.0/CIFS Client and Server enabled on all machines. 4 do not reconnect on startup, not sure why only 4, but that is the case. This is a public drive on our...
  6. Cannot access Samba share

    in Windows 10 Network and Sharing
    Cannot access Samba share: Hi, I have a few Windows 10 computers and some linux computers on my network. I use Samba to enable sharing between the Windows and Linux computers. On one of the Windows computer I have a Storage Spaces drive set up as a Samba share. I can access some of the folders on this...
  7. Samba connectivity

    in Windows 10 Network and Sharing
    Samba connectivity: I'm still working with a problem I've mentioned here before: my Windows boxes have lost connectivity to my Samba box since adopting Win 10. There are dozens of flavors of this problem discussed online, and dozens of solutions, none of which have worked for me. Describing...
  8. Cannot connect to SAMBA shares on CENTOS7

    in Windows 10 Network and Sharing
    Cannot connect to SAMBA shares on CENTOS7: Hello everyone, I'm having this very annoying issue with samba shares. The server is running on a CentOS 7 distro with samba-4.1.12-23.el7_1.x86_64. My Windows 10 build is 10240. The shares are visible but when I try to connect it waits a while and then gives me this...
  9. SAMBA share visible in Explorer, but cannot accress

    in Windows 10 Network and Sharing
    SAMBA share visible in Explorer, but cannot accress: I have SAMBA shares on a debian server. I can see the shares in Explorer. When I doubble click I am asked for credentials, but when I enter the correct (more than double and triple checked) credentials I get an error indicating that the error is due multiple connections....
  10. Win10ProN cannot connect to samba network share

    in Windows 10 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 issue. Every time I try to...