Best books for a beginner on networking in system administration?

Question

Books

I am engaged in programming and have not yet clearly defined who I want to be in it. At the moment I know such technologies as: html, css, sass, js, jquery (a little), php (a little), sql, mysql, photoshop, git, java se, javaFX (superficially), some basic windows and linux commands, worked with virtual box and like everything.
Now I decided on system administration and made the following plan:
1. Network technologies 2.
Windows command line
3. Windows administration
4. Remote administration
which will give the most important knowledge and will be easy to perceive.
Question 2 - are computer technologies and network technologies the same thing?
3 question - how is the plan in general?

Answer 1

Books - IMHO useless Talmuds in the case of mastering basic knowledge. You need to read the product documentation.
Your plan seems sound. You can learn by jumping between points, so that the brain does not turn sour from the same type of load. Detailing:
It is also worth remembering that choosing only networks and Windows, you limit yourself only to work in the Enterprise segment and providers, the competition there will grow and not in your favor.

Answer 2

The most important knowledge in networks is theory. On networks, there is a good channel by Andrey Sozykin for beginners.
Computer technology and network technology are two different things.

Answer 3

And I would start reading "Networks for the smallest." linkmeup.ru/blog/11.html
And do everything they say.

Answer 4

1. "Computer Networks" - there are two very good books on networks with the same title, the first by E. Tanenbaum, the second by Olifer. There is also a good series of articles on Habré "Networks for the smallest".
2. It really makes no sense to get excited on cmd, it's better to spend time on powershell.
3. Windows/Linux administration is a very large piece of material, on an equal footing with programming or network administration. And if in network administration, having mastered the basic knowledge and CLI of one vendor, it will not be difficult to deal with other vendors. With the administration of systems, this will not work, because in most cases it is not the system itself that is administered, but the services that are raised based on some OS.
4. What is remote administration? RDP/SSH/IPMI/Hyper-V/ESXi what?
It is worth deciding on the direction to which there is more interest in development or administration, because there is a lot of information and mastering everything at a qualitative level is simply unrealistic. If you are developing for the WEB, then you should limit yourself to understanding the OSI models, the operation of DNS services, IIS, Apache, NGINX, Failover Cluster, NLB Cluster, SSH, WinRM, Bash, PowerShell, Reverse Proxy (Apache, Nginx, IIS), IPVS, iptables, windows firewall. The list is far from complete from what I quickly remembered. Relying on Windows administration only when developing for the web is short-sighted, because most of the servers are still on Linux.