I have been following the Tutorial viewtopic.php?f=42&t=199907 . Have a few questions to the latest on this topic. I have Windows Home Network with Windows 10 PCs and Laptops. All OSs up-to-date. I have a need to get an old PC up and running with an OS lighter than Windows and yet feels like Windows (for the family). Had been checking out Zorin, Ubuntu, Mint, Debian and presently evaluating Mint Tricia (Mate) as the choice to come out of Windows.
I have tried the steps in the Tutorial. Here's my situation:
- PC1-nosmb1: Windows 10, SMB1 disabled
- PC2-smb1: Windows 10, SMB1 active by default (not the one that deactivates automatically)
- PC3-TMate64: Virtual Machine running Mate on Virtualbox with Bridge connection to PC1-nosmb1 Ethernet. Mate comes up as a separate box in the Network, can track using my Router, received its unique IP from DHCP.
- I can access Windows Share from PC3-TMate64 box. I have modified smb.conf to include Windows Workgroup Name, lanman, ntlm authentication. Have also put max, min client protocol but that doesn't seem to be making any difference. Have implemented WSDD in PC3-TMate64
- [1.1] PC1-nosmb1 never comes up ever in the Caja Explorer Network view or Nemo. But if I put smb://PC1-nosmb1.local, I can view the shares, access the shares, open files.This doesn't seem to happen at first attempt. I have to run
Then attempt again with smb://PC1-nosmb1. This works till I reboot the Mate64. After reboot, perform the same ritual.
Code: Select all
pidof gvfsd-smb-browse Kill $pid
- [1.2]PC2-smb1 comes up in Network view of the File explorers unlike PC1-nosmb1. Still to access the shares, I must perform the ritual (mentioned above) at first, then access the shares using smb://PC2-smb1
- [1.3]Windows Workgroup seems to be coming up, not consistently, in the Network view of Caja, Nemo (more consistently). If I rest the PC3-TMate64 a few mins after reboot, chances of seeing Windows Workgroup in the Network view increases. But that's all, I can't get into the Windows PCs without using smb://
- [1.4]Have also installed Gigolo. It fails to go into the shares and mount, although it can list the shares if I use mDNS. For Domain field, I put Workgroup name, User as the Admin-user of PC3-TMate64. There is a following password prompt where I key in the PC3-TMate64 admin pwd. The error thrown up is "Failed to mount Window share:Connection refused". If I had shares mapped by doing the steps in sub-points 1 and 2 above, those shares come up in the view list of Gigolo.
 PC1-nosmb1 can see PC3-TMate64 by smb://PC3-TMate64.local . But PC3-TMate64 fails to come up in Network section of File explorer. Able to access Share.
 PC2-smb1 can see PC3-TMate64 listed under Network section of File Explorer. Able to access Share. smb:// works too.
So, with WSDD (WSD) on Linux, still I can't see PC3-TMate64 from PC1-nosmb1, listed in Network section of Windows File Explorer...to do that I must enable SMB1.0/CIFS client.I remember PC3-TMate64 coming up briefly and laboriously in Windows File Explorer Network section when I had WSD set up first time. Was not able to access the Linux Share. Then enabled SMB1.0/CIFS client, immediately PC3-TMate64came up in the Network Section and was able to access. Now after removing SMB1.0, PC3-TMate64 fails to come up even once in the File Explorer Network section.
I do not wish to continue using SMB1.0 in Windows. I believe altair4 mentioned at the beginning of the tutorial that without SMB1.0 enabled in Windows, there is no way the Linux box will come up listed under Network in File Explorer of Windows.
Do you see any problem with what the setup mentioned above? Has there been any major progress to do things any differently and subsequently easier, especially the browsing of PCs under Network and accessing Shares, from Linux and Windows?
Thank you for all the help!
Trying to attach to dump text file