![]() name resolve order, host name length restrictions, etc. If you have to turn the clock back to SMB1 days you need to follow the rules set at that era. Whether you can "discover" all the workgroups and hosts in Nautilus is another matter. That will probably eliminate the SMB1 error message. If you don't do that on the server you will likely get a protocol negotiation failed: error. Then restart samba: sudo service smbd restart If the server is running Ubuntu 20 or anything with the same version of samba you would have to edit smb.conf on that machine and add: server min protocol = NT1 If you kept your Win10 machine up to date it is disabled so you will have to enable it there. Of course the server you are trying to connect to must have SMB1 enabled on its side. Create new configuration file /etc/xinetd. Enable service SWAT in /etc/nf and restart with the new configuration by the following: sudo update-inetd -enable swat sudo dpkg-reconfigure xinetd. ![]() ![]() Right under the workgroup = WORKGROUP line add this one: client min protocol = NT1 In a terminal write: sudo apt-get install samba smbfs samba-doc swat xinetd. Use 3rd-party packages with AD support from a trusted source. For details, see Build Samba from Source. Second, if you are talking about that specific error when running smbclient you would need to enable SMB1 ( Samba calls it NT1 ) on the client side in /etc/samba/smb.conf. Red Hat does not provide packages for running Samba as an AD DC. First, there is no such thing as a HomeGroup in Linux, MacOS, or Windows starting with Win10. Install Samba Server on Ubuntu 7.10 (Gutsy Gibbon) If you want to share files between your Ubuntu and Windows computers, Weve got samba installed, but now we. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |