I doubt it's a networking problem.
But you've not provided enough information for anyone to do more than guess.
Start by providing the following (in no particular order):
But you've not provided enough information for anyone to do more than guess.
Start by providing the following (in no particular order):
- Pi model
- OS name and major release running on the Pi. By release name not any of the myriad version numbers that might be delayed.
- How you're mounting the partition on the Pi. Include you fstab entry, mount command, or systemd mount unit if applicable.
- The output from
Code:
testparm -s
- What filesystem you have formatted the partition with.
- Exactly what you are doing on the clients
- Exactly what error messages you are seeing (no "can't access, can't access, can't access" is not useful. Nor is it an expected error message from Windows)
- What version and "level" of windows are the clients running?
- Whether there are any relevant error messages in the output from the following commands on the Pi:
Code:
dmesgjournalctl
- The output on the Pi of
Code:
mountpoint \mnt\usb1\
- The output on the Pi of
Code:
ls -ld \mnt\usb1\
- What changed on the Pi between it working and not
- What changed on the clients between it working or not?
Statistics: Posted by thagrol — Sun Apr 21, 2024 8:53 pm