Page 1 of 1

Not able to access HDA shared files windows 10...

Posted: Sat Jul 08, 2017 12:42 pm
by yoyocint
Regards.

I was able to get my Amahi 10 server up and running, thanks for the help on getting the install code right.

On my prior Amahi servers I had a database file installed on a share and was able to access it from my windows 10 PC's.

Yesterday I created the share directory to store the database files again on the HDA, but, can not see it from my windows 10 PC file manager.

I read some posts and followed the WIKI instructions for the Windows 1-0 Samba issue. Ran the t2 command lines on windows CMD as administrator and the system confirmes that the changes were implemented.

Still, I can not see the HDA HDD or shared folders.

Now what?

Re: Not able to access HDA shared files windows 10...

Posted: Sat Jul 08, 2017 3:33 pm
by bigfoot65
Can you accessby IP address? For example \\x.x.x.x

Might need to restart your network.

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 4:43 am
by yoyocint
No....

Ill restart all the equipment this morning and see...

thanks

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 10:51 am
by yoyocint
I restarted the HDA and all the network componentes. PC's and access points, to no avail.

What should I try or verify?

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 1:37 pm
by bigfoot65
Is the HDA your DHCP and DNS server for clients?

From the terminal, verify IP address:

Code: Select all

ip address

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 2:03 pm
by yoyocint
I can access the HDA web interphace.

The HDA does not show up on windows file manager, neither comes up on file manager search wither by searching HDA or entering the ip which is 10.0.0.75.

I did deactivate the DHCP server on my DSL modem and the HDA is serving as DHCP server for the network.

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 2:14 pm
by yoyocint
Ran the ip address command on the HDA via SSH. The result...

Did the ip address command from terminal.

This is the result... ( XXXXXXX@hda is substituted for the real user name at the HDA)

[XXXXXXX@hda ~]$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 44:39:c4:53:de:82 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.75/24 brd 10.0.0.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::ed78:ffb8:7f5d:80d0/64 scope link
valid_lft forever preferred_lft forever
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::5e62:a008:6904:1fcd/64 scope link flags 800
valid_lft forever preferred_lft forever
[XXXXXX@hda ~]$

I had also done the network troubleshooting tool and everything came out OK.

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 2:25 pm
by bigfoot65
Do you have IPV6 enabled on your router? If so, you need to turn it off.

#Amahi only works with IPV4.

Not sure if the 10.x.x.x could be causing issues.

Please provide URL for:

Code: Select all

apaste --sysinfo
May have to get our developer to help with your issue.

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 3:40 pm
by yoyocint
https://paste.fedoraproject.org/paste/M ... ~rHa703FqA

Let me know if deemed adequate to involve the developer or other type of support on this.

Again, thanks

Re: Not able to access HDA shared files windows 10...

Posted: Mon Jul 10, 2017 4:01 pm
by bigfoot65
I can see you didn't follow the install instructions precisely. There should not be a /home partition. That's where all your drive space was dedicated.

Do you have more than one NIC on this machine?

Something with your setup is amiss. Did you make any manual changes to the machine?