I have no idea why there is a Windows Network profile appearing as it is on my network but when I trying to open it. It doesn’t exist. By using Fedora system which I recently used to do a hardware reset on my router and modem. There should be no connections to any Windows machines. I do have a lap top with windows installed but it is not turned on and not on the network. As I right click with the mouse on the Windows Network icon. I have no options to delete or enter it.
Thank you very much for teaching me new levels of entering Samba by CLI .
I do not understand if I shall create a new user sudo smbpasswd -a Jonas as a guest of the allready existing user [TemplePusher@jonas-bloch-riisgaard ~]
[TemplePusher@jonas-bloch-riisgaard ~]$ sudo firewall-cmd --reload
success
[TemplePusher@jonas-bloch-riisgaard ~]$ sudo smbpasswd -a Jonas
New SMB password:
Retype new SMB password:
Failed to add entry for user Jonas.
[TemplePusher@jonas-bloch-riisgaard ~]$ sudo smbpasswd -a Jonas
[sudo] password for TemplePusher:
Sorry, try again.
[sudo] password for TemplePusher:
New SMB password:
Retype new SMB password:
Failed to add entry for user Jonas.
As I follow the example I do fail because of lack of understanding. As I understand the Quick docs - How to create a Samba share. I will create a guest user and NOT a new user with the sudo rights ?
This is always difficult, but maybe i can explain in short terms:
Samba/smb is a protocol/software who acts as an interface between Linux & Windows (and others i guess).
It has a own User-Database! that’s why you have to create a separate user and password.
That you can configure Samba you need sudo or root rights. Setting a password is a configuration.
In your example, your are crating a SAMBA-user named Jonas who will be used with your Linux-account TemplePusher who apparently is a sudo user.
When you connect from windows, you will use the user/pw from Jonas to connect to the share.
If you want to see your share from Network: “Browse Network” in Linux you will need also to use the user/pw from Jonas.
And yes as @jpbn mentioned, writing down a password would be a good idea in this case ;-).
To simplify the whole thing, using the username/pw from Windows to create a samba-user, helps to remember better that you are communicating between windows and linux over samba.
Thank you very much. Here you really explains me how the Transport layer actually functioning by a part of OSI to differ from the GUI where my basic knowledge reach. I will study more and see if I can do further modification.
Just one question @jpbnwriting down a password would be a good idea in this case ;-).
Is it enough security using a PW saver like a cloudbased as Lock wise Browser Password manager ( Mozilla ) or an Fedora software install as KeepPassXCPassword manager for Fedora 34. All this writing down and finding passwords can be a lot of keeping track on when there is more than 20 different account to logins. I thought about getting a Physical password manager. Typically, these gadgets are advertised as an alternative to writing passwords on paper or in digital documents on the computer for easy access.Physical passwordmanager Perhaps getting a Smartcard Smartcard or similiar.
As far as I know I didn’t set up any Windows server and definitely no printers as I haven’t any (I know a printer can print PDF ). Hmm, kind of strange. Wonder what I did this time
Samba/SMB is a “Windows server”. My mistake, looks like this is a default location for printer drivers. Anyway, you can check your /etc/samba/smb.conf. You’ll probably see a section like this below. You can comment out that share name if you don’t want/need it.
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
Now I get it. SAMBA is for the routers software configuration which is made for windows users. What doew it means that it is a Windows server ? What is there for Fedora Linux as an alternative if there is any ?
It’s a way to allow Linux to present itself as a “native” server for Windows - i.e.; it will make your Linux server look like a Windows server to other Windows machines/clients.
It’s perfectly fine to use Samba if that’s what you need - Windows and macOS machines can easily access Samba network shares.
If you’re looking for a “Linux native” file sharing protocol though, you might want to check out NFS.
Personally, I’ve always just used Samba because of its cross-platform compatibility.
Oh! Now I understand why this Windows icon appear on my machine. Thank you very much for explaining me. I was a litle confused because I thought I had an Windows machine connected through my router to this machine.
Oh! Now I understand why this Windows icon appear on my machine. Thank you very much for explaining me. I was a little confused because I thought I had an Windows machine connected through my router to this machine.