[smitelli]

I have been nerd-sniped into conjuring up a less-traveled-path technique:

Portable Python on the Windows computer. `python -m http.server`. On the Linux computer, something like `wget -mkp` followed by `find … -delete` to get rid of the index files.

(Lots of disks are soldered in nowadays, or the procedure might require multiple M2 slots that the destination mobo might not have. Is your company IT department happy to know their hardware is being disassembled?)

I have not benchmarked to see if this would sustain the 120 Mbps the original scenario would require.

[sdenton4]

Or set up SFTP on the Linux machine, and find whatever Windows crapware that's able to connect to it... Filezilla, maybe?

[zamadatix]

Windows has had OpenSSH's ssh/sftp/scp client binaries built in by default for ~7 years now. You can also do this in reverse by enabling OpenSSH Server on Windows (included feature but not installed or enabled on boot by default) and having the sftp client be the Linux box, which can be easier depending which you have more control of.

[chris_engel]

Or just... put in a usb thumb drive, move the 50gb on it and call it a day?

[mouse_]

I was gonna say nginx, lol. It's smaller and more portable than python afaik

[nicce]

Or just use PowerShell! It can run HTTP server too.

[pphysch]

I've done this exact approach and it worked well, it was on LAN so plenty of throughput. I would definitely try this before tearing apart the hardware.