SOLVED: F14 Headless Amahi Server-Not Connecting To Network

[frechetn]

I know, rather old setup. A few weeks ago, the power to the house went out. When it returned, the Amahi server would not dole out DHCP addresses nor could I connect to the sever through the network with a static address. The server appears to be booting up to the CL prompt. I am able to logon as root. I just can't seem to get the server back on-line.

Using the Amahi Network Troubleshooter I typed in the cmd's and copied the cmd results into pastebin file. The results are available at on pastebin
I tried to post the link on the IRC channel but there doesn't appear to be anyone available to help.

Thinking that the network card got damaged, I replaced it with a another identical card (3C905B). But that didn't appear to help either.
I checked /etc/udev/rules.d/70-persistent-net.rules to make sure that the new card was eth0.

Any help would be appreciated.

[bigfoot65]

Can you ping from the HDA? Did you cycle your network connections? What I mean is power up modem, router, then HDA before turning on any clients?

[frechetn]

No, unable to ping to or from HDA. I know the network is working since the router is now handling DHCP addresses.

Using Super_WinPE, I am able to ping resources on the network and on the internet. So the NIC is good!

[bigfoot65]

Ok. My point behind the comment about cycling the network is sometimes that is required to get the HDA a DHCP lease before turning off the feature on the router.

Recommend you recycle, having only the modem, router, and HDA powered on. All other devices must be off to test.

If the HDA does not get a DHCP lease, then that is the sole problem. It could be something got corrupted with the power outage. If that is the case, you may have to rebuild the HDA from scratch.

Hopefully that is not the case, but I have seen it happen.

[frechetn]

Ok, I think I've got it.

Following our chat, I thought I'd better check to see if the network service even started.

Code: Select all

> service network restart Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring. [FAILED]

I did a quick search on-line and found this article. Edited /etc/sysconfig/network-scripts/ifcfg-eth0 file by changing the MAC address to the new NIC card.

Code: Select all

DEVICE="eth0" # HWADDR=00:10:4B:87:B6:44 <-- Remarked this out HWADDR=00:50:DA:93:26:BA <-- Added this IPV6INIT="yes" MTU="1500" IPADDR=192.168.1.10 NETMASK=255.255.255.0 GATEWAY=192.168.1.1 DNS1=192.168.1.10 DNS2=192.168.1.10 SEARCH=home DOMAIN=home BOOTPROTO=none NM_CONTROLLED=no ONBOOT=yes # generated by hdactl on 2014-08-10 10:40:34 /1

Tried it again and voila!!!

Code: Select all

> service network restart Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ]

I'm now able to ping the server from other pc's.
Thanks for your assistance bigfoot65!

[bigfoot65]

Awesome! Glad to here it's resolved.