Can't connect to network, network troubleshooting

greg5 · 2014-10-29 20:21:41

I updated last Monday and since then I've not been able to connect to my network/internet, I normally use netctl to load a static ip address, but I can't connect to anything right now and all of my troubleshooting has been a bust. Let me know any info you need, as I'm not really sure where to start.

tomk · 2014-10-29 22:46:21

Wired or wireless? Also, define "all of my troubleshooting" i.e. what you tried, what you expected, and what actually happened.

Trilby · 2014-10-29 22:49:38

greg5 wrote:

Let me know any info you need, as I'm not really sure where to start.

Well start somewhere. You've given us absolutely nothing to go on here. What did you update last monday? What troubleshooting have you tried? What kind of network is it? What kind of NIC do you have? What's the airspeed velocity of an unladen swallow?

greg5 · 2014-10-30 01:41:08

I've tried disabling netctl and manually assigning an ip address with no luck, I have an Intel® I217V nic, standard home network, router and modem.

Packages I updated:

[2014-10-20 12:47] [PACMAN] upgraded glib2 (2.40.0-2 -> 2.42.0-1)
[2014-10-20 12:47] [PACMAN] upgraded at-spi2-core (2.12.0-1 -> 2.14.0-1)
[2014-10-20 12:47] [PACMAN] upgraded atk (2.12.0-1 -> 2.14.0-1)
[2014-10-20 12:47] [PACMAN] upgraded at-spi2-atk (2.12.1-1 -> 2.14.1-1)
[2014-10-20 12:47] [PACMAN] upgraded cairo (1.12.16-3 -> 1.14.0-1)
[2014-10-20 12:47] [PACMAN] upgraded dbus-glib (0.102-1 -> 0.102-2)
[2014-10-20 12:47] [PACMAN] upgraded dconf (0.20.0-1 -> 0.22.0-1)
[2014-10-20 12:47] [PACMAN] upgraded dhcpcd (6.5.0-1 -> 6.5.1-1)
[2014-10-20 12:47] [PACMAN] upgraded p11-kit (0.20.7-3 -> 0.22.1-1)
[2014-10-20 12:47] [PACMAN] upgraded gnutls (3.3.8-2 -> 3.3.9-1)
[2014-10-20 12:47] [PACMAN] upgraded v4l-utils (1.2.1-1 -> 1.6.0-1)
[2014-10-20 12:47] [PACMAN] upgraded ffmpeg (1:2.4.2-1 -> 1:2.4.2-2)
[2014-10-20 12:47] [PACMAN] upgraded file (5.19-1 -> 5.20-1)
[2014-10-20 12:47] [PACMAN] upgraded xdg-utils (1.1.0.git20140630-1 -> 1.1.0.git20141009-1)
[2014-10-20 12:47] [PACMAN] upgraded sqlite (3.8.6-1 -> 3.8.7-1)
[2014-10-20 12:47] [PACMAN] upgraded filezilla (3.9.0.5-1 -> 3.9.0.5-2)
[2014-10-20 12:47] [PACMAN] upgraded pango (1.36.6-1 -> 1.36.8-1)
[2014-10-20 12:47] [PACMAN] upgraded gdk-pixbuf2 (2.30.8-1 -> 2.31.1-1)
[2014-10-20 12:47] [PACMAN] upgraded gtk-update-icon-cache (2.24.24-1 -> 2.24.25-1)
[2014-10-20 12:47] [PACMAN] upgraded gtk2 (2.24.24-1 -> 2.24.25-1)
[2014-10-20 12:47] [PACMAN] upgraded firefox (32.0.3-1 -> 33.0-1)
[2014-10-20 12:47] [PACMAN] upgraded libspiro (1:0.2-1 -> 1:0.2-2)
[2014-10-20 12:47] [PACMAN] upgraded zeromq (4.0.4-4 -> 4.0.5-1)
[2014-10-20 12:47] [PACMAN] upgraded fontforge (20140101-3 -> 20141014-1)
[2014-10-20 12:47] [PACMAN] upgraded gobject-introspection (1.40.0-1 -> 1.42.0-1)
[2014-10-20 12:47] [PACMAN] upgraded gjs (1.40.1-1 -> 1.42.0-1)
[2014-10-20 12:47] [PACMAN] upgraded gsettings-desktop-schemas (3.12.2-1 -> 3.14.1-1)
[2014-10-20 12:47] [PACMAN] upgraded glib-networking (2.40.1-1 -> 2.42.0-1)
[2014-10-20 12:47] [PACMAN] upgraded libsigc++ (2.3.1-2 -> 2.4.0-1)
[2014-10-20 12:47] [PACMAN] upgraded glibmm (2.40.0-1 -> 2.42.0-1)
[2014-10-20 12:47] [PACMAN] installed adwaita-icon-theme (3.14.0-1)
[2014-10-20 12:47] [PACMAN] upgraded gtk3 (3.12.2-1 -> 3.14.3-2)
[2014-10-20 12:47] [PACMAN] upgraded gnome-sound-recorder (3.12.2-1 -> 3.14.0.1-1)
[2014-10-20 12:47] [PACMAN] upgraded gtkmm3 (3.12.0-1 -> 3.14.0-1)
[2014-10-20 12:47] [PACMAN] upgraded libsoup (2.46.0-1 -> 2.48.0-1)
[2014-10-20 12:47] [PACMAN] upgraded gvfs (1.20.2-1 -> 1.22.1-2)
[2014-10-20 12:47] [PACMAN] upgraded gvfs-afc (1.20.2-1 -> 1.22.1-2)
[2014-10-20 12:47] [PACMAN] upgraded jre7-openjdk-headless (7.u65_2.5.2-3 -> 7.u71_2.5.3-1)
[2014-10-20 12:47] [PACMAN] upgraded jre7-openjdk (7.u65_2.5.2-3 -> 7.u71_2.5.3-1)
[2014-10-20 12:47] [PACMAN] upgraded jdk7-openjdk (7.u65_2.5.2-3 -> 7.u71_2.5.3-1)
[2014-10-20 12:47] [PACMAN] upgraded phonon-qt4 (4.8.0-1 -> 4.8.1-1)
[2014-10-20 12:47] [PACMAN] upgraded kdelibs (4.14.1-2 -> 4.14.2-1)
[2014-10-20 12:47] [PACMAN] upgraded oxygen-icons (4.14.1-1 -> 4.14.2-1)
[2014-10-20 12:47] [PACMAN] upgraded kdebase-runtime (4.14.1-4 -> 4.14.2-1)
[2014-10-20 12:47] [PACMAN] upgraded libical (1.0-3 -> 1.0.1-1)
[2014-10-20 12:47] [PACMAN] upgraded kdepimlibs (4.14.1-1 -> 4.14.2-1)
[2014-10-20 12:47] [PACMAN] upgraded less (468-1 -> 470-1)
[2014-10-20 12:47] [PACMAN] upgraded libev (4.15-2 -> 4.19-1)
[2014-10-20 12:47] [PACMAN] upgraded libfm-extra (1.2.2.1-3 -> 1.2.3-1)
[2014-10-20 12:47] [PACMAN] upgraded libfm (1.2.2.1-3 -> 1.2.3-1)
[2014-10-20 12:47] [PACMAN] upgraded libgee (0.14.0-1 -> 0.16.0-1)
[2014-10-20 12:47] [PACMAN] upgraded libgnome-keyring (3.12.0-1 -> 3.12.0-2)
[2014-10-20 12:47] [PACMAN] upgraded libraw (0.16.0-1 -> 0.16.0-2)
[2014-10-20 12:47] [PACMAN] upgraded librsvg (1:2.40.2-1 -> 1:2.40.5-1)
[2014-10-20 12:47] [PACMAN] upgraded openssl (1.0.1.i-1 -> 1.0.1.j-1)
[2014-10-20 12:47] [PACMAN] upgraded openssh (6.6p1-2 -> 6.7p1-1)
[2014-10-20 12:47] [PACMAN] upgraded pcmanfm (1.2.2-3 -> 1.2.3-1)
[2014-10-20 12:47] [PACMAN] upgraded phonon-qt5 (4.8.0-1 -> 4.8.1-1)
[2014-10-20 12:47] [PACMAN] upgraded rest (0.7.91-1 -> 0.7.92-1)
[2014-10-20 12:47] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2014-10-20 12:47] [PACMAN] upgraded virtualbox-host-modules (4.3.18-1 -> 4.3.18-3)
[2014-10-20 12:47] [PACMAN] upgraded vte-common (0.36.3-1 -> 0.38.1-1)
[2014-10-20 12:47] [PACMAN] upgraded webkitgtk (2.4.5-1 -> 2.4.6-2)
[2014-10-20 12:47] [PACMAN] upgraded xcb-util (0.3.9-2 -> 0.4.0-1)
[2014-10-20 12:47] [PACMAN] upgraded xcb-util-image (0.3.9-2 -> 0.4.0-1)
[2014-10-20 12:47] [PACMAN] Running '/usr/bin/pacman -U /home/greg/aurget/aurget-4.3.3-1-any.pkg.tar.xz'
[2014-10-20 12:47] [PACMAN] upgraded aurget (4.3.2-1 -> 4.3.3-1)
[2014-10-20 12:49] [PACMAN] Running '/usr/bin/pacman -U /home/greg/google-chrome/google-chrome-38.0.2125.104-1-x86_64.pkg.tar.xz'
[2014-10-20 12:50] [ALPM-SCRIPTLET] [m(B[1m[38;5;4m==>[m(B[1m Updating desktop MIME database...[m(B
[2014-10-20 12:50] [ALPM-SCRIPTLET] [m(B[1m[38;5;4m==>[m(B[1m Updating icon cache..[m(B
[2014-10-20 12:50] [ALPM-SCRIPTLET] [m(B[1m[38;5;4m==>[m(B[1m[38;5;3m NOTE:[m(B[1m The binary is called: 'google-chrome-stable'[m(B
[2014-10-20 12:50] [PACMAN] upgraded google-chrome (38.0.2125.101-1 -> 38.0.2125.104-1)

Last edited by greg5 (2014-10-30 01:52:11)

ewaller · 2014-10-30 02:03:52

Well, since you refuse to tell us, I guess it is up to us to research your hardware to find out if it is wired or wireless. It looks like it is a wired Ethernet.

So, what is the output of ip addr ?

Trilby · 2014-10-30 02:06:46

What does "with no luck" mean? What were the actual results? What error messages did you get?

greg5 · 2014-10-30 03:05:55

ewaller wrote:

Well, since you refuse to tell us, I guess it is up to us to research your hardware to find out if it is wired or wireless. It looks like it is a wired Ethernet.
So, what is the output of ip addr ?

Sorry, yes it is wired.

ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    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: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether
    inet 192.168.5.17/24 brd 192.168.5.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::e23f:49ff:fe0f:90b2/64 scope link 
       valid_lft forever preferred_lft forever

trilby wrote:

What does "with no luck" mean? What were the actual results? What error messages did you get?

I don't remember any error messages, first I stoped my netctl profile, then I followed this wiki page: https://wiki.archlinux.org/index.php/Ne … assignment. it changed my ip address, but I still couldn't access/ping my router.

jasonwryan · 2014-10-30 03:09:09

Work through the wireless page to connect manually: it will then be apparent what, if anything, is failing.

Moving to NC...

ewaller · 2014-10-30 03:40:21

Okay, I can see that your interface has a carrier, and is using an an IPv4 address of 192.168.5.17. The mask is /24. That is a valid address, but it is a little unusual for a home network.

Most home networks have subnets in 192.168.0.0/24. or 192.168.1.0/24.
(1)Do you have any other computers on the network that are functional? (2)What are their IP addresses?

If your network is on 192.168.5.17, then the router should probably be at 192.168.5.1.
(3)What happens if you ping 192.168.5.1 ?
(4)What is the output of ip route ?
(5)If you can ping 192.168.5.1, can you ping 8.8.8.8 ?
(6) What happens if you run dig archlinux.org

Edit: As an aside, when you start a thread looking for help, consider your reader. Not all Arch systems are created equal. It runs on a wide variety of hardware, can be configured as a server or desktop using a myriad of environments. Sometimes it is easy to become myopic about your system because it is highly familiar to you, but realize that we have no idea about your hardware or the details of your installation. When you have some time, you might want to look through the link in my signature. Anyway, I did get a bit sarcastic; I know better than to do that.

Last edited by ewaller (2014-10-30 03:47:18)

greg5 · 2014-10-30 04:16:11

ewaller wrote:

Okay, I can see that your interface has a carrier, and is using an an IPv4 address of 192.168.5.17. The mask is /24. That is a valid address, but it is a little unusual for a home network.
Most home networks have subnets in 192.168.0.0/24. or 192.168.1.0/24.
(1)Do you have any other computers on the network that are functional? (2)What are their IP addresses?

The same machine also runs win8 using the same nic and it's ip address is 192.168.5.121 and it is functioning properly.

If your network is on 192.168.5.17, then the router should probably be at 192.168.5.1.
(3)What happens if you ping 192.168.5.1 ?

PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
From 192.168.5.17 icmp_seq=1 Destination Host Unreachable

--- 192.168.5.1 ping statistics ---
12 packets transmitted, 0 received, +9 errors, 100% packet loss, time 11016ms
pipe 4

(4)What is the output of ip route ?

default via 192.168.5.1 dev eno1 
192.168.5.0/24 dev eno1  proto kernel  scope link  src 192.168.5.17

(6) What happens if you run dig archlinux.org

; <<>> DiG 9.9.2-P2 <<>> archlinux.org
;; global options: +cmd
;; connection timed out; no servers could be reached

So I can connect via wifi, and that works, here is the ip addr:

 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    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: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 
    inet 192.168.5.106/24 brd 192.168.5.255 scope global wlp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::260a:64ff:fe50:5fab/64 scope link 
       valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether

Edit: ip route for wifi:

default via 192.168.5.1 dev wlp3s0  metric 302 
192.168.5.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.5.106  metric 302

Last edited by greg5 (2014-10-30 04:28:49)

ewaller · 2014-10-30 04:36:55

Well, that's weird. I know you said Windows 8 works, but I'll check anyway -- the link lights are lit at both ends of the cable (computer and router) when the network is (presumably) up, but not working? Have you tried disabling IPv6?

greg5 · 2014-10-30 16:32:25

ewaller wrote:

Well, that's weird. I know you said Windows 8 works, but I'll check anyway -- the link lights are lit at both ends of the cable (computer and router) when the network is (presumably) up, but not working? Have you tried disabling IPv6?

I checked and the link lights are lit on the switch and the nic. I also disabled ipv6 and had the same results.

branch · 2014-10-30 17:27:35

Could you please verify that your router is actually on 192.168.5.1 and responds to pings at that address? Maybe you could try to ping 192.168.5.1 from your working windows installation?

greg5 · 2014-10-31 01:24:42

branch wrote:

Could you please verify that your router is actually on 192.168.5.1 and responds to pings at that address? Maybe you could try to ping 192.168.5.1 from your working windows installation?

I can ping my router with my windows box and my router address is 192.168.5.1 the default gateway in win8.

branch · 2014-10-31 14:34:29

I would like to see a packet dump. Could you try the following?

1) install tcpdump
2) in one terminal, run

sudo tcpdump -c8 -e -n -i eno1 arp

3) in a second terminal, run

sudo arping 192.168.5.1

4) control-c arping after tcpdump completes, or after a couple minutes if tcpdump does not complete
5) post the output of both commands

Also, it may be helpful to know just what hardware we are dealing with. Could you install lshw and post output of

sudo lshw -class network

Also, I would like to see packet statistics. Could you post the output of

ip -s address show eno1

greg5 · 2014-10-31 16:21:08

sudo tcpdump -c8 -e -n -i eno1 arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes
12:14:37.295516 e8:94:f6:bb:a1:49 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.106 tell 192.168.5.1, length 46
12:14:37.356978 2c:44:01:ca:30:b9 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.1 tell 192.168.5.114, length 46
12:14:37.789073 e0:3f:49:0f:90:b2 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.5.1 (ff:ff:ff:ff:ff:ff) tell 192.168.5.17, length 28
12:14:38.347511 e8:94:f6:bb:a1:49 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.106 tell 192.168.5.1, length 46
12:14:38.357845 2c:44:01:ca:30:b9 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.1 tell 192.168.5.114, length 46
12:14:38.789101 e0:3f:49:0f:90:b2 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.5.1 (ff:ff:ff:ff:ff:ff) tell 192.168.5.17, length 28
12:14:39.345533 e8:94:f6:bb:a1:49 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.106 tell 192.168.5.1, length 46
12:14:39.357796 2c:44:01:ca:30:b9 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.5.1 tell 192.168.5.114, length 46
8 packets captured
10 packets received by filter
0 packets dropped by kernel

 sudo arping 192.168.5.1
ARPING 192.168.5.1 from 192.168.5.17 eno1
^CSent 15 probes (15 broadcast(s))
Received 0 response(s)

Hardware:

 sudo lshw -class network
  *-network               
       description: Ethernet interface
       product: Ethernet Connection I217-V
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eno1
       version: 05
       serial: e0:3f:49:0f:90:b2
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.13-4 ip=192.168.5.17 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:29 memory:ef300000-ef31ffff memory:ef339000-ef339fff ioport:f040(size=32)
  *-network DISABLED
       description: Wireless interface
       product: AR9462 Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlp3s0
       version: 01
       serial: 24:0a:64:50:5f:ab
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=3.17.1-1-ARCH firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
       resources: irq:17 memory:ef200000-ef27ffff memory:ef280000-ef28ffff

ip -s address show eno1
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 
    inet 192.168.5.17/24 brd 192.168.5.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::e23f:49ff:fe0f:90b2/64 scope link 
       valid_lft forever preferred_lft forever
    RX: bytes  packets  errors  dropped overrun mcast   
    27612      424      0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    91223      1124     0       0       0       0

branch · 2014-10-31 19:03:05

Something appears broken at a very low level. Packets are being received with no drops or errors. You are succesfully receiving arp requests from other hosts on the network. Your arp requests go out but there are no replies.

It could be unrelated, but i find it interesting that none of the requests in the dump are getting replies. Not that we would see the replies to other hosts directly, but all of the requests are retried which indicates there was no reply. For instance It looks like 192.168.5.114 is also not getting arp responses from 192.168.5.1 even though 192.168.5.1 is clearly active on the network because it is issueing arp requests. Is the host at 192.168.5.114 working correctly on the network?

This may be a long shot, but try this and report the result:

sudo ip neighbour add to 192.168.5.1 lladdr e8:94:f6:bb:a1:49 nud permanent dev eno1
ping 192.168.5.1

*edit* fixed interface name in ip command

Last edited by branch (2014-10-31 19:12:48)

greg5 · 2014-10-31 20:57:49

branch wrote:

It could be unrelated, but i find it interesting that none of the requests in the dump are getting replies. Not that we would see the replies to other hosts directly, but all of the requests are retried which indicates there was no reply. For instance It looks like 192.168.5.114 is also not getting arp responses from 192.168.5.1 even though 192.168.5.1 is clearly active on the network because it is issueing arp requests. Is the host at 192.168.5.114 working correctly on the network?

That is interesting, It's my phone and it doesn't work unless the screen is on. I've turned off the wifi on it, but it had no effect.

 sudo ip neighbour add to 192.168.5.1 lladdr e8:94:f6:bb:a1:49 nud permanent dev eno1
RTNETLINK answers: File exists

ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
^C
--- 192.168.5.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9018ms

This is probably unrelated but I found this error in my logs.

Oct 31 16:42:28 red5 ntpd[530]: bind(21) AF_INET6 fe80::e23f:49ff:fe0f:90b2%3%3#123 flags 0x11 failed: Cannot assign requested address
Oct 31 16:42:28 red5 ntpd[530]: unable to create socket on eno1 (5) for fe80::e23f:49ff:fe0f:90b2%3#123

ewaller · 2014-10-31 21:07:33

In looking over the last few posts, I have a thought. When you connect as a Windows box you are at a different address. For the Arch box, you are using a static address. For Windows, you did not say, but it does not really matter. Is there any possibility that another device on your network has been assigned 192.186.5.17 ? If there is, and the router knows its whereabouts, it could be routing everything there. Log into your router from whatever machine you can and see what it knows about IP address, MAC addresses, and where it thinks they all are.

Edit: When was the last time you rebooted your router?

Last edited by ewaller (2014-10-31 21:08:26)

greg5 · 2014-10-31 22:27:17

ewaller wrote:

In looking over the last few posts, I have a thought. When you connect as a Windows box you are at a different address. For the Arch box, you are using a static address. For Windows, you did not say, but it does not really matter. Is there any possibility that another device on your network has been assigned 192.186.5.17 ? If there is, and the router knows its whereabouts, it could be routing everything there. Log into your router from whatever machine you can and see what it knows about IP address, MAC addresses, and where it thinks they all are.

I checked the dhcp client list as well as the active connections and there was no listing of 192.168.5.17. I also changed the ip address a few times with the same results. I've also tried to use dhcpd, but it just timed out. My win8 nic (same as the one we are troubleshooting) is listed in the dhcp client list with 192.168.5.121.

ewaller wrote:

Edit: When was the last time you rebooted your router?

I rebooted the router yesterday.

branch · 2014-11-01 00:50:47

I must admit i am running out of ideas. I don't suppose you can ping 192.168.5.114 can you? Was one of the other static IP addesses you tried 192.168.5.121 by any chance? If not, that may be worth while.

greg5 · 2014-11-06 18:54:21

I just put in a new nic and everything is working as usual. Thanks to everyone, for all your input in helping me diagnose the issue, I really appreciate it.

Arch Linux

#1 2014-10-29 20:21:41

Can't connect to network, network troubleshooting

#2 2014-10-29 22:46:21

Re: Can't connect to network, network troubleshooting

#3 2014-10-29 22:49:38

Re: Can't connect to network, network troubleshooting

#4 2014-10-30 01:41:08

Re: Can't connect to network, network troubleshooting

#5 2014-10-30 02:03:52

Re: Can't connect to network, network troubleshooting

#6 2014-10-30 02:06:46

Re: Can't connect to network, network troubleshooting

#7 2014-10-30 03:05:55

Re: Can't connect to network, network troubleshooting

#8 2014-10-30 03:09:09

Re: Can't connect to network, network troubleshooting

#9 2014-10-30 03:40:21

Re: Can't connect to network, network troubleshooting

#10 2014-10-30 04:16:11

Re: Can't connect to network, network troubleshooting

#11 2014-10-30 04:36:55

Re: Can't connect to network, network troubleshooting

#12 2014-10-30 16:32:25

Re: Can't connect to network, network troubleshooting

#13 2014-10-30 17:27:35

Re: Can't connect to network, network troubleshooting

#14 2014-10-31 01:24:42

Re: Can't connect to network, network troubleshooting

#15 2014-10-31 14:34:29

Re: Can't connect to network, network troubleshooting

#16 2014-10-31 16:21:08

Re: Can't connect to network, network troubleshooting

#17 2014-10-31 19:03:05

Re: Can't connect to network, network troubleshooting

#18 2014-10-31 20:57:49

Re: Can't connect to network, network troubleshooting

#19 2014-10-31 21:07:33

Re: Can't connect to network, network troubleshooting

#20 2014-10-31 22:27:17

Re: Can't connect to network, network troubleshooting

#21 2014-11-01 00:50:47

Re: Can't connect to network, network troubleshooting

#22 2014-11-06 18:54:21

Re: Can't connect to network, network troubleshooting

Board footer