Difference between revisions of "Network troubleshooting"
| Line 22: | Line 22: | ||
If the above does not work, try and fix it by double checking the settings. | If the above does not work, try and fix it by double checking the settings. | ||
| − | After the above works, you should be able to access <pre>http://hda</pre> from the HDA machine's desktop. | + | After the above works, you should be able to access <pre>http://hda</pre> from the HDA machine's desktop. |
| + | |||
== Step 2 == | == Step 2 == | ||
Revision as of 17:28, 17 August 2009
Rule #0: do not turn off DHCP 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.
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.
Tell us what step you get stuck at.
Steps in network troubleshooting:
Step 1
From your hda itself (via ssh or at the desktop in a terminal), can you:
- ping hda (this ensures the dns server is working)
- ping router (this ensures your HDA can see the router)
- ping 68.180.206.184 (this ensures you can see the rest of the world)
- ping yahoo.com (this ensures your dns server can see the world)
If the above does not work, try and fix it by double checking the settings.
After the above works, you should be able to access
http://hda
from the HDA machine's desktop.
Step 2
If the above works, then and only then you may turn off the DHCP server in your router.
IMPORTANT: after turning off the DHCP server, you must repair (or reboot) your clients for them to get the DHCP lease from your Amahi HDA.
Then move to one or more of the clients:
- ping hda (this ensures the client can see the DNS server in your HDA)
- ping router (this ensures the client can see your network gateway)
- ping yahoo.com (this ensures the client can see the world)
if you want to stop by the IRC channel for help, it would speed things up to report where you are "stuck" in that list, like step 1.3, or 2.2.
When all else fails
In some cases, it could be the client OS causing issues.
One known issue is the Vista_Networking_Issue
