Does anyone know if a new FW supporting SMB V2 is available? I have two Buffalo NAS and one has FW 1.7 and the other is 1.8 but neither support SMB V2. I would like to be able to disable SMB V1 in my Windows OS but not until the NAS supports SMB V2.
Any suggestion is much appreciated.
Thanks,
Jav
Model?
LS421DE
LSWVL - forgot exactly but its the ProDou
The LS421 has it anyways, log onto the web interface as admin > Advanced settings > File sharing > SMB > edit > enable SMB2 protocol > OK.
I don't think its an option on the LS-WVL.
I have web access but only see the shared folders so I will verify that when I get home. If I see that on my LS421, I will migrate everything off my LS-WVL, disable SMB1, and use LSWVL as backup. Thank you much!
Quote from: javelin on May 24, 2017, 11:30:05 AM
I have web access but only see the shared folders so I will verify that when I get home. If I see that on my LS421, I will migrate everything off my LS-WVL, disable SMB1, and use LSWVL as backup. Thank you much!
Thank you. It is there. In fact, I saw this last night and it says it was "Disabled", I didn't do the edit.
Thanks for checking, I appreciate it!
SMB v1 has been permanently disabled on my laptop because of the "wannacry" ransom ware.
It was a done as part of the win 10 security updates.
Now I cannot access either of my two Buffalo NAS units.
Does this mean I should just throw them out? What a fricking waste.
I have an LS-WVL/E and an LS-X2.0TL . Both were working fine and then in the matter of one day I have been limited to FTP Access Only.
Are they seriously not going to support SMB v2 on these devices?
Buffalo like most companies these days provides absolutely no way to contact them to ask so I am hoping someone on this forum is in the know.
Quote from: garneke on June 05, 2017, 02:16:17 PM
SMB v1 has been permanently disabled on my laptop because of the "wannacry" ransom ware.
It was a done as part of the win 10 security updates.
Now I cannot access either of my two Buffalo NAS units.
Does this mean I should just throw them out? What a fricking waste.
I have an LS-WVL/E and an LS-X2.0TL . Both were working fine and then in the matter of one day I have been limited to FTP Access Only.
Are they seriously not going to support SMB v2 on these devices?
Buffalo like most companies these days provides absolutely no way to contact them to ask so I am hoping someone on this forum is in the know.
I am interested in this as well. I also have two LinkStation Pro Duo LS-WVL/E.
Quote from: garneke on June 05, 2017, 02:16:17 PM
SMB v1 has been permanently disabled on my laptop because of the "wannacry" ransom ware.
It was a done as part of the win 10 security updates.
Now I cannot access either of my two Buffalo NAS units.
Does this mean I should just throw them out? What a fricking waste.
I have an LS-WVL/E and an LS-X2.0TL . Both were working fine and then in the matter of one day I have been limited to FTP Access Only.
Are they seriously not going to support SMB v2 on these devices?
Buffalo like most companies these days provides absolutely no way to contact them to ask so I am hoping someone on this forum is in the know.
...this is a "me to" request for smb2.
I know my boxes are old - 2 x TS-QVH8.0TL/R6 with the last available firmware being v1.24... right now these 2 are shutdown and a 'FreeNAS Mini' is on-the-way (future proof). I take this as a lesson learned.
It's been awhile since we've sold those, I wouldn't expect a firmware update.
https://www.howtogeek.com/250228/what-windows-10s-optional-features-do-and-how-to-turn-them-on-or-off/
If you want to turn it back on for legacy support.
Update available for the LS-X series is available on the EU website. Will also work on the LS-WXL, LS-WVL, LS-QVL, LS-XL and LS-CHL v2.
[Note]
Version 1.73 [2017.7.5]
Bug Fixes
[SMB]
- Modified to deal with a Samba programming vulnerability (CVE-2017-7494).
http://www.buffalo-technology.com/Download_t3f.php?elif=%2Fuserfiles%2Ffile%2Fdownloads%2FLS-series-fw173_fwwin.zip
Quote from: davo on July 10, 2017, 11:08:53 AM
Update available for the LS-X series is available on the EU website. Will also work on the LS-WXL, LS-WVL, LS-QVL, LS-XL and LS-CHL v2.
[Note]
Version 1.73 [2017.7.5]
Bug Fixes
[SMB]
- Modified to deal with a Samba programming vulnerability (CVE-2017-7494).
http://www.buffalo-technology.com/Download_t3f.php?elif=%2Fuserfiles%2Ffile%2Fdownloads%2FLS-series-fw173_fwwin.zip
I installed this update to the firmware but I don't see how it allows it to work with SMBv1 disabled.
Is there a new setting?
It fixes the vulnerabilityin SMB1 so technically would allow you to use the protocol.
Quote from: davo on July 11, 2017, 03:21:17 AM
It fixes the vulnerabilityin SMB1 so technically would allow you to use the protocol.
Doesn't help if windows updates disable SMB1 for security reasons. No since is wasting time with this update. Anyone want a couple of paper weights?
read : http://forums.buffalotech.com/index.php?topic=24628.msg88050#msg88050
and : http://forums.buffalotech.com/index.php?topic=24630.msg88052#msg88052
best regards
I recently upgraded to Windows 10 Pro. ( I was previously using Windows 10 Home). I have a Linkstation 200 Series LS220DE. I discovered that Windows 10 Pro uses SMB 2 and I cannot connect to the NAS without reconfiguring "Programs and Features - Features" and checking the SMB1 selection. For this feature to change, a reboot is required. In the Firmware update "ls200-v170", will the SMB 1 be updated add the SMB2 feature? (is it included in the ls200-v170 update? Thank you
The LS220 already supports SMBv2. In the advanced settings go to the SMB settings and enable SMBv2.
Browser ID: smf
(is_webkit)
Templates: 1:
Printpage (default).
Sub templates: 4:
init,
print_above,
main,
print_below.
Language files: 1:
index+Modifications.english (default).
Style sheets: 0:
.
Hooks called: 129 (
showintegrate_autoload, integrate_pre_load, integrate_load_session, integrate_verify_user, integrate_pre_load_theme, integrate_user_info, integrate_load_board, integrate_board_info, integrate_allowed_to_general, integrate_allowed_to_general, integrate_boards_allowed_to, integrate_mod_cache, integrate_pre_load_theme, integrate_allowed_to_general, integrate_simple_actions, integrate_allowed_to_general, integrate_load_theme, integrate_pre_log_stats, integrate_actions, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_codes, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_menu_buttons, integrate_current_action, integrate_theme_context, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general)
Files included: 27 - 1055KB. (
show./index.php, ./Settings.php, (Cache)/db_last_error.php, (Sources)/QueryString.php, (Sources)/Subs.php, (Sources)/Subs-Auth.php, (Sources)/Errors.php, (Sources)/Load.php, (Sources)/Security.php, (Sources)/Subs-Compat.php, (Sources)/Subs-Db-mysql.php, (Sources)/Cache/CacheApi.php, (Sources)/Cache/CacheApiInterface.php, (Sources)/StopForumSpam.php, (Sources)/Subs-Charset.php, (Sources)/Unicode/Metadata.php, (Sources)/Unicode/QuickCheck.php, (Sources)/Session.php, (Sources)/Logging.php, (Sources)/Class-BrowserDetect.php, (Sources)/Unicode/RegularExpressions.php, (Sources)/Unicode/CaseUpper.php, (Sources)/Unicode/CaseTitle.php, (Current Theme)/languages/index.english.php, (Current Theme)/languages/Modifications.english.php, (Sources)/Printpage.php, (Current Theme)/Printpage.template.php)
Memory used: 767KB.
Tokens:
post-login.
Queries used: 14.
[Show Queries]