NAS server install won’t work
December 27, 2022, 20:31
it just gave me back a another line
pi@raspberrypi:~ $ sudo systemctl restart smbd.service
pi@raspberrypi:~ $
try browsing your network from your other computer now
nothing shows up
See
<@175426704297295873>
Your ability to provide a photographic representation of a non-error message is...incredible.
oh lol
that illuminating evidence aside...
sorry if i am doing dumb things
If the samba service is running, but you can't see anything on the network from your other computer...the next thing I'd look at is whether or not there is a network socket listening on the Pi
what is network socket?
a network socket is something that is more specific than just an IP address for locating a service/resource on a network. It's generally, a port+protocol.
In this case...Samba is the protocol that normally listens/uses ports 139 & 445
ok
so is port 139/TCP or 445/TCP listening on your Pi right now? ((will probably expect to be 445 - https://www.varonis.com/blog/smb-port))
wait how do i determine that
i am a little lost
sudo netstat -tulpn | grep LISTENper https ://www.cyberciti.biz/faq/unix-linux-check-if-port-is-in-use-command/
Read these links I'm sending you.
yup doing that right now
ok my pi for samba is listening to port 139
at what address?
ok
so samba is listening on every address on your pi
next question - what is the IP address of your Pi?
192.162.254.56
What is the IP address of the other computer on your network trying to access the Pi?
192.162.254.50
That's the computer you're SSHing into the Pi from?
yes
Well, when everything appears to be good on the Pi's end re: Samba listening and properly configured AND you know you can talk on the network between the 2, the only other things to check are going to be on the client-side, which would be Explorer not being configured correctly or something in Windows prohibiting discovery of file shares on that network (due to Windows thinking it's a public network, ergo not allowing for promiscuous network discovery)
i have it looking for public network?
ok let me read this
<@175426704297295873>
got progress
but nothing still
dont know what to do now
the fact that it's showing up as 'other device' and not as the name of your Pi under the 'Computer' section tells me that your computer is unable to understand the name of the Pi on your network.
oh
so i tried connecting to it on my phone
and i am able to acces
why does it not show up on my pc
Your phone is smarter than Windows...no surprise there. ;p
lol
got it
probably related to netbios naming
oh
so what am i supposed to do now
what is the hostname of your Pi, on your network, and how does Windows know that?
you should also be able to access it directly via //192.162.254.56
raspberrypi
or pi
from a command prompt on Windows
ping raspberrypi
oh
typing that by itself does nothing
Oh
you really should read up on some basics of computering
or get some sleep
understand the difference between a command and a switch/option/value
and the proper shell/context which will understand them
Oh lots to learn
Some I know most I dont
So what am I supposed to do right now
You know samba is running correctly on your Pi, because you can access it on your phone
so figure out why you can't access it via Windows
Yea but even on my phone I can only acces threw guest
When I go threw guest it works
I am going to take a break when I am back I will ping you
Thanks for the help so far
How to make it that I can put files into it
You've exceeded the scope of Raspberry Pi file sharing related questions
and I'm very sensitive to scope creep
Samba is running on your pi - now you need to figure out how to properly access a samba file share on your network from the client of your choice
If I had to guess...the issue now is related to the config of the samba server and file/folder permissions
I don't recommend this long-term, but you can create a tempFolder in ~/Share/Server (assuming that's where you specified in your smb.conf) and then
$ sudo chown -R nobody:nogroup tempFolderand then you should be able to read/write to that over the network via Samba, anonymously
the big thing is making sure that the files/folders you create in linux for the file share match the permissions allowed to read/write to it when connecting to the file share over the network (eg. if you're connecting with the 'pi' account, then the folders shared by samba need to be owned/writeable by the 'pi' account)