![]() My luck there is something wrong with the Windows environment, which I've seen some subtle hints (from a few months ago) that sharing was having issues.Right click folder, click "Sharing Options"Įnable sharing and allow others to create and delete files, and allow Guest access. Thank you very much for your assistance with this. Lastly, what should be done with the smb.conf file? Should I comment out EVERY line and let the Nautilus config file take care of everything, or should I only comment out the share definitions? I'm assuming you believe it is unnecessary. it was in a sample config file and I included it only to solicit comments on in and whether it is needed. As far as I'm concerned, at this point, while the switches look differently than the manually generated ones in smb.conf, I think I can live with this until I get better at setting things up. When I right click on a folder and create a share and then view my shares with the command from Morbius1 ( net usershare info -long), I see where the /var/lib/samba/usershares folder share files are created. Between you and mastablasta, I've decided to comment out the shares in the smb.conf file and let the system use the Nautilus generated file. I actually have a nickname I appropriately use. Me is the substitute name I used just for this thread. It seems that Windows10 is preventing me from accessing the shared file and I don't understand why. I placed a zero byte file in there as well with no change in outcome. As far as I'm concerned, at this point, while the switches look differently than the manually generated ones in smb.conf, I think I can live with this until I get better at setting things up.Īfter commenting out the share definitions in smb.conf and using Nautilus share config, and sharing the "Public" folder in my home directory, I still get the dreaded "Windows cannot access \\myserver\Public folder. ![]() ![]() Between you and Morbius1, I've decided to comment out the shares in the smb.conf file and let the system use the Nautilus generated file. me is the substitute name I used just for this thread. instead, providing the above listed error. I'm assuming I have all the parameters set right, but for the life of me, I cannot get Windows to recognize the Linux share. ![]() Passwd chat = *Enter\sne\s*\spassword:* %n\n Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*. Panic action = /usr/share/samba/panic-action %d Server string = %h server (Samba, Ubuntu) On my physical Linux machine, Ubuntu Desktop 18.04, I have the following set in the "/etc/hosts file. On my Windows10 PC, I have the workgroup set to WORKGROUP So, my questions are, what am I potentially doing wrong? AND Why didn't the GUI 'share local network' modify the smb.conf file after setting it from the desktop?Īlright, no matter what I do, I continue to get a "Windows cannot access \\192.168.1.100\downloads" error message. However, after adding myself, I still couldn't access the folder share via Windows10. So, I opened it and added the share at the end of the file.Īfter reading a few posts, I discovered that I had forgotten to add myself as a Samba user (thinking this was going to fix me up). After doing this, I went into the smb.conf file to verify that the share was added, and it WAS NOT. I had to install Samba and once that was complete, I was able (from the GUI) to create a local network share. What I'm having difficulty with now is getting Windows 10 to recognize my shares on the Linux box. Quite frankly, I think I like it better than the server version as many of the problems I had before are now less and less. I recently had some problems with my 18.04 (server) instance so I scrapped it and reinstalled the desktop version. I am again in need of help from you subject matter experts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |