I guess this might be more of a Windows problem but, just wondering if I can do anything from the Linux side to address this?
The problem is, I created an NFS share on my Antergos box. I have a Windows 10 PC accessing that share. Everything is working perfectly except for one thing. When the Windows 10 box goes to access the NFS share, upon first access, there is a slight pause and after that, I can open the share instantly. Any way to eliminate that initial pause when opening the share from the Windows box on that first try?
I also noticed that there is a red X on the share when the Windows PC reboots. But when I click on the share, it comes up (after the slight pause). Any way to avoid that red X at boot on the Windows box?
Bonus question: I noticed that when the Window box copies files over to that NFS share, they belong to the 'autologin' group. My user account on that Linux box belongs to the same group. This going to cause any problems down the road?
Lastly, this is for fellow newbies that might come across this post far into the future. When I was distro hopping, one of the things I judged distros on was how easy they made sharing files/folders via Samba so my Windows PCs on the network could access files from my Linux media server. At the time, if Samba sharing didn't work 'out of the box' or with MINIMAL configuration, I'd delete that distro and move on.
As I've used Linux more and more over the past couple of years, I've taken a liking to NFS and prefer it over Samba. The Windows 10 boxes in my house (just 2 vs the 4 Linux boxes) have zero problems access my NFS shares. Sure, with Samba, you just right click on a folder and share it. Well, right click and hope that Samba is installed and can automagically take care of all the back end things that need setup/configured. More often than not, Samba setup falls on its' face and requires you to dig through forums looking for help.
When Samba works, it's great. When it doesn't, it SUCKS for a newbie to troubleshoot things.
For NFS sharing, on my Antergos box, I started and enabled the nfs.server and rpcbind services, created my /etc/exportfs text file that tells the NFS server what I want shared and my Linux/Windows 10 boxes are accessing it perfectly fine. Save yourself some trouble, start using NFS! The hardest thing was creating the proper exportfs text file but use Google.... TONS of examples out there. To save you some time, here's mine. (If you want to use it, you'll need to probably make changes of course.)
Code:
/mnt/md0 192.168.1.1/24(rw,insecure,sync,all_squash,nohide,no_subtree_check,anonuid=1000,anongid=1000)