Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am replacing an old Fedora 18 drive because it is failing with a new Fedora 33. I have copied the configurations from the old. I can ping the Fedora 33 file server from Windows but cannot reach it otherwise. Samba is installed and smb.conf file is verified as the same.
From the Fedora drive I can browse the internet and ping the Windows PC so I know the network is working. The only thing missing is the Samba shares. It has been 6 years since I worked with Linux so suspect I have forgotten something basic but can't get a toe hold. Can anyone point me to what I might check ?
samba and Windows has changed a bit between versions 18 to 33. It's not that 33 is not sharing it is because the network feature in the file browser to find shares uses SMB/CIFS version 1 which has been depreciated and turned off and/or removed. Windows 10 now uses WS-discovery. linux has a WS-Discovery implementation service (wsdd) which is similar to WS-Discovery and lets Windows find linux servers.
Without smb version 1 or wsdd you can connect directly to a linux share from windows by directly entering the server in the URL text box \\samba_server_address\share. Windows will prompt you for a username and password. The same is true for Fedora, in the file browser select other location and enter smb://Windows_computer_address/share.
Don't forget to test your installation with smbclient. I would run it on the Fedora server itself (smbclient -L //servername to list all shares) and from a remote Linux system.
If you don't have a remote system, set one up in a VM on Fedora or Windows, or use WSL on Windows.
After listing the shares, try to connect to one. Then mount it:
Code:
smbclient -U USERNAME //servername/sharename
mount -f cifs -o <some option to set username> //servername/sharename /mnt/blabla
Last edited by berndbausch; 12-01-2020 at 02:20 AM.
The first thing that occurs to me is this: Did you configure the smbpasswd file? See man smbpasswd for more,
No I didn't. Thank you very much! I now do recall having to create SMB users in addition to users. I have now done that, along with the SMBPASSWD. I am still unable to reach the Fedora PC with a file browser but the SMB user and password were needed. Thank you. I am also unable to browse to the Windows PC from Fedora, even though I have a share for Everyone. That means there is something else going on. I can ping each from the other but that is all. I will let you know what I find.
samba and Windows has changed a bit between versions 18 to 33. It's not that 33 is not sharing it is because the network feature in the file browser to find shares uses SMB/CIFS version 1 which has been depreciated and turned off and/or removed. Windows 10 now uses WS-discovery. linux has a WS-Discovery implementation service (wsdd) which is similar to WS-Discovery and lets Windows find linux servers.
Without smb version 1 or wsdd you can connect directly to a linux share from windows by directly entering the server in the URL text box \\samba_server_address\share. Windows will prompt you for a username and password. The same is true for Fedora, in the file browser select other location and enter smb://Windows_computer_address/share.
From Windows 10, with a user the same as one defined in Fedora and with an SMBUSER, I attempt to browse to \\192.168.1.71. The Windows 10 is 192.168.1.2, the same subnet, going throug a CAT6, not wireless. Both are plugged into the same Netgear router as the only things plugged into it.
[QUOTE=berndbausch;6190519]Don't forget to test your installation with smbclient. I would run it on the Fedora server itself (smbclient -L //servername to list all shares) and from a remote Linux system.
On the Fedora PC I opened console with su - and entered: smbclient -L //192.168.1.71 and got
[root@localhost ~]# smbclient -L //192.168.1.71
do_connect: Connection to 192.168.1.71 failed (Error NT_STATUS_CONNECTION_REFUSED)
[root@localhost ~]#
Samba is installed, smb users created with passwd and shares defined in a smb.conf file copied from the working Fedora 18. I really didn't expect this failure. I'll double check everything.
From Windows 10, with a user the same as one defined in Fedora and with an SMBUSER, I attempt to browse to \\192.168.1.71. The Windows 10 is 192.168.1.2, the same subnet, going throug a CAT6, not wireless. Both are plugged into the same Netgear router as the only things plugged into it.
This should work regardless of wsdd. Can you successfully connect to the Fedora computer?
You do not have to be root. From the same computer
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Samba not sharing
