Win 11 and SMB2 for NSA325v2 - Firmware NSA325_4.81(AAAJ.1)
All Replies
-
Ah that's ist! I found it in /opt/sbin
Thank you for clarification! ;-)
0 -
Many thanks for the links and the instructions. Unfortunately, there is no package "zyxel-samba-replacement" inside Entware anymore. I tried samba server but this didn't work (looks like the whole environment for zyxel is missing). Is there any chance to get the zyxel-package?
0 -
Edit: Sorry, duplicate…
0 -
I can see it here:
Check in /opt/etc/opkg if that repo is in the list.
1 -
Perfect, there it is. Small note, https as in the link creates an error due to certificate errors (haven't checked any details), but http works. I also got the symlink error, but it looks like everything works. Many thanks, this has saved my plans for paperless without buying new hardware😀
0 -
Hello again, I did encounter a strange situation. After the installation, I set SMB2 as the target-version ("min protocol = SMB2" inside ZyXELSambaReplacement.conf, later also in /etc/samba/smb.conf for a test). It ran perfectly for a week; I used it for paperless and also could access my shares from iPhone Files-App. All of a sudden, I couldn't access my shares anymore. After few small researches and reboots, I found that the server doesn't propagate version 2 anymore (checked via nmap). Also, my special config was gone. Still, smbstatus -V says it is Version 3.6.25. I haven't found any reason for the missing v2. I can access over v1, but this looks very suspecious to me.
Has anyone ever had this experience or do you guys has any idea what to check?
0 -
later also in /etc/samba/smb.conf for a test
Is you SMB2 setup dependent on a setting in that file? That file is volatile, and generated from scratch by the firmware. At any moment the firmware case decide to generate a fresh file.
Still, smbstatus -V says it is Version 3.6.25
AFAIK smbstatus doesn't actually query the running smb server. It just assumes the running server was in the same package. If you want to know which binary is running, use top to find it's PID, and then execute
cat /proc/<PID>/cmdline | tr '\0' ' '
to read it's commandline.
1 -
Update: After a few restarts, v2 is here. I'm sorry for the inconveniences. Many thanks for your help.
Thanks for your answers. I think I have a better understanding now. Somehow, the old environment was active again. I did some research, found log-files in /usr/local/zy-pkgs/opt/var/log and therefore could get the new environment come up again. I do now have /opt/sbin/smbd running and I tried to set min protocol = SMB2 in ZyXELSambaReplacement.conf, but I get the error "(reply_negprot)
No protocol supported !" So i do have the newer version but still only v1 active. Any idea what could be wrong?0
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 156 Nebula Ideas
- 104 Nebula Status and Incidents
- 5.9K Security
- 314 USG FLEX H Series
- 285 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.6K Consumer Product
- 256 Service & License
- 398 News and Release
- 85 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.7K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 78 Security Highlight