Score:0

Very long startup time on fixed IP Ubuntu Server 20.04 LTS running SAMBA

ph flag

My Ubuntu Server 20.04 LTS running SAMBA It has a fixed IP address is 192.168.20.235. My routers gateway is 192.168.20.1

Upon startup the last message takes 1-2 minutes every time:

[  OK  ] Reached target Network (Pre).
Starting Network Service...
Starting Wait for Network to be Configured...
Starting Network Name Resolution.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[**    ] A start job is running for Wait for Network to be Configured (XX / no limit)

The Server is "hanging" in this line for 1-2 minutes. Then eventually gets connection.

I have seen a similar question here: Very long startup time on Ubuntu Server (network configuration) However the answer to this question does not take into account that I am using a fixed IP address.

I do not have a similar problem on my old 16.04 server, which I made following Franks guide.

Both servers and all 10 (ten) windows 10 computers in the house uses the same WORKGROUP (as defined in /etc/samba/smb.conf), yet the old server shows up more easily in windows 10 "this computer" and "network" without having to access it directly \192.168.20.235.

My server gives the following output to this command "cat /etc/netplan/*.yaml":

This is the network config written by 'subiquity'
network:
  ethernets:
    eno1:
      dhcp4: true
    eno2:
      addresses:
      - 192.168.20.235/24
      gateway4: 192.168.20.1
      nameservers:
        addresses:
        - 192.168.20.1
        search: []
  version: 2

/etc/netplan/ contains one file named "00-installer-config.yaml" with the above contents.

ip addr show gives the following output:

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: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 4c:72:b9:21:01:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.235/24 brd 192.168.20.255 scope global eno2
       valid_lft forever preferred_lft forever
    inet6 fe80::4e72:b9ff:fe21:107/64 scope link
       valid_lft forever preferred_lft forever
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 4c:72:b9:21:01:08 brd ff:ff:ff:ff:ff:ff

I wonder if the "version 2" part should be earlier in the file? Should I modify my router settings to assign a static IP to the MAC address of the server? (I did not do that with my old one). I have not setup NETBIOS or cloud

The server has not been setup for access from outside the home network.

Any advice will be highly appreciated and just ask away if you have any question. I will answer as quickly as possible.

in flag
Are both of your ethernet ports used? Or does `eno1` remain unplugged all of the time?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.