Edit: browsed the DJGPP website and found answers, there are libs available.
In DOS times you only had one core, so there was no particular necessity for multithreading. Network card drivers were available using the NDIS standard: http://www.freedos.org/wiki/index.php/Networking_FreeDOS_-_N...
DOS games tended to roll their own protocol on top of the raw packet drivers. This is why they were often LAN-only. Generally in the DOS era you didn't have Internet; it existed, but wasn't widely deployed.
DJGPP got some use (see the PCGPE as well), but professional game development tended to use Watcom: http://www.openwatcom.org/index.php/Project_History
So you'd download the day's schedule or updates by copying the file off the network and use a few primitive means of coordinating things like using 'flag' files for signaling and then if exists xxx / echo foo > do_bckup.txt type things in your batch files.
It's very primitive, but most things were at least doable and you could always write small programs to extend your scripts if need be.
I was able to deploy updates via a similar mechanism. There was a network script called from autoexec.bat. I would make a few changes to have it pull in the new updates from the network, then tell them to reboot at their convenience. So I almost never had to leave my desk to deal with them, except for a restore from backup.