Can't access files and can't troubleshoot

[Voidhawk]

Bigfoot,


Ok, so I've been messing around with this for a couple weeks since you assisted me with the full dvd install using fedora 19. I think my problems began when I turned off the machine manually by holding the power button as at the time, i didn't know there was a "power off" and "reboot" button in my HDA settings.

The next time I turned and since then, the "status" on the control panel has shown "Stopped". It's still connected to the internet as I can access things via the control panel and the HDA. I can see the server on my network, but I can't access anything. I've been researching the forums to see about solutions and tried a few things, but I'm running into a lot of road blocks.

My first issue is that when I try to access any of my folders it'll prompt for a username/password thing and I can't get in. I've used the trouble shooting to change the host names and things like that and cannot get thru. So I started looking for other workarounds.

The next thing I tried to do was the trouble shooting. I hooked up a monitor to my server and was using the interactive internet version of the trouble shooter. It kept timing out and saying it can't contact other servers?

I also tried to download the install net-tools bind-utils but that failed. It looked for other mirrors and then said no package available and "nothing to do". I took a picture of that screen and what it said in case you'd like to see it. I can also show pictures of any of the other results I'm getting in case that would be helpful.

I'd sincerely appreciate your guidance here. I'm not sure what to do next.

-Voidhawk

[bigfoot65]

Yes using the power button is not the best option. You can shut it down via SSH or using the Dashboard. Not sure if that caused your issues, but could be something to consider.

Appears that your HDA may not have internet connectivity. Based on your feedback, that would be my first thought.

When you shut it down, did you turn the DHCP server function on your router on?

Might help if you can describe how you have your network set up. Router as DHCP and DNS server or not. Are other clients getting DHCP leases when the HDA is off. You get the idea.

[Voidhawk]

Bigfoot,


This is really going to show my ignorance here. I haven't messed with my router at all during the entire server process.

I would say it does have internet access since it was able to locate a few mirror sites when trying to download the utility tool and I'm also able to turn off/reboot the server with the online amahi control panel.

In the beginning, the instructions advised to use an IP address for the server and since I had used it as a PC prior, it already had an IP so I used the same one. I didn't play with any other features regarding the DHCP or leases. I don't recall running into anything of that nature during the install period. Again, being very new to the whole "server" game puts me at a strong disadvantage here and I'm sorry for that.

With that being said, when I pull up my router control panel and look at DHCP, it asks "Enable DHCP Server" and there's a check box which is checked saying "Enabled". All of my other networked devices all have proper expirations so I'd say my leasing is working properly?

Other than that, I have no idea about any of the other DHCP settings. Sadly, my router is also VERY poor in explaining how to do modify most things and my settings. It's the Motorolla SURFboard SBG6782-AC. I'm open to your next suggestions/ideas. I feel I'm pretty decently technologically saavy and have no problem diving into things. Again, I'd be happy to provide screenshots/pics of anything on my screens that may assist you. Just point me in the right direction.

[bigfoot65]

Ok, so that could be your issue. You cannot run 2 DHCP servers on the same network subnet. If you are going to use the HDA, you have to disable it on the router. BTW, this is mentioned in the install instructions I believe it's Step 4.

That is why the HDA worked for a few hours with all the clients. I recommend you run the HDA as your sole DHCP server.

[Voidhawk]

lol! You're absolutely right.

"It's strongly recommended that you turn off the previous DHCP server and let Amahi handle DHCP so that DNS falls into place"

Since I didn't know how important that was I'm sure I just overlooked it. I'll disable the DHCP on the router tomorrow and give the server another whirl and report back to you.

Would this have anything to do with my inability to access my server folders when it asks for username/password?



Thanks again.

[bigfoot65]

No problem.

As for the folder access, it might be the issue. Will have to see.

[Voidhawk]

So I'm home and have turned off the "Enable DHCP Server" option on my router. Nothing changed on the server so I rebooted it (using the HDA// web based button). Since rebooting it, now my HDA// won't pull up at all. It just continually says it's not available...? The Amahi control panel still says "STOPPED" for status.

[bigfoot65]

Did you turn off all devices except the HDA? Might need to reboot the router too.

[Voidhawk]

OK, so finally got more time to play around. Results are not good.

I started by disabling the DHCP on the router. I then turned off every device in the house including router and HDA. Turned router on. Let it fully boot. Turned on HDA. Then turned on laptop. After a few moments, laptop had internet. Checked HDA// and got the "webpage not available". So I thought maybe I need to have the HDA on first. So I shut off the laptop and unplugged the router again while leaving the HDA running. Turned router back on. Booted. Got on web with laptop - same result. Still can't access the HDA. Control panel still says "STOPPED" too. I took a screenshot of my router DHCP settings.

What would you advise I try next? :-/

[bigfoot65]

What I would do is enable the DHCP server on your router. Set it to the Starting local address to match the HDA IP address (BTW it must be less than 100). Then set Max number of network devices equal to one.

Turn off everything, except the modem. Then turn on the router. After a few minutes turn on the HDA. Give it a few minutes. Finally turn on a client and see if the HDA is working and you can connect to the internet.

Remember the HDA IP address is the one you set in the HDA profile on amahi.org.

Also the web browser address for the dashboard is http://hda not HDA//. The HDA has to be on and connected to the internet before any client is powered on.