[Solved] Unable to ping other devices from server


Recommended Posts

This is a compound issue, but I think the problem of pinging out from the server is at least a clue to the root cause, so I'm using that as the thread title. (For now, anyway.)

 

Some background:

I'm running version 5.0-rc8a.

After trying (and failing) to install SimpleFeatures, I noticed that my other plugins (sabnzbd, sickbeard, headphones etc. (influencer versions)) were not functioning properly. I tried reinstalling them, but this failed too. Rebooting also took ages (I think it was waiting for each plugin-installation to time out). I've removed all the plugins except for dropbox, since this still works (strangely enough), but this doesn't seem to solve the more basic connection issues I'm having.

 

Current status:

  • I can ping the server fine from my other computers.
  • The unRAID Web GUI works fine.
  • The Samba service and shares work fine.
  • The Dropbox plugin works fine and even updates files from the Internet
  • telnet to the server works fine, but the logon prompt takes about a minute to show up
  • DNS name resolution works
  • Ping from the server does not work (not to any devices on the network, including the router)
  • wget does not work (which I guess is why the influencer-plugins are having problems)

 

Contents of network.cfg:

# Generated settings:
USE_DHCP="yes"
IPADDR="10.0.0.42"
NETMASK="255.255.255.0"
GATEWAY="10.0.0.138"
DHCP_KEEPRESOLV="no"
DNS_SERVER1="193.213.112.4"
DNS_SERVER2="130.67.15.198"
DNS_SERVER3=""

 

I know the various IP settings are redundant when USE_DCHP="yes", but that shouldn't matter, should it?

I've attached the syslog in the post here, but the only errors I see there, are related to ACPI.

 

I hope I've provided you with enough clues to help me figure out the root cause, or at least help me find more clues.

syslog.txt

Link to comment

Hi, and thanks for the quick reply. There's probably a time-zone difference, so my answers will be lagging a bit behind.

 

Did you edit network.cfg?

 

Yeah, after browsing through the forum for a mention of similar problems, the one that seemed closest had apparently been solved by reverting to DHCP instead of static IP, so I just went in and did the edit manually before restarting the network.

 

Anyway, tried replacing the network.cfg and rebooting now, and it apparently does not change anything regarding network connectivity.

A fresh syslog is attached to this post.

syslog.txt

Link to comment

Right. Plugins are out, and I've rebooted again.

Still no luck with pinging.

Name resolution fails now too, by the way.

 

root@Tower:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes
root@Tower:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1e:67:23:4b:b3
          inet addr:10.0.0.42  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:241 errors:0 dropped:0 overruns:0 frame:0
          TX packets:258 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20642 (20.1 KiB)  TX bytes:66255 (64.7 KiB)
          Interrupt:16 Memory:b1100000-b1120000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

 

[Edit:] I may be a bit myopic here, but I've gotten hung up on the fact that there's a delay before the telnet prompt comes up. I timed it, and it's exactly 30 seconds. Did a bit of googling on this, and it seems it could be related to DNS resolving not working as it should (the 30 second delay is the timeout from the reverse DNS lookup). I'm just not sure where to start troubleshooting this. Here's the content of /etc/resolv.conf:

# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
domain lan
nameserver 193.213.112.4
nameserver 130.67.15.198
nameserver 10.0.0.138
# /etc/resolv.conf.tail can replace this line

[/edit]

Link to comment

IPADDR="10.0.0.42"

NETMASK="255.255.255.0"

GATEWAY="10.0.0.138" <----

 

While this is technically possible, it is very illogical and someone would have had to go out of their way to set this irregular GW IP.  Probably not the full issue (a bad gateway would still allow for local access to other devices on your subnet), but a symptom of other issues.

 

Do you have an IP config for another machine on that network that is working?

 

Link to comment

IPADDR="10.0.0.42"

NETMASK="255.255.255.0"

GATEWAY="10.0.0.138" <----

 

While this is technically possible, it is very illogical and someone would have had to go out of their way to set this irregular GW IP.  Probably not the full issue (a bad gateway would still allow for local access to other devices on your subnet), but a symptom of other issues.

 

Do you have an IP config for another machine on that network that is working?

 

The static IP address information can now be disregarded.

The server is now up and running with a DHCP supplied IP address.

 

There is - as you said - no technical reason why the gateway should be the lowest or highest address on the subnet, it is merely done by convention. The gateway address has to be specified either way. In this instance, 10.0.0.138 is the default address of a ZyXEL router.

 

That being said, yes I have about 6 other devices on this network that can all communicate fine both with each other and with the Internet.

E.g. the machine I'm sitting at now (Windows 7, btw):

Ethernet adapter eth0:

   Connection-specific DNS Suffix  . : lan
   Link-local IPv6 Address . . . . . : fe80::cc47:6223:41e9:4326%25
   IPv4 Address. . . . . . . . . . . : 10.0.0.111
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.0.138

Link to comment

Did the server work correctly before the Simplefeatures attempt? What does "/sbin/route -n" show?

 

I'm not 100% sure.

It has just been running by itself for quite a while, and since the samba service worked like it should, I didn't think to do a complete check on it before trying out Simplefeatures.

 

This output looks OK to me:

root@Tower:~# /sbin/route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.0.138      0.0.0.0         UG    202    0        0 eth0
10.0.0.0        0.0.0.0         255.255.255.0   U     202    0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

Link to comment

How do you have your DNS entry configured?

 

Is this set to "automatic" (= supplied by DHCP) or a static entry ?

 

An easy way to check if DNS is working is to perform a 'named' ping from the server. For example:

 

  ping www.akamai.com

 

As stated in this post, DNS entries are received from DHCP.

DNS name resolution does not work on the server, even though it works fine for other devices on the same subnet (also using DHCP).

Link to comment

Your resolv.conf file shows your router (10.0.0.138) acting as a DNS proxy. If that intentional ?

 

Normal practise for DNS proxing is to hide the external DNS addresses, but you are doing both...

 

# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
domain lan
nameserver 193.213.112.4
nameserver 130.67.15.198
nameserver 10.0.0.138
# /etc/resolv.conf.tail can replace this line

 

You can set on your unRAID system (for testing) fixed DNS entries. For example use the ones of openDNS.org:

 

208.67.222.222

208.67.220.220

 

Btw Perhaps rebooting your router as suggested by dgaschk may solve your problem...

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.