Windows nao reconhecendo samba com cabo de rede

Linux
1

entao gente, eu tenho dois notebooks e uso os dois simultaneamente e queria ter essa troca rápida entre um e outro e comecei a utilizar o samba, só que estou enfrentando um problema, quando eu conecto o cabo de rede no notebook que ta o servidor samba não consigo acesso pelo notebook com o windows que ta via wifi, o que posso fazer?

(quando eu tiro o cabo de rede o windows reconhece normalmente)
(ja tentei conectar com o ip do cabo de rede e o wifi ambos ele nao encontra)

2

Pode ser problema da placa de rede.

Qual o drive dacplaca?
lspci

3

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

4

Ok…

As saidas dos comandos

ip link

ip ad

Já tentou colocar um ip fixo?

5

ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 1c:39:47:5f:d1:f3 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 5c:c9:d3:88:39:fb brd ff:ff:ff:ff:ff:ff

6

ip ad

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 1c:39:47:5f:d1:f3 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.6/24 brd 192.168.100.255 scope global dynamic noprefixroute enp1s0
valid_lft 65251sec preferred_lft 65251sec
inet6 2804:2c00:540:a068::3/128 scope global dynamic noprefixroute
valid_lft 226293sec preferred_lft 139893sec
inet6 2804:2c00:540:a068:e4e7:39c4:2c3f:11e4/64 scope global temporary dynamic
valid_lft 226292sec preferred_lft 64690sec
inet6 2804:2c00:540:a068:80ef:b61c:7cd4:17ca/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 226292sec preferred_lft 139892sec
inet6 fe80::ce66:ffb5:2d66:af9e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 5c:c9:d3:88:39:fb brd ff:ff:ff:ff:ff:ff

7

Cara foi mal

Eu pensei que não acessava a rede…
Pensei que nào estava pegando um ip…

Vamos lá…

Passa a configuração do samba

/etc/samba/smb.conf

8

[global]
workgroup = jonatas

[Compartilhamento]
comment = comentario
path = /home/jonatas/smbd
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Documentos]
comment = comentario
path = /media/jonatas/Disco de Dados/Documentos
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Filmes e Series]
comment = comentario
path = /media/jonatas/Disco de Dados/Filmes e Series
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Imagens]
comment = comentario
path = /media/jonatas/Disco de Dados/Imagens
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Videos]
comment = comentario
path = /media/jonatas/Disco de Dados/Videos
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Winrar]
comment = comentario
path = /media/jonatas/Disco de Dados/Winrar
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Instaladores]
comment = comentario
path = /media/jonatas/Disco de Dados/Instaladores
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Musicas]
comment = comentario
path = /media/jonatas/Disco de Dados/Musicas
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Faculdade]
comment = comentario
path = /media/jonatas/Disco de Dados/Faculdade
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

[Isos]
comment = comentario
path = /media/jonatas/Disco de Dados/Isos
read only = no
guest ok = yes
force create mode = 0755
force user = jonatas
force group = jonatas

9

em global adicione

workgroup = JONATAS
server string = Server Linux
netbios name = LINUX
client min protocol = NT1
server min protocol = NT1
dns proxy = no
name resolve order = lmhosts bcast host wins
domain master = auto
local master = yes
preferred master = yes
idmap config * : backend = tdb

Com este configuração você pode limitar o acesso na sua somente na sua rede

hosts allow = 127.0.0.1 192.168.2.0/26
hosts deny = 0.0.0.0/0
interfaces = lo enp4s0
bind interfaces only = yes

aqui vc pode determinar permissão
create mask = 0644
directory mask = 2755
force create mode = 0644
force directory mode = 2775

teste e veja se funciona

10

todas essas informações são em [global]?

11

sim…

acho que só com
server string = Server Linux
netbios name = LINUX
client min protocol = NT1
server min protocol = NT1

já deve funcionar…

o resto pode ver aqui o que é

https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html

e atenção…

vc deve ter o serviço netbios ligado no samba

pode ser nmb.service

não sei qual é no mint.
entao

sudo systemctl enable nmb.service
sudo systemctl start nmb.service

12

Failed to enable unit: Unit file nmb.service does not exist.
root@pop-os:/etc/samba# systemctl start nmb.service
Failed to start nmb.service: Unit nmb.service not found.
root@pop-os:/etc/samba#

13

systemctl enable --now nmbd?

1 curtida
14

ainda nao ta indo gente, o windows nao reconhece com o cabo de rede conectado

15

vc tem que reiniciar os aer4viços

smbd
nmbd

sudo systemctl restart smbd nmbd

mas talvez reiniciando o pc seja melhor

16

só pra eu entender, no windows 10 eu pesquiso por (duas barras invertidas)(endereço ipv4) ne?

17

sim…

mas pode pesquisar pelo nome da máquina também

fica mais fácil

no navegador do windows 10 tem a opção de visualizar as estações…

e é para isso que ativamos o serviço netbios

18

systemctl staus nmbd.service fala que o nmbd deu falha, e quando tento restartar ou startar ele trava o terminal e da falha na inicializacao do servico

19

Job for nmbd.service failed because a timeout was exceeded.
See “systemctl status nmbd.service” and “journalctl -xe” for details.

20

O smbd funciona

systemctl -l status smbd nmbd