I've updated my wzr-d1800h to the newest dd-wrt brainslayer Version BrainSlayer-V24-preSP2/2014/11-20-2014-r25408/.
What I want to use is the NAS functionalty with an Attached USB Stick. The Router detected the Stick correctly and mounted it sucessfuly. I configured a new samba share, with an user who has rights for access.
When I now try to connect from Windows 8.1 Client to the new created samba share I typed in the Windows Explorer Adressfield \\192.168.1.1 (this is the IP of the Router). It shows me my new share, but if I want to access, it told me the share doesn't exist. What have I done wrong?
I read some other Wiki entries that told me I have to use Optware and then install Samba 3.5. Is this the only way to solve it?
Well I seriously don't know what's up. The Virtual SSID just won't let any clients connect even waiting for hours and rebooting the router completely.
Now I find out that every time I reboot the WZR-D1800 it causes my TP-Link SG2424 to not properly route VLAN. I have to go in to the SG2424 and untag and re-tag a port.
so frustrating!
Last edited by mbze430 on Fri Feb 27, 2015 22:18; edited 1 time in total
While I'm guilty of *dirty flashing* myself, you folks are correct it is a best practice. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
[size=9]
_.-:Curently Deployed Devices:-._
Loc_1.0: R6400 -- Kong PTB 35550M 03-28-2018
Loc_2.0: R6300v2 -- Kong PTB 35550M 03-28-2018
Loc_3.0: R6300v2 -- Kong PTB 35030M 02-19-2018
Loc_4.0: R6300v2 -- Kong PTB 28600M 12-31-2015 (Radios OFF) & 5 Ubiquity UniFi APs
Loc_4.1: E4200 -- BrainSlayer K2.6 30880
Others: too many others to list
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
30/30/30 is the biggest bullshit I have ever read since I started developing 5 years ago. I have not seen a single device including my older K26 units, that would do what you expect it to do:-)
LMAO, like sheep to the slaughter...
I guess i'll just flash a new build, do nvram erase, then reboot.