Here's what I got: Anonymous login successful ??? Sharename?????? Type????? Comment ??? ---------?????? ----????? ------- ??? data_server???? Disk ??? IPC$??????????? IPC?????? IPC Service (Samba 4.7.6-Ubuntu) Reconnecting with SMB1 for workgroup listing. Anonymous login successful ??? Server?????????????? Comment ??? ---------??????????? ------- ??? Workgroup??????????? Master ??? ---------??????????? ------- ??? WORKGROUP??????????? HOMENETWORK It looks pretty similar to yours in form. Bill Lugg On 11/16/19 11:55 AM, Rowland penny via samba wrote:> So, what does 'smbclient -L localhost -N' return ? > > I get: > > Anonymous login successful > > ??? Sharename?????? Type????? Comment > ??? ---------?????? ----????? ------- > ??? Demo??????????? Disk > ??? tmpguest??????? Disk > ??? berryboot?????? Disk > ??? linprofiles???? Disk > ??? services??????? Disk????? services > ??? test??????????? Disk > ??? IPC$??????????? IPC?????? IPC Service (Samba 4 Client devstation) > Reconnecting with SMB1 for workgroup listing. > Anonymous login successful > > ??? Server?????????????? Comment > ??? ---------??????????? ------- > ??? DEVSTATION?????????? Samba 4 Client devstation > > ??? Workgroup??????????? Master > ??? ---------??????????? ------- > ??? SAMDOM > > Yours will be different. > > Rowland > > >
On 16/11/2019 20:22, William Lugg via samba wrote:> Here's what I got: > > Anonymous login successful > > ??? Sharename?????? Type????? Comment > ??? ---------?????? ----????? ------- > ??? data_server???? Disk > ??? IPC$??????????? IPC?????? IPC Service (Samba 4.7.6-Ubuntu) > Reconnecting with SMB1 for workgroup listing. > Anonymous login successful > > ??? Server?????????????? Comment > ??? ---------??????????? ------- > > ??? Workgroup??????????? Master > ??? ---------??????????? ------- > ??? WORKGROUP??????????? HOMENETWORK > It looks pretty similar to yours in form. > > Bill Lugg >OK, we now know that Samba is running and that you have a share. go to another Linux machine, open a terminal and type this: smbclient //shorthostname/data_server -U username Replace 'shorthostname' with the Samba servers short hostname and 'username' with the Samba user you created. You should get prompted for the users password, after entering the password, you should get this: Try "help" to get a list of possible commands. smb: \> If it doesn't work, try with the Samba servers ipaddress instead of the hostname. Type 'q' to exit If this works, then try again from Windows. If it doesn't, check that the share directory exists and that your user has permission to enter and write to it. Rowland
I did as instructed and it works.? After I sent the last email, I pulled up the Thunar file manager on the client machine, browsed the network and to my surprise the host machine appeared in the list.? I opened it and data_server was there waiting for me. So I logged in and was able to read and write files successfully. If I look at file properties for files placed in the share from the client side, I note that the user and group in the shared folder is root (root) on both the client and host.? However, I can open and edit them as a regular user, which makes sense as user, group and others all have rw access.? Is this as it should be? Win10 was also successful once I figured out not to include the shared folder name in the path. Thanks so much for your help.? Like I said at the outset, I know enough about these things to get myself into trouble.? :o) Bill Lugg On 11/16/19 1:43 PM, Rowland penny via samba wrote:> OK, we now know that Samba is running and that you have a share. > > go to another Linux machine, open a terminal and type this: > > smbclient //shorthostname/data_server -U username > > Replace 'shorthostname' with the Samba servers short hostname and > 'username' with the Samba user you created. > > You should get prompted for the users password, after entering the > password, you should get this: > > Try "help" to get a list of possible commands. > smb: \> > > If it doesn't work, try with the Samba servers ipaddress instead of > the hostname. > > Type 'q' to exit > > If this works, then try again from Windows. > > If it doesn't, check that the share directory exists and that your > user has permission to enter and write to it.