PC not able to open Humax folder on network

[pADDYB]

My Hummy shows up in my computers network, but when I try and open the folder I get a message "HUMAX is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find if you have access permissions. The network address is invalid.".

I can still access the box using remote access and set recordings using the RS package and can also access files using my laptop on the same network, so guessing it's something in my PC settings, though I haven't consciously changed anything. I've occasionally had this problem in the past, but it has gone away after rebooting pc/humax, but not this time, it's been like this for a few days now.

Hope someone can help.

 

[Black Hole]

More details required, such as the operating system and version of both working and non-working computers.

 

[pADDYB]

Thanks for getting back to me.

Win 10 Pro on both.

 

[pADDYB]

Correction, Laptop is Win 10 Home.

 

[Black Hole]

WIndows is a bugger for this sort of thing, frankly. I take it you have the samba package installed, and you have configured the appropriate settings (on the Win PCs) to enable SMB1?

 

[pADDYB]

Yes, I have the samba package installed and running. Not sure how to check if it's correctly configured in Windows, is there a guide to setting it up on this forum?

 

[MymsMan]

Have a look at https://docs.microsoft.com/en-us/wi...oot/smbv1-not-installed-by-default-in-windows

 

[pADDYB]

Thanks. I remember having a similar problem when I first started using Win 10. I posted this thread and found out the answer was that I needed to enable SMB 1.0:
https://hummy.tv/forum/threads/new-pc-humax-not-showing-in-windows-explorer.9761/#post-142382

I checked how to do this using this guide, but it seems to be already enabled:

Site Deactivated – Ideas Proposals for New Features / Idées et suggestions

I did the CMD prompt instal as well, but still no joy.

 

[Black Hole]

Try rebooting your router.

 

[pADDYB]

I've done that multiple times, also the humax and pc.

 

[peterworks]

Are the workgroup names the same on both pcs and /mod/etc/smb.conf?

 

[pADDYB]

The workgroup name on both computers is Workgroup.

On the PC, all the SMB boxes are ticked. On the Laptop (which works) SMB 120 CIFS Client Server is unticked. There is also a box SMB direct that is ticked on the PC, but that box is not present on the Laptop.

Not sure what you mean by mod/etc?

 

[peterworks]

Not sure what you mean by mod/etc

It's on the Humax - you can check using FTP. Default for the smb.conf is workgroup I seem to remember.

 

[pADDYB]

Thanks, can you elaborate on how to check this please?

 

[peterworks]

Seen this (https://docs.microsoft.com/en-us/windows-server/storage/file-server/smb-direct) :
SMB Direct requires the following:

• At least two computers running Windows Server 2012 R2 or Windows Server 2012
• One or more network adapters with RDMA capability.

Try unticking SMB Direct and reboot.

 

[pADDYB]

Unticking SMB direct did the trick! Thanks for you help with this.

 

[pADDYB]

Struggling with this again on a Windows 11 Home Laptop. Can't see the Humax folder whatevery options I tick / untick and muliple reboots etc. Any ideas?

 

[Black Hole]

You might have to simply accept that Windows is making things on old protocols harder and harder to access, for "security"* purposes.

* For "security" read "we know nobody takes any notice of potential threat warnings, so were gonna turn off any possibility of accessing insecure resources so there is no possibility of you suing us when something does go wrong, even if the resource is on your home network under your own control."

The solution I have adopted is to get Microsoft out of my life wherever possible, and where that isn't possible I'm running Win7.

A possible solution for you is to try NFS protocol instead of SMB, or failing that FTP.

 

[MartinLiddle]

Struggling with this again on a Windows 11 Home Laptop. Can't see the Humax folder whatevery options I tick / untick and muliple reboots etc. Any ideas?

Does this article help https://www.supportyourtech.com/tech/how-to-enable-smb1-on-windows-11-step-by-step-guide-for-users/

 

[prpr]

If anyone's feeling brave, they can try using Samba 3 which gets rid of the requirements to install SMB1 support on Windows.