Cannot access my hda from windows

[McCabe]

I had my amahi server up and running and working fine. Then I lost power the other day, and when it came back, and rebooted my server I could no longer find my hda through windows explorer. My wife's macbook cannot access the server either.

I can still log on to my dashboard and can see that my server is in fact up and running... but I cannot access my files. I am pretty new to linux and servers in general so I am lost as to what to do.

[bigfoot65]

Recommend you check out the Network Troubleshooter.

[imgermany]

Hi there,

same problem for me: HDA is up and running, i can install aps but i cant connect to the shares (tries all combinations of password/User i found in the forum).

Maybe my problems have to do with my installation procedure: I installed in one pc and then moved the hdd in my headless "Hewlett Packard Storage Works Data Vault x510" -> http://www.smallnetbuilder.com/nas/nas- ... 0-reviewed.
But because i can log in and see all the shares i thik its ok...?

Bit I guess my problems have something to do wih my network setup an dhcp/dns settings. I have to say i dont have clue what the correct settings are because i dont want the hda to run all the time so disabling dhcp on my router is not a good idea. But it seems to (me because hda says so) that my WLAN Devices got there DHCP Leases from the HDA? How can i prevent this i think i schould only have one dhcp Server in my network?
And what me really confuses is the "home domain". I left that at the default settings but have no idea if that is ok for my network. All i know is that i already have a "domain" that is called "fritz.box" and a workgroup named "workgroup".

The Amahi congratulation mail said this

Home Domain: amahi.net
Static IP: 192.168.1.2 -> my hdas' ip
Netmask: 255.255.255.0
Gateway: 192.168.1.1 -> my routers' (fritzbox) ip

So i ended up using the online troubleshooter. This one looks pretty good, but i got stuck here because the command traceroute was not found (german error message: "Kommando nicht gefunden"). So i gues my HDA has no traceroute on it. What can i do now to find the problem oder better: a solution?

This is where i got stuck:

Troubleshooting for Step 5 - Router is reachable?
If you have multiple network adapters on your server (maybe an onboard, and a PCI), make sure the cable is plugged in the correct adapter. If you're using Amahi, it needs to be plugged in the adapter identified as eth0. Trying to plug the cable in the other adapter, then retrying the last test, wouldn't hurt!


If the above doesn't help, execute the following commands on the HDA itself, using either SSH, or a Terminal:

netstat -nr

arp -a

traceroute -q 1 -m 5 router
Copy the text generated by the commands into a new paste at pastebin.ubuntu.com.
After submitting your paste, copy the generated url (from the url bar).
Head over to the Amahi IRC channel, and share your link with one of the helpful folks there.
Good Luck! Thanks for choosing Amahi.

Progress
Step 1: Your HDA IP address is 192.168.1.2

Step 2: Your HDA domain name is amahi.net

Step 3: Your router IP address is 192.168.1.2

Step 4: Your HDA DNS server is working fine for local hostnames

Step 5: Your router is NOT accessible from your HDA server.

Any ideas?

[bigfoot65]

Recommend you check out the Network troubleshooting page in the wiki.

Also for the connecting to the shares, see Storage and file sharing article. The user name and password is the one you set during install.

[imgermany]

Thank you for your answer.

I tried The troubleshooting wiki Step 1:
Only the number 5 didnt work, The hda is not reachable via name...but it is reachable via IP address.

So what can i do now?

[ Post made via Android ]

[bigfoot65]

Did you disable DHCP and DNS server on your router? Have you Renwed the IP address for your client?

[imgermany]

No i did not. As i wrote i dont want to have The amahi up all the time because of power consumption...
Ist it necessary to disable DHCP and DNS in the router? I read in the FAQ that this is optional?

I now renewed the ip adresses...just to give it a try i told one of my pcs to use the 192.168.1.2 as the DNS Server. the Pc is now in the amahi.net domain.
http://hda ist now reachable via Browser, but i still cannot connect to the shares on the hda. As before i can see them, but after giving username and password its "no permission".

[ Post made via Android ]

[bigfoot65]

Ok, understand. What user name and password are you using for the shares? It should be the same one you log into the HDA with.

If using Windows as a client, you may need to set up the credentials. I believe there is some guidance on the internet for doing this as it's not Amahi specific.

[imgermany]

i tried with the the user i created at the install process and with different other user accounts i created later...just to make sure not to use a user with another name than my windows user...

i tried with username like :

hda.amahi.net\[user]
hda\[user]
amahi.net\[user]
[user]

but Errormessage is always the same :-/

[bigfoot65]

I presume you are using \\hda in Windows.

This Windows credential manager guidance may help.