Can't access username.yourhda.com

[bigfoot65]

Hard to say, but might want to check the clients to see what they show for DNS. If it's not the HDA, that may be part of your issue.

[wiredwrx]

Is that a computer wide setting, or a browser setting. As for what it should be, should it be the HDA's internal IP address, or something else. I find it wierd to be a client computer specific issue, since all the clients have the issues, but I will check.

[bigfoot65]

All clients need to have a DHCP and DNS address from the HDA. If they don't things won't work correctly.

You can check out the wiki network troubleshooting area if you need more info.

[wiredwrx]

So, I checked every client, and they are all set to obtain IP and DNS automatically, I assume through DHCP, though there is no where to specify from where to obtain the DNS and IP.

I also thought that it might be that I am suing two APs, one for wireless and one for wired, so I powered down the wireless AP/Router, and rebooted the wired router, and the HDA and all clients. However, still, when I type in username.yourhda.com I get the wired router log in screen.

Ran the Network Troubleshooter, and everything is as it should be.

[bigfoot65]

What are the client's using for OS? You need to verify the actual addresses for DHCP and DNS. If they are not the HDA's, then there is a problem.

[wiredwrx]

Mix of XP, Windows 7, IOS, and Android.

Should I be designating the DHCP and DNS servers? Or, is setting them to automatic enough? And then what happens when I take a laptop and travel?

[bigfoot65]

Leaving them as automatic is fine. You need to do

Code: Select all

ipconfig /all

at the command prompt and ensure it reflects DHCP, DNS, and domain suffix as the HDA.

[wiredwrx]

One returned the following, while the other returned an error that I am currently researching.

REDACTED

[bigfoot65]

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.

[wiredwrx]

Looks like my error is a common one. Once I am home, I will re-run ipconfig once I can make a hard connection to the router.

http://forum.thinkpads.com/viewtopic.php?t=38709