I am posting about the odd network behavior my GL.iNet GL-MT6000 has been exhibiting specifically around the Network Storage Option.
Up until yesterday I was able to mount my 500TB on my Mac OS machines that is plugged into my router, now when I attempt to connect to the drive (smb://10.0.0.1/5tb) from my laptop and Mac Mini the Finder throws an error “There was a problem connecting to the server “10.0.0.1”or just flat out disappears with no error given.
Network Drive - Hard drive
Western Digital Red Drive 500TB - EXT4 formatted mounted in an external case
Shared VIA Samba from the GL-MT6000 router
Laptop - Mac OS Monterrey - 12.5.1
Mac Mini - Mac OS Tahoe - 26.1
Troubleshooting Steps:
Unmount / Remount attempts
SSH’d to the router and restarted the SAMBA4 service (/etc/init.d/samba4)
Attempted to mount the drive from Debian OS
I can see that the files are still on the drive when I ssh to the router at /tmp/mountd/disk1_part1/
Has anyone else experienced this? I really hope there is a solution for this because it was rad having all my files available on the network from a central location
Could you please help confirm the following details:
What firmware version is currently installed on the MT6000?
Has the Debian OS mounted successfully? If not, please let us know the exact error message.
If the Debian OS is mounted successfully, please ensure the macOS device is connected to the home network and check its firewall settings to confirm that no required traffic is being blocked.
Here is the funny thing, everything is working and back to normal, this is till concerning because I haven’t done anything outside of what I originally posted. I’m inclined to update to the latest firmware but I’m also concerned it won’t stabilize the experience I’ve been having. Thank you for your attention to this.
It’s possible that a small detail was overlooked—for example, the device may not be connected to your home network.
If you plan to upgrade to the latest firmware, please note that SMB1 / NTLMv1 is disabled by default in version 4.8.x for security reasons. If you still have devices that rely on SMB1 or NTLMv1, you can manually adjust the configuration using the command below.
sed -i 's/SMB2/NT1/g' /etc/samba/smb.conf.template4
reboot