Samba configuration has blocked my internet access!

English Network/Internet
#1

Hi,
recently, I installed TW as Dual Boot system on a HP spectre laptop using the graphical installer and choosing “default” options whereever possible. Either I missed setting the name of my laptop during that installation or this option does no longer exist (I used to do it in my last openSUSE installations a few years ago). My laptop’s name therefore resulted in some cryptical letter combination (I think, there was linux within that name, but I’m not sure).

Now, I wanted to share some folders in my private network at home with the other (windows) computers there (the thing that you do in Windows by clicking on “share folder”). So, I started Yast>Samba and tried to set the necessary entries there. So, start on boot, allow users to share their home, membership in WORKGROUP and the netBIOS name, let’s call it “mylaptop”. From my previous experiences with Samba I was not surprised that it didn’t work (I really like Linux, but with this simple share-folders-task I have always had fights). I then had another look at manuals in the internet and tried to set all options as in this manual: https://cubiclenate.com/linux/system-configuration/simple-samba-setup/ (only the given options for the Yast>Samba configuration, I did not type anything in a linux console and I did nothing to the firewall). This didn’t help either.
However, this time it is worse than ever: My complete network connectivity is gone!

My wlan adapter seems still connected to my DSL router, but there is a warning appearing “limited network access” and I can’t reach any web pages in firefox anymore. Of course, I have stopped the Samba and rebooted several times, but without success. Samba is inactive now, but what has changed to before is, the netBIOS name is still set to “mylaptop” (I don’t know how to un-set it) and the laptop seems somehow belong to WORKGROUP. By the way, linux did never take on the new name “mylaptop” in the console. The prompt still says <username>@linux.
Furthermore, it seems possible to me that a firewall got activated, when I clicked “open port on firewall” in the Yast>Samba configuration. However, if I choose Yast>Firewall, there is nothing configured (and I haven’t done anything in this part of Yast).

Can anyone please help me, to get my network connection back?

Kind regards,
Flo

#2

Please share output from the following to start with…

sudo systemctl status network

ip a

ip r

grep -i name /etc/resolv.conf

BTW, you can copy/save the output to a file, and transfer that via a USB memory stick to an internet-connected computer and post that information here.

#3

Thank you for the reply. Here is the output (I could sent it to the harddisk partition shared with Windows):
Output 1: Just as you asked
Output 2: After setting the “static hostname” in Yast>Network connections to “mylaptop”
Output 3: After deleting the connection with the somehow strange name wlo1 in the network manager (I’m pretty sure that used to be called SSIDname before I got this network problem) and setting up the connection to my wifi new. It is now called SSIDname again, but nothing changed concerning the network connection.
The KDE message still tells me, there is a network connection but no internet access.

Output 1:


linux:~ # systemctl status network● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Sun 2022-04-24 10:54:11 CEST; 1min 28s ago
       Docs: man:NetworkManager(8)
   Main PID: 1583 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 544ms
     CGroup: /system.slice/NetworkManager.service
             └─1583 /usr/sbin/NetworkManager --no-daemon


Apr 24 10:54:16 localhost.localdomain NetworkManager[1583]: <info>  [1650790456.2428] manager: startup complete
Apr 24 10:54:16 localhost.localdomain NetworkManager[1583]: <info>  [1650790456.2828] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.4450] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.4991] dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.4999] policy: set 'wlo1' (wlo1) as default for IPv6 routing and DNS
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.4999] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.6711] dhcp6 (wlo1): state changed new lease
Apr 24 10:54:17 localhost.localdomain NetworkManager[1583]: <info>  [1650790457.7560] policy: set-hostname: set hostname to 'linux.fritz.box' (from address lookup)
Apr 24 10:54:23 linux.fritz.box NetworkManager[1583]: <info>  [1650790463.4600] agent-manager: agent[3d5c06f5640bf794,:1.29/org.kde.plasma.networkmanagement/1000]: agen>
Apr 24 10:54:24 linux.fritz.box NetworkManager[1583]: <info>  [1650790464.1332] audit: op="statistics" interface="wlo1" ifindex=2 args="500" pid=3589 uid=1000 result="s>
linux:~ # ip a
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: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether cc:15:31:3b:44:cb brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
    inet 192.168.178.32/24 brd 192.168.178.255 scope global dynamic noprefixroute wlo1
       valid_lft 863768sec preferred_lft 863768sec
    inet6 2a00:1e:df00:3401:bdb6:fcd:2474:850f/64 scope global temporary dynamic 
       valid_lft 5798sec preferred_lft 2198sec
    inet6 2a00:1e:df00:3401:ce15:31ff:fe3b:44cb/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 5798sec preferred_lft 2198sec
    inet6 fe80::ce15:31ff:fe3b:44cb/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
linux:~ # ip r
default via 192.168.178.1 dev wlo1 proto dhcp metric 20600 
192.168.178.0/24 dev wlo1 proto kernel scope link src 192.168.178.32 metric 600 
linux:~ # grep -i name /etc/resolv.confrnd 
nameserver 192.168.178.1
nameserver fd00::464e:6dff:fe19:554c

Output 2: (after setting the “static hostname” in Yast>Network connections to “mylaptop”)


linux:~ # systemctl status network
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Sun 2022-04-24 10:54:11 CEST; 9min ago
       Docs: man:NetworkManager(8)
    Process: 4900 ExecReload=/usr/bin/busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Reload u 0 (code=exited,>
   Main PID: 1583 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 1.121s
     CGroup: /system.slice/NetworkManager.service
             └─1583 /usr/sbin/NetworkManager --no-daemon


Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.3851] config: signal: SIGHUP (no changes from disk)
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5213] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
Apr 24 11:00:05 mylaptop systemd[1]: Reloaded Network Manager.
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5310] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5360] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5361] policy: set-hostname: set hostname to 'linux.fritz.box' (from address lookup)
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5892] hostname: static hostname changed from (none) to "mylaptop"
Apr 24 11:00:05 mylaptop NetworkManager[1583]: <info>  [1650790805.5893] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
Apr 24 11:02:45 mylaptop NetworkManager[1583]: <info>  [1650790965.4420] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
Apr 24 11:02:45 mylaptop NetworkManager[1583]: <info>  [1650790965.4424] policy: set-hostname: current hostname was changed outside NetworkManager: 'mylaptop'
linux:~ # ip a
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: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether cc:15:31:3b:44:cb brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
    inet 192.168.178.32/24 brd 192.168.178.255 scope global dynamic noprefixroute wlo1
       valid_lft 863916sec preferred_lft 863916sec
    inet6 2a00:1e:df00:3401:bdb6:fcd:2474:850f/64 scope global temporary dynamic 
       valid_lft 7112sec preferred_lft 3512sec
    inet6 2a00:1e:df00:3401:ce15:31ff:fe3b:44cb/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7112sec preferred_lft 3512sec
    inet6 fe80::ce15:31ff:fe3b:44cb/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
linux:~ # ip r
default via 192.168.178.1 dev wlo1 proto dhcp metric 20600 
192.168.178.0/24 dev wlo1 proto kernel scope link src 192.168.178.32 metric 600 
linux:~ # grep -i name /etc/resolv.conf
nameserver 192.168.178.1
nameserver fd00::464e:6dff:fe19:554c

Output 3: (after setting up the connection to my wifi new and rebooting)

mylaptop:~ # systemctl status network
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Sun 2022-04-24 11:42:46 CEST; 6min ago
       Docs: man:NetworkManager(8)
   Main PID: 1810 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 684ms
     CGroup: /system.slice/NetworkManager.service
             └─1810 /usr/sbin/NetworkManager --no-daemon


Apr 24 11:42:50 mylaptop NetworkManager[1810]: <info>  [1650793370.6702] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 24 11:42:50 mylaptop NetworkManager[1810]: <info>  [1650793370.6730] manager: NetworkManager state is now CONNECTED_SITE
Apr 24 11:42:50 mylaptop NetworkManager[1810]: <info>  [1650793370.6731] policy: set 'wlo1' (wlo1) as default for IPv4 routing and DNS
Apr 24 11:42:50 mylaptop NetworkManager[1810]: <info>  [1650793370.7950] device (wlo1): Activation: successful, device activated.
Apr 24 11:42:50 mylaptop NetworkManager[1810]: <info>  [1650793370.7959] manager: startup complete
Apr 24 11:42:55 mylaptop NetworkManager[1810]: <info>  [1650793375.8324] dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Apr 24 11:42:55 mylaptop NetworkManager[1810]: <info>  [1650793375.8331] policy: set 'wlo1' (wlo1) as default for IPv6 routing and DNS
Apr 24 11:42:55 mylaptop NetworkManager[1810]: <info>  [1650793375.9865] dhcp6 (wlo1): state changed new lease
Apr 24 11:42:58 mylaptop NetworkManager[1810]: <info>  [1650793378.5640] agent-manager: agent[0809a68916872767,:1.29/org.kde.plasma.networkmanagement/1000]: agent register>
Apr 24 11:42:59 mylaptop NetworkManager[1810]: <info>  [1650793379.2167] audit: op="statistics" interface="wlo1" ifindex=2 args="500" pid=2888 uid=1000 result="success"
mylaptop:~ # systemctl status network
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Sun 2022-04-24 11:42:46 CEST; 10min ago
       Docs: man:NetworkManager(8)
   Main PID: 1810 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 1.388s
     CGroup: /system.slice/NetworkManager.service
             └─1810 /usr/sbin/NetworkManager --no-daemon


Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4770] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4918] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4921] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4925] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4938] manager: NetworkManager state is now CONNECTED_SITE
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.4940] policy: set 'New SSIDname' (wlo1) as default for IPv4 routing and DNS
Apr 24 11:52:38 mylaptop NetworkManager[1810]: <info>  [1650793958.5702] device (wlo1): Activation: successful, device activated.
Apr 24 11:52:39 mylaptop NetworkManager[1810]: <info>  [1650793959.9542] dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Apr 24 11:52:39 mylaptop NetworkManager[1810]: <info>  [1650793959.9548] policy: set 'New SSIDname' (wlo1) as default for IPv6 routing and DNS
Apr 24 11:52:40 mylaptop NetworkManager[1810]: <info>  [1650793960.1085] dhcp6 (wlo1): state changed new lease
mylaptop:~ # ip a
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: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether cc:15:31:3b:44:cb brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
    inet 192.168.178.32/24 brd 192.168.178.255 scope global dynamic noprefixroute wlo1
       valid_lft 863946sec preferred_lft 863946sec
    inet6 2a00:1e:df00:3401:f5a5:d890:6fb:53d/64 scope global temporary dynamic 
       valid_lft 6075sec preferred_lft 2475sec
    inet6 2a00:1e:df00:3401:16d3:566f:ffb7:73ac/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6075sec preferred_lft 2475sec
    inet6 fe80::3bdd:4170:2a05:b7f8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
mylaptop:~ # ip r
default via 192.168.178.1 dev wlo1 proto dhcp metric 20600 
192.168.178.0/24 dev wlo1 proto kernel scope link src 192.168.178.32 metric 600 
mylaptop:~ # grep -i name /etc/resolv.conf
nameserver 192.168.178.1
nameserver fd00::464e:6dff:fe19:554c
#4

And what exactly is a problem? What is output of “ping 8.8.8.8”?

#5

Well, the problem is the missing internet access. Even for updates.
ping 8.8.8.8 works perfectly fine, no package loss, fast response.

#6

Hi
So DNS is not working, have you rebooted the router? Use external DNS (eg openDNS)?

#7

What is the output of

ping -4 google.com
ping -6 google.com
#8

Hi, Thanks for caring!

My router is a Fritz Box. There is a field about “used DNS” with two addresses but it doesn’t seem like I could change them. And I am pretty sure, I never did change anything on the Fritz Box. It gives perfectly fine internet access, if I boot Windows on my laptop instead of Linux, btw. Anyway, I rebooted it, but nothing changed.

ping -4 google.com
ping -6 google.com

gives “google.com: Name or service not known”

I tried with www.google.com and https://www.google.com, too.

In the Fritz Box, the connection to mylaptop looks good and I see no difference to the connection to other computers in my home.

Perhaps something is wrong with the DNS on my Linux laptop? In the Samba configuration, there is the field about the WINS service (or two, one for giving a remote server), perhaps that changed something permanently - even though Samba is inactive now?

Kind regards,
Flo

#9

Check the hosts entry in /etc/nsswitch.conf

grep hosts /etc/nsswitch.conf
#10

What is full output of

dig google.com
dig @8.8.8.8 google.com
#11

gives:

hosts: [NOTFOUND=return] files mdns_minimal dns wins

#12

The problem is with the “[NOTFOUND=return]” at the beginning. Change it to

hosts:      files mdns_minimal [NOTFOUND=return] dns wins
1 Like
#13

dig google.com

; <<>> DiG 9.16.25 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51764
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 43 IN A 142.251.36.174

;; Query time: 15 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Mon Apr 25 23:11:09 CEST 2022
;; MSG SIZE rcvd: 55

dig @8.8.8.8 google.com

; <<>> DiG 9.16.25 <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41443
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 124 IN A 142.251.36.238

;; Query time: 15 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 25 23:13:05 CEST 2022
;; MSG SIZE rcvd: 55

#14

Remove ‘[noparse][NOTFOUND=return][/noparse]’ completely from this line.

#15

Hi, and thank you very much!
This did the trick, I can write this forum entry from my TW installation now. The question is solved.
I have no idea, why these entries have changed order, as I only used the Yast>Samba configuration tool, but now the internet is back :slight_smile:

To prevent me opening another thread with very similar contents as this one tomorrow:
What manual is a good suggestion for setting up a simple samba share with a Windows 10 computer in my local network?

( So far I had used
https://cubiclenate.com/linux/system-configuration/simple-samba-setup/

and I saw this one (but that expects manually editing the config file)
https://forums.opensuse.org/content.php/199-Configure-Samba-for-Local-Lan-Workgroup

There is also a tab “share” in the KDE/Dolphin file manager. Can this do this simple samba configuration for just sharing a folder in the local WORKGROUP or is the samba setup necessary beforehand? )

Kind regards, and thank you once again for bringing the internet back!

#16

Good to read of your progress here.

To prevent me opening another thread with very similar contents as this one tomorrow:
What manual is a good suggestion for setting up a simple samba share with a Windows 10 computer in my local network?

( So far I had used
https://cubiclenate.com/linux/system-configuration/simple-samba-setup/

and I saw this one (but that expects manually editing the config file)
https://forums.opensuse.org/content.php/199-Configure-Samba-for-Local-Lan-Workgroup

The samba wiki documentation is a good place to start…
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server

There is also a tab “share” in the KDE/Dolphin file manager. Can this do this simple samba configuration for just sharing a folder in the local WORKGROUP or is the samba setup necessary beforehand? )

The concept of WORKGROUP is deprecated (it relied on SMBv1). The Dolphin samba sharing plugin is useful, but limited to sharing within the user’s home environment obviously.

Kind regards, and thank you once again for bringing the internet back!

Glad to have been of guidance. :slight_smile:

#17

Works for me too, thanks a lot!

#18