Can't access username.yourhda.com

[wiredwrx]

We really did not need to see the network specifics, just know that you checked them.

Probably not a good idea to share your HDA IP Address with the world. I presume that is the IP address your clients reflect.

Are you using any other dynamic DNS clients like no-ip.org or similar? Mixing them with Amahi could cause the issue you experience.

Nope, no other DDNS clients. Just Amahi.

I thought I edited out the important information, but did not think my internal client ip addresses should be hidden. Thanks.

[bigfoot65]

Understand. I personally don't expose any IP addresses to be safe. I am unsure what the next step is for this problem.

The only thing I can think of is there is something with your router set up that is not letting the dynamic DNS pass through to the network. It is stopping at the router it seems.

[wiredwrx]

Hmmmmm, weird.

What are your thoughts on making the WRT54 the router for Wired and Wireless, which should let the DHCP/DNS pass, and just using the Actiontec from Verizon to serve internet to the WRT54?

[bigfoot65]

Sounds like a good idea. Definitely worth a shot.

[wiredwrx]

Going to try and put the actiontec into Bridge mode, and see what happens with the WRT54G.

[wiredwrx]

Sooo, could not do the Bridge mode.

The problem persists. I can reach hda and owncloud from any browser inside my network, and I can reach username.yourhda.com from outside my network, but if I enter username.yourhda.com when inside my network, I end up at my router log in screen.

Should I change something somewhere? Should I delete my HDA and start over?

[bigfoot65]

I had that same problem once. Can't remember what I did. Did you try restarting your network?

Not sure there is anything wrong with the HDA install. It may be something else with the router setup.

[wiredwrx]

I have shut everythinng down, including routers. And then turned on routers, started HDA, and started clients. That did not resolve the issues. While I am willing believe it is a problem in the routers, I have turned off DHCP and DNS in both routers, but that does not seem to have alleviated the issues. What about trying an external DNS, and how would that work. What about DynDNS or something?

[bigfoot65]

Don't think that will make a difference. It's really not a big deal if that does not resolve internally as it's intended to be used externally. Why would you want to access apps internally using it?

Did you check the client settings to see that it's getting DHCP and DNS from the HDA and no where else?

It also may work itself out as well. Seems like I had the issue for a while, then I either fixed it or it disappeared. Wished I could remember more.

[wiredwrx]

I wonder if that is affecting my ability to map owncloud using webdav as a drive. I have tried on XP and Linux without success (though one internal client with Win7 was able to map owncloud to a drive) and I think I am having issues because it can't resolve the username.yourhda.com server address. I am willing to map it to two drives, one for internal, and one for external use (when traveling).