Network troubleshooting

Rule #1: Do NOT turn off the DHCP server in your router until your HDA has full network connectivity

Your HDA should be capable of browsing all the major sites and http://www.amahi.org before doing anything else.

If you do not have connectivity, you may want to check that the settings that you programmed in amahi.org for your network and router match that of your actual network and the router in it. Amahi assumes a regular, typical home network and the settings there should be done to match what you have. The most common error is that the gateway is not set up properly. We have a page on how to Find Your Gateway IP.

Please note that only the first NIC/ethernet card (eth0) is supported out of the box. If you have two, please make sure you use eth0 for the LAN where your Amahi HDA resides. There is an unsupported way to support amahi on the eth1 device.

If a wireless network connection is all you have available, you may want to experiment with running Amahi_over_wlan0. This is not a well tested or recommended approach, though, so expect problems of some kind.

Identify the problem

To help you identify a network problem you might have, try using the Interactive Amahi Network Troubleshooter. If it fails along the way, it will give you instructions on how to get additional help, and how to provide us with the information we need to help you understand and fix the problem.

Additional troubleshooting

If ping hda does not work it might be that you have a problem with journalling. Especially if /var/named/data/named.run contains a line like
zone home.com/IN: journal rollforward failed: journal out of sync with zone
you must delete /var/named/*/*jnl and issue the command hdactl-hup
Then retry ping hda to see if things are working.

If the Network Troubleshooter above can't help, you can try the steps in the More network troubleshooting page.

Non Default Network Set-ups

If your router does not have an IP of 192.168.1.1, the following command will make the process easy to allow your HDA to work:

su -

[enter root password]

hda-change-gw [gateway IP]

Example if your default gateway (router) has an IP of 192.168.0.1:

hda-change-gw 192.168.0.1

Note: You will need to restart your server after applying the change.

When all else fails

In some cases, it could be the client OS causing issues.

One known issue is the Vista_Networking_Issue

There are some special instructions if you have an Airport express or an Airport extreme