Ethernet not connecting [SOLVED]
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Ethernet not connecting [SOLVED]
I recently bought a router and linked my PC to it. It was working OK until I needed to run Windows yesterday (on same PC). So, after I done my business on Windows, I restarted back to Mint and it didn't connect to internet. I checked the network with my phone and Windows system - they both connect.
The only clue I have is that when my PC was connected to the network wire directly, sometimes it didn't get IP4 address (while on Mint). But it was easily solvable by toggling connection off and on. Now I don't know what to do. I can not connect my PC to the WAN cable directly anymore, because my ISP has this stupid security check of associating the device MAC address with their database entry or something. My connection is static. I will give you any information you need.
The only clue I have is that when my PC was connected to the network wire directly, sometimes it didn't get IP4 address (while on Mint). But it was easily solvable by toggling connection off and on. Now I don't know what to do. I can not connect my PC to the WAN cable directly anymore, because my ISP has this stupid security check of associating the device MAC address with their database entry or something. My connection is static. I will give you any information you need.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 4 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Ethernet not connecting
It is not clear from the facts given if Linux Mint can connect to the ISP router, just not the Internet? It sounds like you have a direct cable to the ISP router from the Linux Mint box? Did you try bringing up the router admin interface? Most routers have a web administration interface for the router: typically either http://192.168.0.1/ or http://192.168.1.1/ By default the admin interface doesn't work on wireless, just wired.
Re: Ethernet not connecting
My PC is connected to the router via cable.mybrid wrote:It is not clear from the facts given if Linux Mint can connect to the ISP router, just not the Internet? It sounds like you have a direct cable to the ISP router from the Linux Mint box? Did you try bringing up the router admin interface? Most routers have a web administration interface for the router: typically either http://192.168.0.1/ or http://192.168.1.1/ By default the admin interface doesn't work on wireless, just wired.
I can't connect to the web interface, either.
Re: Ethernet not connecting
This is weird, I can successfully connect from a laptop (wired) which has Xubuntu 16.04. And in router's interface I can't see my PC in the DHCP client list, which means that it can't connect to router?
Re: Ethernet not connecting
I ran ipconfig:
The IP4 address is not being assigned.
Code: Select all
enp0s25 Link encap:Ethernet HWaddr d0:50:99:95:40:ec
inet6 addr: fe80::e548:852b:a248:72bb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:680 errors:0 dropped:0 overruns:0 frame:0
TX packets:917 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:158703 (158.7 KB) TX bytes:171198 (171.1 KB)
Interrupt:20 Memory:f7c00000-f7c20000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:13272 errors:0 dropped:0 overruns:0 frame:0
TX packets:13272 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1028395 (1.0 MB) TX bytes:1028395 (1.0 MB)
Re: Ethernet not connecting
Are you using a VPN service. Some people have experienced weird problems like this.
Re: Ethernet not connecting
No.WharfRat wrote:Are you using a VPN service. Some people have experienced weird problems like this.
*Sigh* I'm stuck with Windows again.
Re: Ethernet not connecting
Screw this, no matter what I try, it doesn't connect to router. I spent almost 2 days on this bullshit. I had enough.
Re: Ethernet not connecting [POORLY SOLVED]
I pinned down this issue a little. So, the issue: I boot into Windows 7; then I boot into Mint 18.1 and lose connection to router and internet. The stupid solution: I boot into old Mint 17.3 system on a separate hard drive and it fixes the connection. What's the problem? Is it kernel, firmware, drivers or something else?
- CaptainKirksChair
- Level 4
- Posts: 456
- Joined: Sat Feb 18, 2017 9:29 pm
Re: Ethernet not connecting [POORLY SOLVED]
First, when you boot to Windows and then want to boot into Mint, don't restart. Make sure you take Windows all the way down to a power off. Then restart the computer and boot into Mint. Also, make sure that Windows fast booting is turned off. Fast booting is just a type of hibernation and who knows everything that Windows locks when it hibernates. Try these first.
Second, make sure you have installed Samba in Mint 18. (Open the Software Manager, search for "samba", and install "system-config-samba.") By default, Mint 18 does not have Samba installed. I know I had to install Samba in Mint 18 to access network shares. It shouldn't have anything to do with general networking but if you are going to share data between computers, installing Samba will make it easier.
Third, run the following command at a terminal. If you type, the letter F is a capital.
Post the output back here between code tags. Let's get a look at that networking hardware and drivers.
Second, make sure you have installed Samba in Mint 18. (Open the Software Manager, search for "samba", and install "system-config-samba.") By default, Mint 18 does not have Samba installed. I know I had to install Samba in Mint 18 to access network shares. It shouldn't have anything to do with general networking but if you are going to share data between computers, installing Samba will make it easier.
Third, run the following command at a terminal. If you type, the letter F is a capital.
Code: Select all
inxi -Fxz
Re: Ethernet not connecting []
Bummer - the old system stopped connecting, too. So I can't install anything for now.CaptainKirksChair wrote:First, when you boot to Windows and then want to boot into Mint, don't restart. Make sure you take Windows all the way down to a power off. Then restart the computer and boot into Mint. Also, make sure that Windows fast booting is turned off. Fast booting is just a type of hibernation and who knows everything that Windows locks when it hibernates. Try these first.
Second, make sure you have installed Samba in Mint 18. (Open the Software Manager, search for "samba", and install "system-config-samba.") By default, Mint 18 does not have Samba installed. I know I had to install Samba in Mint 18 to access network shares. It shouldn't have anything to do with general networking but if you are going to share data between computers, installing Samba will make it easier.
Third, run the following command at a terminal. If you type, the letter F is a capital.
Post the output back here between code tags. Let's get a look at that networking hardware and drivers.Code: Select all
inxi -Fxz
My stuff:
Code: Select all
System: Host: Alexiy-PC Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.1 Serena
Machine: Mobo: ASRock model: H97 Pro4
Bios: American Megatrends v: P1.90 date: 07/27/2015
CPU: Dual core Intel Core i3-4350 (-HT-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14367
clock speeds: max: 3600 MHz 1: 3600 MHz 2: 3599 MHz 3: 3600 MHz
4: 3600 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Mesa DRI Intel Haswell Desktop
GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
driver: snd_hda_intel bus-ID: 00:03.0
Card-2 Intel 9 Series Family HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.4.0-53-generic
Network: Card: Intel Ethernet Connection (2) I218-V
driver: e1000e v: 3.3.5.3-NAPI port: f080 bus-ID: 00:19.0
IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1640.3GB (4.0% used)
ID-1: /dev/sda model: WDC_WD6400AAKS size: 640.1GB
ID-2: /dev/sdb model: TOSHIBA_DT01ACA1 size: 1000.2GB
Partition: ID-1: / size: 457G used: 54G (13%) fs: ext4 dev: /dev/sdb6
ID-2: swap-1 size: 8.19GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 38.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 191 Uptime: 1 min Memory: 382.7/15728.9MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35
Re: Ethernet not connecting [SOLVED]
Finally I've found the solution - it is the asnwer at https://askubuntu.com/questions/596062/ ... -after-win.
On MBs with Intel adapters like mine, one has to update the driver and uncheck all things in network adapter's power options (Wake on LAN can be left). This leaves the adapter in clean state, thus Linux can use it properly.
On MBs with Intel adapters like mine, one has to update the driver and uncheck all things in network adapter's power options (Wake on LAN can be left). This leaves the adapter in clean state, thus Linux can use it properly.
- catweazel
- Level 19
- Posts: 9763
- Joined: Fri Oct 12, 2012 9:44 pm
- Location: Australian Antarctic Territory
Re: Ethernet not connecting [SOLVED]
I'm glad you got it sorted. Unfortunately Windwoes does this kind of thing with hardware, leaving it in a dirty state.Alexiy wrote:Finally I've found the solution - it is the asnwer at https://askubuntu.com/questions/596062/ ... -after-win.
On MBs with Intel adapters like mine, one has to update the driver and uncheck all things in network adapter's power options (Wake on LAN can be left). This leaves the adapter in clean state, thus Linux can use it properly.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.