javitu / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 2 forks source link

SMB sharing not always working #1405

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. upgrade to firmware 3.4.3.8-088 and above

What is the expected output? What do you see instead?
- able to browse SMB share in windows envirroment.
- error message in PC when trying to access SMB share: "device not accessible"

What version of the product are you using? On what operating system?
RT-N56U
3.4.3.9-091

Please describe the problem as detailed as it's possible.

Since the upgrade, I still see the RT-N56U SMB share in my network neighborhood 
on Windows 7/8 machines but I cannot access it; returns "device not accessible" 
error either with name or IP.

I found a way to fix it for a moment:
- turn off SMB & FTP.
- remove all users created.
- reboot RT-N56U
- enable SMB & FTP
- recreate user accounts
- can now access share

However, this will work for maybe a day or two until I get the same error and 
have to go thru these steps again...

Some configurations:
Access with accounts
Master Browser disabled (running in AD network)
LLTD enabled
WINS disabled
Device set in AP mode

Original issue reported on code.google.com by julioqc47 on 17 Jan 2015 at 3:30

GoogleCodeExporter commented 8 years ago
I also have this or a similar issue and I see this in the system log 

Feb 15 18:43:58 smbd[1440]: 
Feb 15 18:43:58 smbd[1441]: 
Feb 15 18:43:58 smbd[1442]: 
Feb 15 18:44:02 smbd[1443]: 
Feb 15 18:44:02 smbd[1444]: 
Feb 15 18:44:04 smbd[1445]: 
Feb 15 18:49:39 smbd[1455]: 
Feb 15 18:49:39 smbd[1456]: 
Feb 15 18:49:44 smbd[1457]: 
Feb 15 18:49:44 smbd[1458]: 
Feb 15 18:49:44 smbd[1459]: 
Feb 15 18:49:44 smbd[1460]: 
Feb 15 18:49:44 smbd[1461]: 
Feb 15 18:49:44 smbd[1462]: 
Feb 15 18:49:46 smbd[1463]: 
Feb 15 18:49:47 smbd[1464]: 
Feb 15 18:49:47 smbd[1465]: 

I can fix the issue instantly by changing the value in Advanced Settings > USB 
Application > Common Setting > Maximum Login User and changing the value to 
something different and back. The share is then immediately working on the 
client PC.

Original comment by sdja...@gmail.com on 15 Feb 2015 at 6:54

GoogleCodeExporter commented 8 years ago
I confirm I get the sane log traces. I will try what you do and see if I starts 
working again. Appears much faster then what I found as a workaround!

Original comment by julioqc47 on 15 Feb 2015 at 11:15

GoogleCodeExporter commented 8 years ago
Changing the "Max user" value works for me as well. Also, i've noticed the 
problem occurs mostly after a reboot of the device (hard or soft).

Original comment by julioqc47 on 2 Mar 2015 at 5:13