bb-qq
Multiple disconnection problem. Unable to access locally.
Description of the problem
Multiple disconnection problems. I cannot connect locally to my NAS with my domain name, but only with my private address 192.168.1.xxx:yyyy
Description of your products
Synology DS 920+ Linux DS920 4.4.302+ #72806 SMP Mon Jul 21 23:14:27 CST 2025 x86_64 GNU/Linux synology_geminilake_920+ DSM 7.2.2-72806 Update 4 ethernet dongle UGREEN CM648 USB-C RJ45
Description of your environment
Adapter connected from switch 2.5G to a 2.5Gb port on a Synology RT6600ax router cable category Cat.7
Output of dmesg command
Output of lsusb command
|__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |__1-2 05e3:0608:8538 09 2.00 480MBit/s 100mA 1IF ( ffffffd6ffffffa3ffffffebffffffcb) hub |__1-2.1 0463:ffff:0100 00 1.10 12MBit/s 20mA 1IF (EATON Eaton 3S Blank) |__1-2.4 0403:6015:1000 00 2.00 12MBit/s 90mA 1IF (dresden elektronik ConBee III DE03217673) |__1-4 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 7F00047D2A13F280) |__usb2 1d6b:0003:0404 09 3.00 5000MBit/s 0mA 1IF (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |__2-1 0bda:8156:3104 00 3.20 5000MBit/s 256mA 1IF (Realtek USB 10/100/1G/2.5G LAN 4013000001)
Output of ifconfig -a command
docker0 Link encap:Ethernet HWaddr 02:42:19:59:79:56 inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:189245 errors:0 dropped:0 overruns:0 frame:0 TX packets:199245 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:150381627 (143.4 MiB) TX bytes:112827942 (107.6 MiB)
docker657 Link encap:Ethernet HWaddr F2:A9:06:A5:72:7F UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:137958 errors:0 dropped:0 overruns:0 frame:0 TX packets:126429 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:61270678 (58.4 MiB) TX bytes:51483931 (49.0 MiB)
eth0 Link encap:Ethernet HWaddr 00:11:32:CA:AD:63 inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1017841344 errors:0 dropped:0 overruns:0 frame:0 TX packets:622645485 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:595925665584 (554.9 GiB) TX bytes:34229712944 (31.8 GiB) Interrupt:97 base 0xc000
eth1 Link encap:Ethernet HWaddr 00:11:32:CA:AD:64 inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:96 base 0xe000
eth2 Link encap:Ethernet HWaddr 6C:1F:F7:15:BD:58 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:152529986 errors:0 dropped:0 overruns:0 frame:0 TX packets:5850565 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87588681018 (81.5 GiB) TX bytes:8112764234 (7.5 GiB)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:22297329 errors:0 dropped:0 overruns:0 frame:0 TX packets:22297329 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:11040157911 (10.2 GiB) TX bytes:11040157911 (10.2 GiB)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tun1000 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:169.254.135.116 P-t-P:169.254.135.116 Mask:255.255.248.0 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:11493 errors:0 dropped:0 overruns:0 frame:0 TX packets:18624 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1437543 (1.3 MiB) TX bytes:18207691 (17.3 MiB)
If you are using SMB(file share) and can consistently access it using the IP address, then it's an issue with the machine name resolution service.
And this makes it important to know which machine is the "browse master", which will likely make debugging difficult.
Registering the IP address in the Hosts file might be the simplest solution.
