11/19/2023 0 Comments Mucommander unable to load smb shareApplied Samba 3.0.37 - OK, had to use muCommander to copy it overīy following the directions offered by Krishkal it was ultimately successful. Applied Samba 3.0.25 with AD support - Not OK, could not access from PCħ. Re-applied 1.12 - OK web interface backĦ. Applied telnet enabled firmware 1.12 using English updater - OKĤ. Read the following which have links to the downloads hightlighted below.ġ. Net use s: \192.168.1.I did have some problems getting this approach to work on a TS-1.0TGL/R5, which sound similar to those jarrodb has experienced. Next, in “Control Panel”, “All Control Panel Items”, Creditential Manager", click on “Windows Credentials” then the NAS name, then Edit, and enter the same Computername\user, and the password for the NAS.īut, I have had other Samba devices that just won’t map in Windows 10 no matter what I try.įor those, I just use the net commands in a batch file. Select the drive letter and enter \Nst-600nu\public. Right click on Network and select “Map Network Drive” In Windows 10, the computer needs to manage accounts I set User Accounts, but I never use Homegroups In Network and Sharing Center/ Advanced Sharing Settings:Įnable file sharing with devices that 40- or 56-bit encryption (Note, I was mapping the guest account on the NAS with no password) Here are some notes from my ordeal of mapping an NAS to my Windows 10 PC. Windows does everything to make it difficult to map any network drive. I must say, I am quite excited about giving HA a go in replacing my proprietary ADT system with $40 monthly service fee, but I need to get beyond this head bashing some how. local host Processing section “” Processing section “” Processing section “” Processing section “” Processing section “” check_ntlm_password: authentication for user -> -> succeeded Failed to fetch record! pcap cache not loaded No builtin backend found, trying to load plugin tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory daemon_ready: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections waiting for connections Processing section “” Processing section “” Processing section “” Processing section “” Processing section “” check_ntlm_password: Authentication for user -> FAILED with error NT_STATUS_NO_SUCH_USER, authoritative=1 Auth: user at with status workstation remote host mapped to. ** Samba partial LOG after restart and map network drive attempt :**Īdded interface eth0 ip=192.168.1.127 bcast=192.168.1.255 netmask=255.255.255.0 INFO: Profiling support unavailable in this build. On my windows network I have “All Networks” with options set for “turn on sharing to anyone” and “use 128-bit encryption”. I try to map network drive to \192.168.1.127\hassio", type in name/password, but fails saying can’t find. But hassio file share does not show up on my Windows 10. I add/modify Samba config, only changing username/password/interface,then save and start. My router is set to issue fixed IP 192.168.1.127 with 81 port forwarding. Rather than bore with sorted details of this past week, I am starting clean once again, with 88.1 on new Pi B+ and 64k SD, and running headless. One time with duckdns/ssl/Samba even working, but then upgraded from 87 to 0.88.0 and could no longer log into HA any more. I have reformatted SD starting from scratch a dozen times and have gotten to various levels of success. I am a newbie at this HA stuff, and just trying to follow instructions that appear current.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |