12-08-2018, 05:17 PM
First, as a Windows user, you should know that Windows in general, since Windows 95, has continued to display the same annoying kind of buggy dysfunctionality concerning networking; clearly rooted in the same cause: the ridiculous redundancy in its graphical user interface. Because of the rocket pace of Web development, the Windows GUI beginning with Windows 8 has fallen far behind; and become an even worse example of non-intuitive humanly responsive software. Applications work well enough, but are severely compromised, over taxed, and limited by the patchwork quilt that is the GUI integration. This is so true that Windows developers themselves have evolved into experimenters; generally unaware of the results of their efforts until well after the fact, quite often completely unaware of whether or the not their efforts will integrate completely and reliably into the GUI. NTFS itself came to be partly because of this very issue, and the ridiculous redundancy of file explorer in the GUI.
Reading through your posts again I can see that you have experienced issues common to Windows networking. You mention the file size anomaly. This is directly caused by the way file explorer is so redundantly integrated into the GUI. I suggest installing an alternative Commander style file manager to eliminate this problem. The anomaly of VLC (which is cross-platform compatible) only playing a few seconds of a music file is caused by the same issue as well. The whole file was probably uploaded, but with multiple headers and carriage returns added by file explorer, or the wrong file location uploaded, as is common for Windows. Error reporting and packet confusion during uploads often occurs for these same reasons.
You mention you are on 1803 which now has an OpenSSH server and client available for installation. It is a simpler solution in that Windows networking configurations for file transfers do not really come into play. Coupling it with a Commander style file manager should eliminate most of the erratic file transfer issues you are experiencing with Samba and file explorer.
If you want to go for overkill, and/or add simpler functionality to most of the network file handling protocols available to Windows I suggest you may want to install cyberduck, a far reaching open source solution for Windows networking. I have never used it, (but I get paid not to have Windows networking problems in general) but it has got very good reviews, and it is open source.
https://cyberduck.io/
Because you have an OS (Linux Lite) on your server I am assuming you are not running headless. If you are using a local server address via a direct ethernet connection (not through a router) i/e 10.xx.xx.xx I think you might have better luck, and be happier with RDP. 1803 makes this easy as well. Once it is set up, (I would use the Remmina client on the Linux Lite end) change the RDP port from 3389 to something more obscure, or use an SSH tunnel for authentication. With RDP remotely logged in with a Windows administrative account, the Windows CLI and power shell are simply accessible on your Linux Lite desktop as well. RDP and SFTP should give you the least problematic experience and the least problematic way forward.
Finally, since you seem to have Samba 1 working and connecting I would try installing a Windows 10 compatible Commander style file manager first and using Samba from it and see if your error issues resolve.
TC
Reading through your posts again I can see that you have experienced issues common to Windows networking. You mention the file size anomaly. This is directly caused by the way file explorer is so redundantly integrated into the GUI. I suggest installing an alternative Commander style file manager to eliminate this problem. The anomaly of VLC (which is cross-platform compatible) only playing a few seconds of a music file is caused by the same issue as well. The whole file was probably uploaded, but with multiple headers and carriage returns added by file explorer, or the wrong file location uploaded, as is common for Windows. Error reporting and packet confusion during uploads often occurs for these same reasons.
You mention you are on 1803 which now has an OpenSSH server and client available for installation. It is a simpler solution in that Windows networking configurations for file transfers do not really come into play. Coupling it with a Commander style file manager should eliminate most of the erratic file transfer issues you are experiencing with Samba and file explorer.
If you want to go for overkill, and/or add simpler functionality to most of the network file handling protocols available to Windows I suggest you may want to install cyberduck, a far reaching open source solution for Windows networking. I have never used it, (but I get paid not to have Windows networking problems in general) but it has got very good reviews, and it is open source.
https://cyberduck.io/
Because you have an OS (Linux Lite) on your server I am assuming you are not running headless. If you are using a local server address via a direct ethernet connection (not through a router) i/e 10.xx.xx.xx I think you might have better luck, and be happier with RDP. 1803 makes this easy as well. Once it is set up, (I would use the Remmina client on the Linux Lite end) change the RDP port from 3389 to something more obscure, or use an SSH tunnel for authentication. With RDP remotely logged in with a Windows administrative account, the Windows CLI and power shell are simply accessible on your Linux Lite desktop as well. RDP and SFTP should give you the least problematic experience and the least problematic way forward.
Finally, since you seem to have Samba 1 working and connecting I would try installing a Windows 10 compatible Commander style file manager first and using Samba from it and see if your error issues resolve.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.