Windows can't connect to my shares

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Windows can't connect to my shares

Postby gdukin » Sun Apr 28, 2019 6:14 pm

I have been having a more recent issue that I can't access my shares on my network.

In brief, if I go to File Explorer and put in the address of "\\hda" or of "\\hda\SHARENAME," I get an error message indicating "Windows cannot access \\hda." This is reproduced on all 3 computers on my network (2 wireless and one wired connection). All are running Windows 10, most recent updates all installed.

If I run the Windows Network Diagnostics troubleshooter on the connection, the report is "The remote device or resource won't accept the connection," and the detailed report states: "The device or resource (hda) is not set up to accept connections on port "The File and printer sharing (SMB)"."

I am currently running Amahi 10 on Fedora 25. Just updated everything in the server today as well (didn't work before or after the updates).

I can access the dashboard through "http://hda/" as well as my apps web dashboard (Multicraft specifically).

I have run through the interactive network troubleshooter and it found no errors. I also followed the additional steps at: https://wiki.amahi.org/index.php/Networ ... leshooting without success.

I also went through the Shares Troubleshooting portion of the Wiki (https://wiki.amahi.org/index.php/Shares_troubleshooting) also without success.

Per the guidance of the site, the results of my apaste --sysinfo is:

https://da.gd/vBV1

I also posted in the IRC chat, but decided to post here as well as I hadn't received a response after 2 hours. I'll try to leave that open as long as I'm able as well.

Thank you for your help!

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Windows can't connect to my shares

Postby bigfoot65 » Sun Apr 28, 2019 6:44 pm

Your apaste URL does not work. Please redo and post the link it provides.

Also recommend you check out the Shares troubleshooting page in the wiki. Might be a solution there.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Re: Windows can't connect to my shares

Postby gdukin » Sun Apr 28, 2019 6:50 pm

Funny, the apaste link works fine for me. Here's the long version:
https://paste.fedoraproject.org/paste/D ... mD6~B-GUQ/

Also, I already did everything in the "Shares Troubleshooting" page. No love, unfortunately.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Windows can't connect to my shares

Postby bigfoot65 » Sun Apr 28, 2019 7:00 pm

Thanks!

Is your HDA the DHCP and DNS server for your network?

Have you tried rebooting the HDA, then the clients?

Also ensure the clients reflect the correct IP address and DNS server.

Might also try \\IPADDRESS
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Re: Windows can't connect to my shares

Postby gdukin » Sun Apr 28, 2019 7:26 pm

Yes, HDA is the DHCP and DNS.

IP addresses are all correct (and double checked).

Everything has been rebooted a couple of times.

the //ipaddress on client or server?

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Re: Windows can't connect to my shares

Postby gdukin » Sun Apr 28, 2019 8:49 pm

Oh...got the IP address command:

In File Explorer:

If I type: //(local IP address of HDA), it will pop me to my browser and open up the dashboard.
If I type: \\(local IP address of HDA), I get the same cannot connect error.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Windows can't connect to my shares

Postby bigfoot65 » Mon Apr 29, 2019 10:35 am

Check the status of Samba in terminal:

Code: Select all

sudo systemctl status smb
You may need to cycle your network.

Shutdown everything. Then turn on starting with modem, router, and HDA.

Next turn on one client and heck if things are working. Once verified, turn on remaining clients.

I have seen where networks need refreshed occasionally.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Re: Windows can't connect to my shares

Postby gdukin » Tue Apr 30, 2019 7:23 pm

Sorry for the delay, busy day.

So, tried power cycling everything, no success. Still can connect to web dashboard (http://hda), also to Multicraft dashboard via web (it's only served locally, so a local address). However, no luck getting explorer to reach the files.

Results of Samba appear that it isn't running:
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset:
Active: failed (Result: exit-code) since Tue 2019-04-30 21:20:14 CDT; 30s ago
Process: 1802 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAI
Main PID: 1802 (code=exited, status=1/FAILURE)

Apr 30 21:20:14 localhost.localdomain systemd[1]: Starting Samba SMB Daemon...
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Main process exit
Apr 30 21:20:14 localhost.localdomain systemd[1]: Failed to start Samba SMB Daem
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Unit entered fail
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Failed with resul
lines 1-11/11 (END)...skipping...
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2019-04-30 21:20:14 CDT; 30s ago
Process: 1802 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 1802 (code=exited, status=1/FAILURE)

Apr 30 21:20:14 localhost.localdomain systemd[1]: Starting Samba SMB Daemon...
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 21:20:14 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon.
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Unit entered failed state.
Apr 30 21:20:14 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'.
Not sure why, or how to fix it. Suggestions?

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Windows can't connect to my shares

Postby bigfoot65 » Wed May 01, 2019 9:17 am

To start Samba, do the following in terminal:

Code: Select all

sudo systemctl restart smb
Did you by chance make any changes to smb.conf via command line or in the dashboard.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

gdukin
Posts: 20
Joined: Wed Dec 09, 2015 6:54 pm

Re: Windows can't connect to my shares

Postby gdukin » Thu May 02, 2019 8:05 pm

Command returns the following:
[gdukin@localhost ~]$ sudo systemctl restart smb
Job for smb.service failed because the control process exited with error code.
See "systemctl status smb.service" and "journalctl -xe" for details.
I'd try to post those files, but I'm a linux newb, and really have no clue how to even get to them...

And, I've never messed with the file, I have no idea how I'd even start to do that.

Who is online

Users browsing this forum: No registered users and 7 guests