Amahi Forums

All of a sudden today I'm no longer able to reach the HDA from any computer on my network, or get out to the network from the HDA server itself.

By "no longer able to reach the HDA" I mean none of the following work anymore, where previously they did:

1) Connect to http://hda from a browser
2) Connect to \\hda from windows explorer
3) Connect to 192.168.1.10 with Putty
4) Ping 192.168.1.10

By "get out to the network from the HDA server" I mean none of the following work anymore, where previously they did:

a) Get to the internet from Firefox
b) Ping any computer on my network
c) Ping the router on my network

I have DHCP server in Amahi turned off, and have my router doing that. I rebooted both the Server and the Router several times, with no change. The really confusing one is (c), as the HDA server seems to be getting the proper IP address assigned to it by the router, per the following results from "ifconfig":

[root@Amahi AmahiBean]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:18:32:A7:C5
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:29 Base address:0xe000

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:16436 Metric:1
RX packets:627 errors:0 dropped:0 overruns:0 frame:0
TX packets:627 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:56686 (55.3 KiB) TX bytes:56686 (55.3 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@Amahi AmahiBean]#

One thing to note, is that my router is setup to reserve an IP address of 192.168.1.10 for the HDA Server, which it does based on the server's MAC address. So while my router is handling DHCP for my network, it's "guaranteed" to always assign the correct IP address to the server. I can't find any evidence that the router is misbehaving, in this regard.

I haven't changed anything on the server in days (at least, that I'm aware of), but something must have been altered somewhere.

Any thoughts on where to look?

Thanks much!

Well...false alarm.



Before I reveal the source of the issue, I must confess that I considered deleting this post, but figured my public embarrassment might be a humorously good lesson in checking the obvious before running to the forums for help.

Turns out the cat chewed through the network cable.

Still odd, though, that ifconfig reported an IP address. Would that have been leftover from the last time it had a connection?

I'll now crawl my n00bly humbled self into a corner and lick my pride.

run:
ethtool eth0

OR

mii-tool -v

and look at link= <<<<< which should be yes