My HDA domain goes to the actual domain outside my network

[bigfoot65]

You may need to refresh your network. Amahi has nothing to do with accessing your router settings.

In the past, I have shut down everything. Then started with turning on modem, router, and HDA. Once it was booted, verified connectivity then turned on clients.

[diggityDawg]

If the HDA is providing the DHCP and DNS for the entire network, then it does have something to do with accessing any device that it provides an IP to, doesn't it? Maybe I'm missing something...? Another weird thing is that when I try to ping machines on the network from my main Windows machine I get timeouts. The only device I can ping on the network is the HDA. I can see drives on those machines, and browse them through Windows explorer, but I can't ping them...

I will try restarting everything - it's not easy restarting the Amahi machine because it's a headless server, and half the time it doesn't start up and I have to attach my monitor to see what's going on. So for that reason I HATE having to restart it... Anyways, will let you know what happens.

[bigfoot65]

The router IP is typically reserved below 100. Amazing only provides DHCP leases fromm 100 and greater.

Sorry things are such a pain. Seems like DNS is not working correctly. A restart should fix that providing your router is pointed to the HDA for DHCP and DNS.

[ Post made via Android ]

[diggityDawg]

I tried what you suggested - I shut down the HDA, the modem and the router. I then restarted the modem, then router, then HDA. Still can't access the router settings, can't ping anything in the network, but I can browse the Dashboard and apps installed on the HDA, I can ping the HDA, I can access drives on other machines... Any other ideas?

[bigfoot65]

Try the network troubleshooter in the wiki.
http://wiki.amahi.org

[ Post made via Android ]