![]() Samba contains the SMB protocol, support for the Windows naming service (WINS), and support for joining Windows workgroups. Samba-common-bin contains a tool that you'll need to register users with Samba. Sudo apt-get install samba samba-common-bin To write files to the server, use any modern client, such as a Mac with MacOS 12, or a PC with Windows 10/11.The following instructions will set your RPi to share its files on your local network and be accessible by Windows. Windows 98 did not want to launch executables directly from the server, and I had to copy the files to the local disk first. I could successfully connect anything I tried: OS/2 Warp 4.52, Windows NT 4.0, Windows 2000, Windows XP, and Windows 98. So: If in doubt, do a reboot after the installation. With the Raspberry Pi OS of October 30, 2021, this no longer happened. After a reboot, the correct name was used. This is wrong! It should have used the name from smb.conf ("retro"). Note: When I first wrote this guide, after the above steps, the Raspberry Pi created a server with its hostname as the SMB name.Check if it is running: sudo systemctl status nmbd.# Allow guest access, and non-authenticated access # New directories are read/write and browsable for pi, and read/browsable for others # New files are read/write for the owner (pi), and read for the rest # Regardless of the user that actually connects, always use "pi" when accessing files on the share. # Unknown ("bad") users are mapped to "nobody" # Also allow the authentication protocols used by LANMAN1. # Allow the very old LANMAN1 protocol, used e.g. # This is the default, it means that the Raspberry Pi handles security on its own. Server string = File server for retro clients This seems to work better for OS/2 clients. # Set the netbios name to "retro" regardless of the server's name. Install Samba: sudo apt -y install samba samba-common-bin.Create the shared data directory and allow unrestricted access to it: sudo mkdir /media/retro & sudo chmod 777 /media/retro. ![]() Perform the usual initial setup (apt update/upgrade, set host name, set timezone etc.). Start with a fresh image of Raspberry Pi OS Lite. ![]() Because such a server is insecure anyway, allow access without authentication for any Goal: Setup a Raspberry Pi with Samba, configured such that very old clients (such as OS/2 Warp, DOS or Windows 95)Ĭan access the shares. Use the Pi only in your intranet, without any port forwarding, and only to perform the dedicated task of a retro file server. Likely immediately catch a trojan, and your Pi will be used to spam out mail or become part of a botnet for denial of service attacks. Instead, this Gist shows how a dedicated Raspberry Pi can be used to make a file server that supports all of these oldĪ word of caution: Because these protocols are dangerous, never expose the Raspberry Pi to the internet! You will most Usually, these protocols can be re-enabled on a NAS, but I would advise against doing this. Unfortunately, these old systems use protocols that are dangerous and thus disabled on any modern file server, suchĪs a NAS. That can be enabled, then sharing data via a file server is a good solution for this challenge. If the retro machine has an Ethernet adapter A common challenge with retro machines is transferring data from and to it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |