Created attachment 1631925 [details] browse URL of attached USB in router Description of problem: Unable to browse local network folders of my routers attached USB Pendrive Version-Release number of selected component (if applicable): How reproducible: consistent Steps to Reproduce: 1.open/use file browser 2.click link open/to local network folder 3.Error:Internal Error Actual results: Unknown error condition in stat: Software caused connection abort Expected results: open folder URL Additional info: Was ok on fc30 Wasn't sure which component I recompiled the kernel with hoping to correct it but to no avail.
Upgraded fc30>31 and the ability to browse USB Pendrive in the back of the router ceased
Hi, I had a similar problem with samba connections with my network storage. As found in this post: https://bugzilla.redhat.com/show_bug.cgi?id=1753835# -> Samba 4.11 switched off SMB1 protocol support by default. Check the settings of your router, if you can select a higher version of Samba then 1. This solved my issue with the NAS. Best regards, sidewinds
There's nothing I can change on the router. I think the kernel changed with USB gadgets support...giving another try with recompiling as nothing else is making sense
Thank you Samba...oh well probably insecure, I can use it on Android with an address of smb://192.168.1.254 so I'll just use that until if ever this becomes available again
Did you try the other SMB1 dialects, e.g. NT1, LANMAN2 and LANMAN1? Details: https://www.samba.org/samba/history/samba-4.11.0.html (section "SMB1 is disabled by default")
Not sure I understand what that means but my LAN attached printer is found with no problems I replaced smb:// with NT1://, LANMAN2:// and LANMAN1:// but just got 'protocal not supported' or should I manually configure smb.conf?
It means e.g. the options in smb.conf: Example: [global] client min protocol = NT1 But it did not work for me.. My NAS had the option to use SMB2 or 3.
Cool That Hit it. Exactly as your example! Thank you @sidewinds
*** Bug 1770549 has been marked as a duplicate of this bug. ***