• Welcome to Photrio!
    Registration is fast and free. Join today to unlock search, see fewer ads, and access all forum features.
    Click here to sign up

Windows 10 support is over. Likely switching to a version of Linux

Recent Classifieds

Forum statistics

Threads
202,279
Messages
2,837,566
Members
101,188
Latest member
HeyItsMeDusty
Recent bookmarks
0

Sharktooth

Member
Joined
Apr 4, 2022
Messages
441
Location
Canada
Format
Medium Format
I've gone through an absolute nightmare over the last 3 days, trying to get my Linux Mint box to share files with Macs and Windows 10/11 computers on my home network.

I used to have an Apple Time Capsule router with a built in hard drive, but they're no longer supported, and use outdated SMB1. I switched to a different router, and was intending to use a usb drive connected to it, but found out that was only possible with SMB1 as well.

I then thought it would be easy to set up my 2006 Mac Pro to act as a file server, since I had it running well with Mint. This turned out to be much, much, much, much harder than I originally anticipated.

First off, Mint doesn't share files easily with Windows. You need to install SAMBA, which is a communication protocol that can talk to Windows computers. The installation is easy, but after that, it needs to be configured. That's where the nightmares start. Every drive, folder, and file has permissions associated to it, and those have to be adjusted to allow specific users to have access to them. It all has to be done via a terminal, and modifying a special file, like a Windows registry file. There's no simple GUI that I could find that would make this easy. You really have to know a lot more "tech" stuff to get this working. Most of the time was spent googling all kinds of forums on linux. To make things even worse, every drive has a mount point, and that mount point has to have the right permissions settings too.

Three days later, and with significant loss of hair, I am now able to log into the Mint box through my home network. With Macs, I have to use the "Go" menu, and "Connect to Server". I can see the Mint box with the file shares. When I try to see the Mint box from Windows, nothing shows up in the Network. I have to manually type in the IP address for the Mint box ( with the \\ symbols in front). Then the Mint box shows up.

I've only been able to get it to work by using the user name and password for the administrator of the Mint box. I should be able to add other users and passwords, but nothing I've done so far has allowed this to work. I can usually see the shares in the network, but I can't even open them. Since I'm the only user in my home network, this is O.K., but If I wanted to control access for multiple users, I'd be stumped.

There are some other interesting things I've learned through this process. You have to think hard about how you want to format your drives for file sharing. Linux gives you many different formatting options, such as ext4 (native Linux), NTFS (Windows), HFS+ (older macs), FAT32 (older PCs), and many others. I'm using the drives to backup files, so you need to consider what type of files are going to be backed up. FAT32 can usually be read and written to by any Linux, Windows, or Mac computer, so if your Linux box dies, you can remove the drive and connect it into another computer to read the files. If you formatted the drive to ext4, then it won't be readable when connected directly in a Windows or Mac computer. A Windows computer won't read an HFS+ formatted drive either. The first thought would be to format the shared drive as FAT32, since most computers would be able to read it, but FAT32 has some limitations in file size, and may not work with huge files, such a operating system installer dmg files.

I'm now thinking I would have been better off creating a FAT32 formatted drive to share most "general" files, but then also create a NTFS drive to backup system related stuff for Windows, and an HFS+ or APFS drive for Mac system files.
 

koraks

Moderator
Moderator
Joined
Nov 29, 2018
Messages
27,585
Location
Europe
Format
Multi Format
Yep - it is a combination of my slightly stubborn nature and my need to minimize computer equipment and software expenditures that motivates the struggle

Yeah, I can relate! Understandable. Requirements always involve some sort of compromise and the optimum is highly personal, I understand and I also understand how you might get stuck with a 'solution' that seems unlikely for an outsider, but makes good sense to you. I understand how the Seagate combines a couple of attractive attributes. I'd try to get the SMB1 working on Win11 first and if that fails, just fall back to an FTP solution. I imagine either should work one way or another.

@Sharktooth recognizable situation; I'm wondering whether you're using AI (Copilot, Gemini, Chatgpt) to help you navigate through this? It can really speed things up with tailor-made advice for your specific situation.
 

MattKing

Moderator
Moderator
Joined
Apr 24, 2005
Messages
55,487
Location
Delta, BC Canada
Format
Medium Format
@Sharktooth ,
Thanks for sharing your pain :smile:.
A long time ago, in an alternate computer universe, I dabbled a bit with setting up my own Linux server, using an old, IIRC, Windows XP computer converted to one of the Debian flavours of Linux.
At the time, I was also working as a drafted in place, untrained administrator for my office's Windows Network with a legacy Unix based server.
So I had at least mused about converting an old Windows machine I have at hand to serve as a replacement for the backup option I have and like.
But your travails reinforce my concerns about doing so - that and the higher energy use and space demands.
I'd try to get the SMB1 working on Win11 first and if that fails, just fall back to an FTP solution.

So far, the custom Seagate interface is getting in the way of an FTP solution. It diverts you to a disk management solution that is ineffective, because that in turn relies on old, incompatible with modern Windows solutions. I'll continue to explore.
 

koraks

Moderator
Moderator
Joined
Nov 29, 2018
Messages
27,585
Location
Europe
Format
Multi Format
Well, taking @xkaes' suggestion of a VPN, how about installing (at least temporarily) a VPN with WinXP on one of your more modern machines? Then use that to regain access to the Seagate and configure it for FTP access. Once that's done, you should be able to access at least the files (although not the management console) with your regular Win10/11.
 

xkaes

Subscriber
Allowing Ads
Joined
Mar 25, 2006
Messages
5,197
Location
Colorado
Format
Multi Format
My suggestion was for a VB (Virtual Box) not a VPN (Virtual Private Network). Too many abbreviations, if you ask me.
 

Sharktooth

Member
Joined
Apr 4, 2022
Messages
441
Location
Canada
Format
Medium Format
@Sharktooth recognizable situation; I'm wondering whether you're using AI (Copilot, Gemini, Chatgpt) to help you navigate through this? It can really speed things up with tailor-made advice for your specific situation.

I just now tried Perplexity to get an AI answer. It worked pretty well, but much of it only makes sense now after doing a lot of reading over the last few days. It still comes up well short of a clear solution, but it definitely does provide some useful things to try. If I'd started with this 3 days ago, the answer would have been completely useless, since I'd have no idea what the answer meant.

Maybe it would have been been better to ask for a tutorial about permissions on linux first. Maybe I'll try that now.
 
Photrio.com contains affiliate links to products. We may receive a commission for purchases made through these links.
To read our full affiliate disclosure statement please click Here.

PHOTRIO PARTNERS EQUALLY FUNDING OUR COMMUNITY:



Ilford ADOX Freestyle Photographic Stearman Press Weldon Color Lab Blue Moon Camera & Machine
Top Bottom