Description of problem: Error connecting to samba share "Invalid argument" with correct authentication information. I am able to connect on my macbook with no issue, but unable to connect on my Fedora workstation (replacement for macbook). Error occurs with hostname (smb://server) and IP address (smb://192.168.1.x). Version-Release number of selected component (if applicable): Fedora Linux 38 (Workstation Edition) Kernel version Linux 6.4.6-200.fc38.x86_64 Gnome version 44.3 Files (Nautilus) version 44.2.1 Samba Client (smbclient) version 4.18.5 How reproducible: , , , , and receive error. See screenshot Steps to Reproduce: 1. Open "Files" 2. Click "Other Locations" 3. At the bottom of the window where it says "Connect to Server", type in "smb://server" (my actual server name), or "smb://192.168.1.x" (last octet withheld) 4. Press "Connect button" 5. Receive error: "Unable to access location Failed to retrieve share list from server: Invalid argument" Actual results: Error message Expected results: List of shares Additional info: No issue connecting on my macbook with same information
Created attachment 1982863 [details] Screenshot of error
During an exhaustive internet search prior to submitting bug and reading the status of 2072885, I found Gnome Files (Nautilus) bug 2206 (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2206) that is exactly my issue, although Files (Fedora 36) and Samba client (4.16.0) versions are older. The workaround was to downgrade to samba client version 4.15.5-1. I figure by samba client 4.18.5 (current), the issue would have been addressed. Am I mistaken? I don't want to downgrade unless absolutely necessary. Please advise.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.