Answer the question
In order to leave comments, you need to log in
Android stopped opening balls on Win10, how to fix?
Android stopped connecting to Windows 10 balls. Apparently after some kind of update. And by the next machine with the same ten continues to work.
On the other dozen, it connects to the target.
From the deb, smbclient connects with the -m SMB2 key, without it it does not connect.
On the target machine
SmbServerConfiguration -EnableSMB1Protocol $true
SmbServerConfiguration -EnableSMB2Protocol $true
My diagnosis is that the android connects via the smb1 protocol, but for some reason Windows does not want to see it, even though it is enabled, and there is no way to fix it.
Ports are open 137/udp 138/udp 139/tcp 445/tcp
Please help me understand. If you need any logs - tell me which way to look at them.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question