Hi there,
First things first, happy new year to everyone here in the forum and thanks to all of you who work very hard in order to make the Asus Merlin FW possible! You guys rock!
I've been pulling my hair trying to fix a weird issue on my AC68U (384.14). The problem I'm having is that my SMB shares are not accessible after a reboot. Sometimes they start working again but only after it's been several hours since the router was powered on.
I get two different errors when trying to access them:
a) 0x80070035 the network path was not found.
and sometimes I randomly get:
b) \\10.7.7.1\share is not accessible. You might not have permission to use this network resource. Contact the administrator.... Access is denied.
I've read several other threads on this forum with similar issues, and for reference, I've already:
-Enabled SMB SMB 1.0/CIFS on my W10 computers using the "turn windows features on or off".
-Enabled SMBv1 + SMBv2 under network place (samba) share on the web UI.
-Tested with AndSMB on Android using SMBv1 and SMBv2 and the problem persists so I can't isolate it to a Windows issue. I get a "connection refused" error on the AndSMB app on Android, even though credentials are correct and, as mentioned earlier if I wait several hours after a reboot everything starts working again without any changes made on the router or computer or credentials.
-Guest access is not enabled on the SMB share options nor does it make a difference as far as resolving the issue goes.
-I'm using IP addresses for the shares instead of NetBIOS.
Additionally, I have two USB hard drives connected to the router, one ext4 which is connected to the USB 2.0 port and it's only used for entware stuff and an NTFS one which is used to store movies, music, pictures, backup stuff and so on. Neither of them is accessible via SMB.
For further reference, the smb.conf file looks like this:
and the smb.postconf file looks like this:
I've seen nothing out of place on the general log file, but I can definitely see there that the Samba_daemon is up and running.
All other services that use the external drives such as FTP and UPnP are working fine, so I know the drives themselves are not broken. I've already scanned them for errors and both of them are showing ok.
Lastly, I've tried to check if the 445 and 139 ports are opened by doing a telnet on CMD but all I get is a:
C:\Users\Owner>telnet 10.7.7.1 445
Connecting To 10.7.7.1...Could not open connection to the host, on port 445: Connect failed
C:\Users\Owner>telnet 10.7.7.1 139
Connecting To 10.7.7.1...Could not open connection to the host, on port 139: Connect failed
However, when the shares are working, I do not get such an error.
I don't see any reason why I should've to wait 4 - 5 hours after a reboot for samba to work again, and I know I'm probably missing something but it is beyond me at this point.
Any help would be really appreciated!
First things first, happy new year to everyone here in the forum and thanks to all of you who work very hard in order to make the Asus Merlin FW possible! You guys rock!
I've been pulling my hair trying to fix a weird issue on my AC68U (384.14). The problem I'm having is that my SMB shares are not accessible after a reboot. Sometimes they start working again but only after it's been several hours since the router was powered on.
I get two different errors when trying to access them:
a) 0x80070035 the network path was not found.
and sometimes I randomly get:
b) \\10.7.7.1\share is not accessible. You might not have permission to use this network resource. Contact the administrator.... Access is denied.
I've read several other threads on this forum with similar issues, and for reference, I've already:
-Enabled SMB SMB 1.0/CIFS on my W10 computers using the "turn windows features on or off".
-Enabled SMBv1 + SMBv2 under network place (samba) share on the web UI.
-Tested with AndSMB on Android using SMBv1 and SMBv2 and the problem persists so I can't isolate it to a Windows issue. I get a "connection refused" error on the AndSMB app on Android, even though credentials are correct and, as mentioned earlier if I wait several hours after a reboot everything starts working again without any changes made on the router or computer or credentials.
-Guest access is not enabled on the SMB share options nor does it make a difference as far as resolving the issue goes.
-I'm using IP addresses for the shares instead of NetBIOS.
Additionally, I have two USB hard drives connected to the router, one ext4 which is connected to the USB 2.0 port and it's only used for entware stuff and an NTFS one which is used to store movies, music, pictures, backup stuff and so on. Neither of them is accessible via SMB.
For further reference, the smb.conf file looks like this:
Code:
[global]
netbios name = *removed*
server string = RT-AC68U
workgroup = *removed*
username level = 20
unix charset = UTF8
display charset = UTF8
load printers = no
printing = bsd
printcap name = /dev/null
log file = /var/log/samba.log
log level = 0
max log size = 5
security = USER
guest ok = no
map to guest = Bad User
encrypt passwords = yes
pam password change = no
null passwords = yes
force directory mode = 0777
force create mode = 0777
max connections = 9
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE
obey pam restrictions = no
use spnego = yes
client use spnego = no
disable spoolss = yes
host msdfs = no
strict allocate = no
wide links = no
bind interfaces only = yes
interfaces = lo br0 10.7.7.1/255.255.255.0
use sendfile = yes
map archive = no
map hidden = no
map read only = no
map system = no
store dos attributes = no
dos filemode = yes
oplocks = yes
level2 oplocks = yes
kernel oplocks = no
wins support = yes
os level = 255
domain master = yes
local master = yes
preferred master = yes
enable core files = no
deadtime = 30
load printers = no
printable = no
max protocol = SMB2
smb encrypt = disabled
min receivefile size = 16384
passdb backend = smbpasswd
smb passwd file = /etc/samba/smbpasswdand the smb.postconf file looks like this:
Code:
#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
pc_replace "store dos attributes = yes" "store dos attributes = no" $CONFIG
pc_replace "socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE SO_RCVBUF=65536 SO_SNDBUF=65536" "socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE" $CONFIG
exitI've seen nothing out of place on the general log file, but I can definitely see there that the Samba_daemon is up and running.
All other services that use the external drives such as FTP and UPnP are working fine, so I know the drives themselves are not broken. I've already scanned them for errors and both of them are showing ok.
Lastly, I've tried to check if the 445 and 139 ports are opened by doing a telnet on CMD but all I get is a:
C:\Users\Owner>telnet 10.7.7.1 445
Connecting To 10.7.7.1...Could not open connection to the host, on port 445: Connect failed
C:\Users\Owner>telnet 10.7.7.1 139
Connecting To 10.7.7.1...Could not open connection to the host, on port 139: Connect failed
However, when the shares are working, I do not get such an error.
I don't see any reason why I should've to wait 4 - 5 hours after a reboot for samba to work again, and I know I'm probably missing something but it is beyond me at this point.
Any help would be really appreciated!
