Tjyylli

What does 丫 mean? 丫是什么意思？

Special flights

The Nth Gryphon Number

Mounting TV on a weird wall that has some material between the drywall and stud

If Windows 7 doesn't support WSL, then what is "Subsystem for UNIX-based Applications"?

White walkers, cemeteries and wights

Can an iPhone 7 be made to function as a NFC Tag?

Resize vertical bars (absolute-value symbols)

Found this skink in my tomato plant bucket. Is he trapped? Or could he leave if he wanted?

Does the Mueller report show a conspiracy between Russia and the Trump Campaign?

Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?

Asymptotics question

How do living politicians protect their readily obtainable signatures from misuse?

Why are vacuum tubes still used in amateur radios?

Is it dangerous to install hacking tools on my private linux machine?

Is CEO the "profession" with the most psychopaths?

GDP with Intermediate Production

RSA find public exponent

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

Flight departed from the gate 5 min before scheduled departure time. Refund options

AppleTVs create a chatty alternate WiFi network

I can't produce songs

Was Kant an Intuitionist about mathematical objects?

Tannaka duality for semisimple groups

Occasionally losing wired LAN connection on Ubuntu 16.04

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

11

4

I've recently put Ubuntu MATE 16.04 on a computer, which I'm using as a file server, among other things. Twice in the past few days it's lost connection to the LAN. I was in a hurry to get it back up, so I unplugged the connection and replugged. It pulled an IP address again and reconnected to the network.

Now I'm starting to think it probably wasn't just an isolated incident and I'm going to have to figure out why it's losing its connection.

The first time it happened I noticed the network didn't have IP/DNS etc, but I didn't dig any further than that.

The next time this happens, how should I go about figuring out why the network device has lost the DHCP info and didn't query the DHCP server for a new lease (unless it did and failed for some reason)?

Update: I was going through some steps trying to diagnose what's been going on, I started off from this guide. When I got down to dhclient and ran sudo dhclient the machine reconnected to the network.

Pastie of diagnostics while I was disconnected. Did I miss anything?

Update 2: I think I found the culprit in /var/log/syslog.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Withdrawing address record for 192.168.1.200 on enp4s0.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.1.200.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Interface enp4s0.IPv4 no longer relevant for mDNS.

networking ubuntu

share|improve this question

edited Jun 11 '16 at 16:55

leetwanker

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

bumped to the homepage by Community♦ 6 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Check cables to make sure they are not bad? Check if energy savings options are off to prevent network card sleep?
  
  – Peter
  Jun 10 '16 at 5:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is probably un-constructive, but if all you are using it for it a file-server, why do you need a GUI? Why not ubuntu-server? Although, I am not sure if this would fix your specific issue, I would first look into the Network-Manage service and Setting to see if there is a configuration issue. Maybe it is stopping? Or Maybe if you go to Edit Connections and select the Wired Connect 1 Unless you renamed it (Mine is called "Auto Wired") and under general make sure Auto Connect when network is available.
  
  – asmith
  Mar 2 '17 at 7:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It could also be that on top of what Peter said, if you have a cable issues, router/switch issue where port disconnects or get powered down, or power saver is on and those with the Auto Connect not selected would cause this to happen every time there is a temp loss of network connection, even milliseconds.
  
  – asmith
  Mar 2 '17 at 7:44
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Does this article help? hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues
  
  – Jeremy J Wong
  Jun 1 '17 at 23:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Or ubuntugeek.com/…
  
  – Jeremy J Wong
  Jun 1 '17 at 23:56
  

  
  
  
  

 | 
show 7 more comments

11

4

I've recently put Ubuntu MATE 16.04 on a computer, which I'm using as a file server, among other things. Twice in the past few days it's lost connection to the LAN. I was in a hurry to get it back up, so I unplugged the connection and replugged. It pulled an IP address again and reconnected to the network.

Now I'm starting to think it probably wasn't just an isolated incident and I'm going to have to figure out why it's losing its connection.

The first time it happened I noticed the network didn't have IP/DNS etc, but I didn't dig any further than that.

The next time this happens, how should I go about figuring out why the network device has lost the DHCP info and didn't query the DHCP server for a new lease (unless it did and failed for some reason)?

Update: I was going through some steps trying to diagnose what's been going on, I started off from this guide. When I got down to dhclient and ran sudo dhclient the machine reconnected to the network.

Pastie of diagnostics while I was disconnected. Did I miss anything?

Update 2: I think I found the culprit in /var/log/syslog.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Withdrawing address record for 192.168.1.200 on enp4s0.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.1.200.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Interface enp4s0.IPv4 no longer relevant for mDNS.

networking ubuntu

share|improve this question

edited Jun 11 '16 at 16:55

leetwanker

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

bumped to the homepage by Community♦ 6 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Check cables to make sure they are not bad? Check if energy savings options are off to prevent network card sleep?
  
  – Peter
  Jun 10 '16 at 5:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is probably un-constructive, but if all you are using it for it a file-server, why do you need a GUI? Why not ubuntu-server? Although, I am not sure if this would fix your specific issue, I would first look into the Network-Manage service and Setting to see if there is a configuration issue. Maybe it is stopping? Or Maybe if you go to Edit Connections and select the Wired Connect 1 Unless you renamed it (Mine is called "Auto Wired") and under general make sure Auto Connect when network is available.
  
  – asmith
  Mar 2 '17 at 7:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It could also be that on top of what Peter said, if you have a cable issues, router/switch issue where port disconnects or get powered down, or power saver is on and those with the Auto Connect not selected would cause this to happen every time there is a temp loss of network connection, even milliseconds.
  
  – asmith
  Mar 2 '17 at 7:44
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Does this article help? hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues
  
  – Jeremy J Wong
  Jun 1 '17 at 23:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Or ubuntugeek.com/…
  
  – Jeremy J Wong
  Jun 1 '17 at 23:56
  

  
  
  
  

 | 
show 7 more comments

I've recently put Ubuntu MATE 16.04 on a computer, which I'm using as a file server, among other things. Twice in the past few days it's lost connection to the LAN. I was in a hurry to get it back up, so I unplugged the connection and replugged. It pulled an IP address again and reconnected to the network.

Now I'm starting to think it probably wasn't just an isolated incident and I'm going to have to figure out why it's losing its connection.

The first time it happened I noticed the network didn't have IP/DNS etc, but I didn't dig any further than that.

The next time this happens, how should I go about figuring out why the network device has lost the DHCP info and didn't query the DHCP server for a new lease (unless it did and failed for some reason)?

Update: I was going through some steps trying to diagnose what's been going on, I started off from this guide. When I got down to dhclient and ran sudo dhclient the machine reconnected to the network.

Pastie of diagnostics while I was disconnected. Did I miss anything?

Update 2: I think I found the culprit in /var/log/syslog.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Withdrawing address record for 192.168.1.200 on enp4s0.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.1.200.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Interface enp4s0.IPv4 no longer relevant for mDNS.

networking ubuntu

share|improve this question

edited Jun 11 '16 at 16:55

leetwanker

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

Jun 11 10:40:19 nvidia avahi-daemon[886]: Withdrawing address record for 192.168.1.200 on enp4s0.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.1.200.

Jun 11 10:40:19 nvidia avahi-daemon[886]: Interface enp4s0.IPv4 no longer relevant for mDNS.

share|improve this question

edited Jun 11 '16 at 16:55

leetwanker

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

share|improve this question

edited Jun 11 '16 at 16:55

leetwanker

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

asked Jun 9 '16 at 18:22

leetwankerleetwanker

4952520

2 Answers
2

active

oldest

votes

0

This is most likely an issue with avahi daemon and more than likely with .local domain.

Follow those steps in that order, one at the time:

• change your domain from .local to FQDN


• disable avahi from seeing this interface.


• disable IPv6 if you don't use it


• disable/remove avahi daemon if you don't need it ( I would start with this as you probably have no need for avahi anyway)

share|improve this answer

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  can you explain a little further why avahi could be the root? @Chris
  
  – Gewure
  Mar 2 '18 at 3:58
  

  
  
  
  

add a comment | 

0

You don't say how often you lose the connect, but if you're using DHCP instead of a fixed IP, my first guess is that you are encountering the DHCP Lease Time set in your router.

Set your router DHCP range to leave out a chunk of adresses, then set your server to a fixed IP within the chunk not subject to DHCP.

share|improve this answer

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1087359%2foccasionally-losing-wired-lan-connection-on-ubuntu-16-04%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

This is most likely an issue with avahi daemon and more than likely with .local domain.

Follow those steps in that order, one at the time:

• change your domain from .local to FQDN


• disable avahi from seeing this interface.


• disable IPv6 if you don't use it


• disable/remove avahi daemon if you don't need it ( I would start with this as you probably have no need for avahi anyway)

share|improve this answer

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  can you explain a little further why avahi could be the root? @Chris
  
  – Gewure
  Mar 2 '18 at 3:58
  

  
  
  
  

add a comment | 

0

This is most likely an issue with avahi daemon and more than likely with .local domain.

Follow those steps in that order, one at the time:

• change your domain from .local to FQDN


• disable avahi from seeing this interface.


• disable IPv6 if you don't use it


• disable/remove avahi daemon if you don't need it ( I would start with this as you probably have no need for avahi anyway)

share|improve this answer

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  can you explain a little further why avahi could be the root? @Chris
  
  – Gewure
  Mar 2 '18 at 3:58
  

  
  
  
  

add a comment | 

This is most likely an issue with avahi daemon and more than likely with .local domain.

Follow those steps in that order, one at the time:

• change your domain from .local to FQDN


• disable avahi from seeing this interface.


• disable IPv6 if you don't use it


• disable/remove avahi daemon if you don't need it ( I would start with this as you probably have no need for avahi anyway)

share|improve this answer

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

share|improve this answer

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

answered Sep 13 '17 at 10:09

ChrisChris

1,651714

0

You don't say how often you lose the connect, but if you're using DHCP instead of a fixed IP, my first guess is that you are encountering the DHCP Lease Time set in your router.

Set your router DHCP range to leave out a chunk of adresses, then set your server to a fixed IP within the chunk not subject to DHCP.

share|improve this answer

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

add a comment | 

0

You don't say how often you lose the connect, but if you're using DHCP instead of a fixed IP, my first guess is that you are encountering the DHCP Lease Time set in your router.

Set your router DHCP range to leave out a chunk of adresses, then set your server to a fixed IP within the chunk not subject to DHCP.

share|improve this answer

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

add a comment | 

You don't say how often you lose the connect, but if you're using DHCP instead of a fixed IP, my first guess is that you are encountering the DHCP Lease Time set in your router.

Set your router DHCP range to leave out a chunk of adresses, then set your server to a fixed IP within the chunk not subject to DHCP.

share|improve this answer

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

share|improve this answer

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

answered Aug 13 '18 at 21:13

user10216038user10216038

1066

answered Aug 13 '18 at 21:13

user10216038user10216038

1066