Windows 10: Daisy chaining NAS / SAMBA shares across Network(s)

Hi folks

If you are messing around with say Linux / NAS servers on VMs or even a mix of real / virtual sometimes you want to connect one NAS share to another NAS server without messing around with config files etc. This daisy chains shares across entire networks including Windows machines.

For windows it's easy enough --file explorer to search network drives and connect -

For Linux you can issue a mount -t cifs command to mount the remote share -- don't use the -t smbfs any more it's obsolete if it even works at all.

The bonkers thing about this is if the mount point is defined as a samba share on server 2 then the HDD from server 1 can be accessed by any system having access to server 2 even if they don't have access to server 1 i.e "Daisy chaining" samba shares. !!!!!

This saves moving external HDD's around for example when testing servers etc. You'll get network speed of course but with a decent network should all be fine.

so

1) get IP address of remote server

2) issue mount command like the screen shot

3) enter password for the remote share at the prompt (shown in white here).

Seasoned linux users won't have a problem but I know a lot of people on this board are experimenting with NAS type servers etc and this type of command isn't always easy to find in the documentation.





Now on Windows you see my samba share HDD1 on server 2 is actually the content from SERVER 1 which doesn't have access (or vice versa) to the windows machine






Cheers
jimbo

:)

 

SMB writes to remote computer freezes or dropps to 5kbs after creator update

After installing Windows [Version 10.0.15063] my access to NAS (RaspberryPI with USB disks connected) is nearly impossible.

Coping even few megabytes to the NAS takes a long time (minutes) and often does not finish - no errors on the Samba end , just connection from Windows goes dead. Speed seems to be around 5KB/s.

Same network and same NAS with my laptop :
Windows [Version 10.0.14393] and all is working fine - 20+ MB/s - which is what I can expect from this setup and is enough for documents and source code backups.

Reading from the NAS Samba share is fast.

Reading from the laptops' share is fast.

Writing to laptops' share is 5KB/s slow as well. Laptop is sharing folder using the normal Windows SMB. All Microsoft.

Writing to NAS share , SAMBA , is slow.

Looks like any writes I do from the Creator Update computer are slow. Very Slow.

Has anybody got similar problem or solutions to a very slow , unreliable connection to SMB/Samba after the creators update?

 

Pin to Quick Access on a Mapped Network Drive

It seems to be a problem with the samba protocol, the problem is only on a NAS running linux. A large majority of NAS are using samba protocol for file sharing, that's a big problem...