SMB problem : no shared directories / files on network

[Testeur 1970]

Hello,

I am using Alt-F Rc5 for few months on a 320 LW and all was working fine. I just noticed few days ago that My NAS can not be seen on my home network. Samba is working fine and I have shared two directories in Samba. I can connect to the NAS normally with Filezilla and via Firefox. In Service/Network , Samba seems to run normaly. 

My /etc/samba/smb.conf is :

 

[global]

        server string = DNS-320L-02788C NAS

        map to guest = Bad User

        passdb backend = smbpasswd

        username map = /etc/samba/smbusers

        syslog only = Yes

        max log size = 32

        enable core files = No

        socket options = IPTOS_LOWDELAY TCP_NODELAY

        hosts allow = 127. 192.168.1.0/255.255.255.0

        use sendfile = Yes

        print command = lpr -P %p %s; rm %s

[Printers]

[Printers]                                          

        path = /var/spool/samba                     

        guest ok = Yes                              

        printable = Yes                             

        use client driver = Yes                     

        browseable = No                             

                                                    

[Images]                                            

        comment = Images folder                     

        path = /mnt/sda2/Images                     

        public = yes                       

        available = yes                    

        read only = yes        

        inherit permissions = yes

                                 

[Backup]                         

        comment = Backup Area    

        path = /mnt/sdb2/Backup  

        public = yes             

        available = yes          

        read only = yes          

        inherit permissions = yes

I had a look to  /var/log/samba/log.smbd and found this log :

[2017/01/04 20:34:50.805086,  0] smbd/process.c:79(srv_send_smb)
  Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2017/01/04 20:35:00.792989,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
[2017/01/04 20:35:00.803093,  0] lib/util_sock.c:680(write_data)
[2017/01/04 20:35:00.803730,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Transport endpoint is not connected
[2017/01/04 20:35:00.804613,  0] smbd/process.c:79(srv_send_smb)
  Error writing 4 bytes to client. -1. (Transport endpoint is not connected)

 

AS told, Samba was working fine. Can this error explain my problem and if yes how can I solve it ?

Thank you for your help ans happy new year.

[Nave N]

Any update on this issue? I am running into a similar problem. I have a DNS-323 Revb1 and it has been working with R4 alt-f for years. Recently I cannot connect to the SMB shares from multiple windows computers. I upgraded the NAS to R5, I have reset the settings and re-set up the shares but I still cannot connect to the SMB share. The log files look the same as OP. I cannot figure out whats going on.

[João Cardoso]

On Sunday, 29 January 2017 22:51:22 UTC, Nave N wrote:

Any update on this issue?

No, not enough info for trying anything (apart from a duplicated '[Printers]' line)

 

I am running into a similar problem. I have a DNS-323 Revb1 and it has been working with R4 alt-f for years. Recently I cannot connect to the SMB shares from multiple windows computers.

No other changes? MS-Win changes? New PC with win-10/11/12/13?

Does ftp works?

 

I upgraded the NAS to R5,

Before or after the above issue? Have you applied the "RC5 network corruption fix"?

 

I have reset the settings and re-set up the shares but I still cannot connect to the SMB share. The log files look the same as OP. I cannot figure out whats going on.

Neither me without enough info. System->Utilities->Logs, "System Configuration" (generated only at boot time) and System and Kernel Logs (current)

[Nave N]

On Monday, 30 January 2017 12:06:40 UTC-5, João Cardoso wrote:

On Sunday, 29 January 2017 22:51:22 UTC, Nave N wrote:

Any update on this issue?

No, not enough info for trying anything (apart from a duplicated '[Printers]' line)

I will post more information when I get home tonight. 

 

I am running into a similar problem. I have a DNS-323 Revb1 and it has been working with R4 alt-f for years. Recently I cannot connect to the SMB shares from multiple windows computers.

No other changes? MS-Win changes? New PC with win-10/11/12/13?

Does ftp works?

No other changes, I can ping the NAS from my PC, I can SSH to it, I can get to the web site to configure it. 

 

I upgraded the NAS to R5,

Before or after the above issue? Have you applied the "RC5 network corruption fix"?

I applied the fix (ethtool) after upgrading the firmware to RC5 

 

I have reset the settings and re-set up the shares but I still cannot connect to the SMB share. The log files look the same as OP. I cannot figure out whats going on.

Neither me without enough info. System->Utilities->Logs, "System Configuration" (generated only at boot time) and System and Kernel Logs (current)

I will post the logs tonight when I get home. 

[Nave N]

I am just going to attach the config and log files to this ticket.

Any more information or steps to troubleshoot please let me know. I appreciate any help.


Cheers,

Nave

[João Cardoso]

On Wednesday, 1 February 2017 05:08:05 UTC, Nave N wrote:

I am just going to attach the config and log files to this ticket.

Any more information or steps to troubleshoot please let me know. I appreciate any help.

I think that you have a network problem.

It seems that you have not yet "saved settings" after the "long >20secs reset", as the system log shows:

  loadsave_settings: empty or no file  found!

And we also see that 'dropbear' is regenerating its keys and sslcert its certificates

  Starting sslcert: Creating SSL self-signed certificate... OK.

  urandom: Missing random-seed

  dropbear: generating rsa key...  

So you should run the first login wizard and "save settings", which will keep the box with a know "identity" and allow us to follow the track from the point where we left it before.

-in the system log at boot, we see that DHCP was used and an IP of 192.168.1.170 obtained:

  udhcpc[384]: (21:53:19) Sending select for 192.168.1.170...

  udhcpc[384]: (21:53:19) Lease of 192.168.1.170 obtained, lease time 7200

  user.debug rcS: (21:53:19) IP from dhcp server

  udhcpc: (21:53:19) Deconfiguring eth0

  udhcpc: (21:53:19) Renew: Using 192.168.1.170 for 7200 seconds

-But in the system configuration, IFCONFIG and HOSTS section we see that 192.168.1.80 is being used by the box. What changed that? Have you assigned a static IP using the Set->Host webUI meanwhile? Restart samba afterwards?

What is the contents of /etc/network/interfaces? Does /Alt-F/etc/network/interfaces exists? (don't create it, only see if it exists)

The samba (smbd/nmbd) errors/warnings seems to be related with network problems, don't know if caused by the above.

You referred that the network shares not appearing issue started while still in RC4, so try to remember what happen at that time -- a new router? a new PC with win-xx? reusing an old win-XP box? What OSs are you using? Can you power off them all but one (what its IP and OS?), and try to diagnose the situation?

I can't see anything wrong on smb.conf, so lets assume that it's OK and try to diagnose the network. 

[Nave N]

I did a long reset as a step to try and fix this issue. It defaulted to DHCP, I found the new address and manually set the IP to 192.168.1.80 (which is outside of our DHCP pool to avoid conflicts). I have saved settings since then.

I cannot remember exactly when the issues started but recent changes to our home does include a new router, I can put the old router back and see if that resolves anything. Other than the new router we haven't added a new computer or wireless device. We have windows 10 on all of our PCs, no windows XP machines, android phones and a few chromecasts.

I will setup the old router on an isolated network with one windows 10 PC and see if it works.

I'll let you know how it goes, if you have any other ideas let me know.

Cheers!

[João Cardoso]

Interestingly enough (?) I had a "Transport endpoint is not connected" error on the smb log in one of my nas, and other PCs on the net were unable to browse it (and other samba-based nas). I think that the inability for the PCs to browse the network was due to the fact that the nas nmbd was a local master browser.

In any case, stopping samba ('rcsmb stop'), removing its cache files under /var/cache/samba ('rm -rf /var/cache/samba') and restarting samba ('rcsmb start') restored the proper behaviour. The issue might be due to corrupted samba tdb files.

A reboot should be enough to "solve" that also, as /var/cache is normally in RAM, not on disk, and disappear after a poweroff or reboot. Unless if by some hazard it is stored on disk -- if /Alt-F/var/cache/samba exists the files will survive. Can that be your case?

Under Alt-F those samba files are not essential to be preserved, although in disk-based system they should be preserved between reboots.

Just a hint...

[Nave N]

Hmmm okay, I stopped the process removed the cache files and restarted and this showed up in the logs:

 creating lame upcase table
[2017/02/03 21:30:10,  1] lib/util_unistr.c:128(load_case_tables)
  creating lame lowcase table
[2017/02/03 21:30:10,  0] smbd/server.c:1143(main)
  smbd version 3.5.22 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2010
[2017/02/03 21:30:12.164829,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
[2017/02/03 21:30:12.165957,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
[2017/02/03 21:30:12.166976,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
  account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
[2017/02/03 21:30:12.165957,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
[2017/02/03 21:30:12.166976,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
[2017/02/03 21:30:12.167981,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum password age), returning 0
[2017/02/03 21:30:12.168981,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum password age), returning 0
[2017/02/03 21:30:12.169983,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout duration), returning 0
[2017/02/03 21:30:12.170983,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count minutes), returning 0
[2017/02/03 21:30:12.171986,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout attempt), returning 0
[2017/02/03 21:30:12.172988,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect time), returning 0
[2017/02/03 21:30:12.174183,  1] lib/account_pol.c:325(account_policy_get)
  account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse machine password change), returning 0

I still can't access the shares,