After a Windows update, Samba on your DM920 with SatLodge 3.2 likely stopped working because it uses an old Samba version (SMB1), which Windows now blocks. Newer images like OpenViX 6.7 use SMB2/3, which work fine. You can try editing /etc/samba/smb.conf and add:
server min protocol = SMB2
client min protocol = SMB2
server max protocol = SMB3
Then restart Samba. If it still doesn’t work, your image is too old — try a newer SatLodge (OE2.0) or OpenViX. They're stable and will fix the problem.
Recent Windows updates have disabled SMB1 (Server Message Block v1) for security reasons. Many older Linux-based systems (like your DM920 with Satlodge 3.2) still use SMB1 for sharing files. When SMB1 gets disabled, your Dreambox disappears from the Windows network browser.
Re-enable SMB1 on Windows
Note: SMB1 is outdated and insecure. Use only if necessary and ideally only on a trusted LAN.
How to re-enable SMB1:
On your Windows PC:
Press Win + R, type optionalfeatures, press Enter.
Scroll down and check:
"SMB 1.0/CIFS Client"
"SMB 1.0/CIFS Server" (if you want to share back)
Click OK, reboot your PC.
After reboot, check if the DM920 shows up again under "Network" in File Explorer.
Amazing work...
