What to do, linux does not see the windows network?

Question

linux

Debian 9 was installed on the lenovo laptop, everything is fine in principle, but it does not let windows into the ball.
It also does not see the windows network (20 PCs).
And the situation is that from time to time he still sees the network, that is, at first he saw the network and even connected to the ball, the next day he did not see the windows network. Today I saw the network (before the reboot), now it does not see it again. All PCs are pinged. tried to edit smb, did not help.
I tried to install Mint linux, elementary os, the problem is the same, Windows does not see the network, but everything pings.
what could be the problem? he sees, he does not see, 3 days of googling did not bring results.
I'm new to Linux and have never worked before.
I tried to run live versions of Linux on other laptops, the result is the same, windows does not let me on balls.
Everything is hooked up to mikrotik rb2011uias-2hnd-in.
On the Windows ball, the entrance is for everyone, the firewall turned off, the result is zero.

Answer 1

I think it's in the protocols. Turn on support for legacy protocols in Windows, this is in the installation and removal of components (look on the Internet for more details). Or in Linux, read about the option client min protocol = in smb.conf - this is about logging into Windows.
And about the visibility of the windows network, if you meant the display of the network environment, then perhaps this is also due to the smb protocols and everything will be fixed after 1 paragraph, if not, then read about the wins service and the master browser in the Windows network environment from under linux and about the options local master = , os level = , preferred master = and wins support =
- these options in smb.conf are responsible for making linux itself become the master (perhaps the options are outdated, this is from my old records
) Lanman Station]➙[Enable Insecure Guest Entrances]➙[Enabled]
It blew 10k when I needed stupid access without any fuss.

Answer 2

There are actually TOO many ambiguities here.
I worked on different PCs at different jobs ALWAYS.
Windows-Windows is seen ?? PCs in the same workgroup ??
And the advice that was given to me a long time ago is to google the console SMB client and connect via the Windows IP. The console client will issue ERRORS WITH DESCRIPTION. Namely, they need to be dealt with. Maybe he wrote a log somewhere.
I would start with IP ping and then console client. Forget the names for now.
PS they in one subnet though??

Answer 3

"Pings" and "balls" are different OSI levels, the higher ones depend on the lower ones, but not vice versa ("ball" is higher). To "see" a working group or a domain, the machine must be a member of it, has this been done? Actually, this is quite simple to do, it will be more difficult to see Linux from under Windows.