Setting Up and Sharing Files on the Network - Not fixed but solved [Solved]

[Falcon]

I replaces the samba configuration file with the one from computer #2. Then I rebooted. Still no log file under samba.

I also ran the dmesg command above but it didn't return anything.

[Falcon]

I need to shut down for now, but I hope that we can pick this up tomorrow.

Thanks for the help thus far.

[Falcon]

Does anyone else have any suggestions on how I might get these sharing mechanisms to work...???

[CharlesV]

One more possible... I JUST had a machine that I could not get shares working on and I found that the Firewall appeared to NOT be disengaging when I turned it off. I went to the home profile and allowed everything and suddenly was able to share through it.

I havent had a chance to get back and see why this was, but even though I was turning off all three profiles.. it was *NOT* turning off!

[Falcon]

Assuming that I understood you correctly, I went into the Firewall configuration and insured that the firewall was turned off for Public and Office. Then I turned it ON for Home and set both Incoming and Outgoing to Allow. Then I tried again but computer #1 still does not show up in the Network lists on computer #2. However, on the Network list on computer #1, computer #2 DOES appear. So computer #1 can detect the presence of computer #2, but computer #2 can't detect the presence of computer #1.

Then, just to be sure, I went back into the firewall configuration and set both Office and Public to ON, and I set both of them to Allow both incoming and outgoing traffic, but still no success.

[adamofbremen]

Hi there

I had no end of trouble trying to work with samba under mx linux. There seems to be some sort of permissions problem. I gave up in the end. I use NFS. It is much simpler.

If you have a decent conky, it will tell you what your ip address is on your wallpaper - that's convenient. That's all you need for NFS.

Then you want NFS server installed and running on the server machine and a very simple /etc/exports file to tell it what to share and how (read only, read/write, etc)

Then on a client you just mount a volume - its a very short command.

That's about it. The network drive appears in your file manager and you go from there.

It's easier to understand and it's real Linux, not some Microsoft rubbish.

All the best
Adam

[Falcon]

Thanks, Adam. I will give this a try a little later and let you know how I made out.

[FullScale4Me]

I'm not following the UFW profile on/off shuffle. An easier and cleaner test is:

Code: Select all

$ sudo ufw status
Status: inactive

I'm going to assume that in the above 'inactive' = all off.

It seems all thru this thread we all have been dancing around the pink elephant in the room. Delete your computer1 user created share(s) in MX Samba config on computer1.

Then on computer2 run: (you may have to install smbclient)

Code: Select all

smbclient -L computer1_IP

which hopefully result in something very similar to

Code: Select all

user@computer2:~
$ smbclient -L computer1_IP
Password for [WORKGROUP\user]:

	Sharename       Type      Comment
	---------       ----      -------
	print$          Disk      Printer Drivers
	IPC$            IPC       IPC Service (Samba 4.17.12-Debian)
	

Those 2 shares above are always present on MX Linux/Debian. 'IPC$' is hard coded in Samba and 'print$' is defined in /etc/samba/smb.conf

If nothing shows up we need to explore what you haven't told us. Seemingly meaningless changes/addition since the first boot post install.

If no shares are seen above test computer1 with a MX Linux Live USB. It will show up as host MX1 in Thunar's Browse Network (confirmed just now). If this works we're back to my sentence immediately above.

Hopefully the above will result in your ability to 'hold the broken piece' so to speak.

[Falcon]

I decided to try the solution above. First I ran the ufw status command and verified that it came back "inactive".

Then I installed the smbclient on computer #2. Then I executed the command "smbclient -L computer#1_IP" and got the following response:
do_connect: Connection to computer#1_IP failed (Error NT_STATUS_NOT_FOUND)

Next I'll try booting computer #1 from the Live USB and then try the above again.

[Falcon]

After booting computer #1 from a USB, I reran the command in the terminal on computer #2 and got the same error as mentioned above.