A few questions on computer networks: how to make two windows machines see each other? How exactly is the OSI implementation encapsulated?

Question

Computer networks

1. I connected two computers directly using an Internet cable, one running windows 7, the other windows 10. Why doesn't windows 10 see windows 7 in Explorer on the network tab? windows 7 saw windows 10, but not on the first try (updated the explorer interface several times). And then I connected the computers through the hub - now win7 has stopped seeing win10 at all. Turned off the firewall on both computers, allowed all rights in home and public networks (although these rights only do what regulate certain firewall rules). Tried to enable - disable dhcp. The question is how to set up a connection so that computers (with win7 and win10) see each other (not only ping, but also browsing folders) without any problems? I just started studying networks, I decided to start with the simplest thing - to combine two computers into a network, and then such a bummer awaits me, which makes you think of networks as something magical and incomprehensible, and all this is set up only with the help of a tambourine and such and such a mother. Not the most pleasant feeling.
2. More than once heard the expression "if the protocols change, there is no need to change the entire system." Let me explain my understanding. Let's take the tcp protocol, change it. Let's change the software that implements the protocol. Let's leave the tcp interfaces unchanged. We will implement the software in all computers on which the modified protocol is supposed to be used. And the network begins to function (provided that the modified tcp protocol algorithm is correct and the software implements it correctly). Is my understanding correct? I took tcp on purpose, because it lies between other levels.
3. Are the tcp and udp protocol interfaces the same? Let's say I created my protocol at the 7th application layer, and connected it to tcp. Can i connect to udp without changing the code,
4. Let's take two types of communication: wired and wifi. Both types can work with the Internet, in other words, see each other. How exactly is functionality encapsulated? Do both of these types of communication have the same interface for the higher layer? Or maybe the interfaces are different, but the higher level connects to these two interfaces at the same time?
Anticipating the questions "read books" - I read, but have not yet reached the material that would answer my questions. Couldn't find it on google either.

Answer 1

First, the ethernet cable, but it doesn't matter. It is important that the Microsoft SMB protocol does not work very well with multiple network adapters.
1) set up an address on one computer, for example, 192.168.142.41, and on the second, 192.168.142.42.
2) and the doer in the network settings, disable the Microsoft share protocol on the other adapters or something.

Answer 2

You asked questions for a couple of chapters of the book.
The easiest to understand https://www.ibm.com/developerworks/en/library/l-li...
For a deeper understanding

The Linux source code is a great way to learn about driver design for many types of devices, including network device drivers. You will find differences in the design and use of the available kernel APIs, but each will be useful either as instructions or as a starting point for a new driver.

Answer 3

The question is how to set up a connection so that computers (with win7 and win10) see each other (not only ping, but also browsing folders) without any problems?
Computers do not see each other using protocols. Using protocols, different programs can exchange data.
You need to understand how the "Windows Firewall" service differs from the "Computer Browser", what is a shared resource. Actually, in a peer-to-peer windows network, visibility in Explorer depends on the "computer browser". But instead, you can simply directly access the network resource by its wins name (\\server\resource)
. Again, you can’t just turn DHCP on and off and wait for the result if you don’t understand what DHCP does and what it affects.
Do not get into the jungle until you understand the basics. The OSI model contains layers to isolate some and link others. That is why the TCP protocol works not only over ethernet, but also over pptp and over a bunch of other protocols. Therefore, you can get the Internet both via an ethernet cable and via a satellite and via a modem, and so on.

Answer 4

I read, but have not yet reached the material that would answer my questions

Olifers

Answer 5

Since you do not have a domain controller and other services (for example, a WINS server), it means that you are using the Workgroup mode, the list of computers on the network of machines with windows is collected independently, i.e. they will appear/disappear in the list immediately. The workgroup name for computers must match , it is configured in the properties Computer -> Advanced system settings -> Computer name tab -> Change button.
For users to have access to folders on another computer in the workgroup, their usernames and passwords must match , otherwise a password prompt will appear. By default, users without a password do not have access to the remote machine .(this can be changed in the policies of this remote machine). Also, in the folder sharing settings, you must specify the appropriate user (or 'Everyone') and access rights. File and directory permissions for the NTFS file system must also take into account access for this user.
The computers must be connected to the same local network and they must have IP addresses from the same network, for example 192.168.0.1 - 192.168.0.255 when using the mask 255.255.255.0. Usually, when using a router, all addresses are issued automatically (there is a dhcp server there), by the way, windows 7+ can use ipv6 addresses, ..
ps tip, on windows 7, do not select the network type 'Home', select 'Enterprise Network'.
pps another tip, exclude Russian-language usernames (and spaces in names), even if the local network works, problems will come out in games and third-party programs that are not ready for this.
-----------
For applications in the code, there is almost no difference when connecting tcp or udp, it's just a flag in the method, but you need to understand that udp does not guarantee that the data will arrive in the order in which they left, including some packets may not arrive at all, .. this forces developers to control this (this is the price for the higher 'performance' of udp compared to tcp).
You don't need to create your own ip protocol. I don’t know who told you “if the protocols change, you don’t need to change the entire system”, but perhaps they meant protocols and application communication formats, for example, in windows machines transfer files using the smb protocol, and in linux networks, administrators can choose nfs (support for which in windows is discontinued, and it was previously limited with bugs, I believe intentionally), these protocols are not compatible, roughly speaking, this is exactly how files will be transferred over the network.
wifi and wired ethernet - they have differences at the link level, this is a level below ip protocols, and it makes no difference for them and above, data can be transmitted in any way, even on pigeons (in rfc, as I remember, even this option was described), although applications may take into account the characteristics of the radio channel (speed and pings, for example).