Arch Linux

djh712

Member

Registered: 2016-01-21

Posts: 9

[Solved] 192.168.0.100 Refused to Connect

I am trying to connect to Plex, which is installed on my desktop, from a second desktop. My desktop is on ethernet while the other is on wifi. When I try to load http://192.168.0.100:32400/web/ I receive an error:

192.168.0.100 Refused to Connect
ERR_CONNECTION_REFUSED

However, I also have a second hard drive with a new install of Arch on it and I have no trouble loading Plex from the other desktop when I am booted into this hard drive. So, I must have changed something at some point which is now causing Arch to block other devices from connecting to me but I have no idea what. I never configured iptables but other than that I'm not sure what the issue could be.

Any suggestions would be greatly appreciated. I've spent a lot of time search and haven't come across anything particularly useful (I don't think iptables is causing the issue, I'm not trying to SSH, network and hardware seem to be fine since my other install works just fine).

Thanks.

Last edited by djh712 (2017-05-18 19:41:36)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,722

Re: [Solved] 192.168.0.100 Refused to Connect

What are the output of ip addr and of ip route ?
Is the Plex server an Arch Linux box?  Windows?
If Linux, what are the output of ip addr and of ip route on that box?  If Windows, what is the output of ipconfig when run from Powershell?
Are both machines connected to the same router?  Are they on the same subnet?
Can you ping 192.168.0.100 from your client?  Can you ping your client from the Plex server box.
Can you ping the router?  From both machines?
Are you using static or dynamic addresses?

Last edited by ewaller (2017-05-18 14:06:46)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

djh712

Member

Registered: 2016-01-21

Posts: 9

Re: [Solved] 192.168.0.100 Refused to Connect

ip addr

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: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 4c:cc:6a:6d:c4:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet6 fe80::b90f:bf0b:34b7:915/64 scope link 
       valid_lft forever preferred_lft forever

ip route

default via 192.168.0.1 dev enp5s0 src 192.168.0.100 metric 202 
192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.100 metric 202

Yes, I can ping the router from all machines. I am connected to the router via ethernet. The second desktop (Windows) (and my phone [Android] which I also tried to connect on) are connected via wifi, same subnet, IP addresses are dynamic.

I am trying to connect to my Arch Linux machine from the other machine (the ip in general isn't working, so I cannot connect to Plex on :32400 or Apache on :80); Plex lives on the Arch machine. I can ping 192.168.0.100 from the Windows desktop successfully (and the other way around as well).

My best guess is that I installed/configured something at some point (e.g. iptables, except not iptables because I never configured iptables) that is causing the issue but nothing comes to mind.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [Solved] 192.168.0.100 Refused to Connect

Please paste the output of:

systemctl list-unit-files --state=enabled

Moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,722

Re: [Solved] 192.168.0.100 Refused to Connect

...and, try turning off the firewall in Windows (for a short time as an experiment and only if it is behind a firewall on your router)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

djh712

Member

Registered: 2016-01-21

Posts: 9

Re: [Solved] 192.168.0.100 Refused to Connect

Problem solved. I never configured iptables, but it seems that I did at some time configure nftables. Disabling nftables.service fixed the issue so it seems nftables was blocking connections.

Thank you for your help.