Bug 75437
Summary: | Nautilus cannot display SMB shares | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ted Clark <bison> |
Component: | nautilus | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | hp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-10 12:58:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ted Clark
2002-10-08 16:15:44 UTC
Does smb://some_machine/ work? (where some_machine is the netbios name of some machine with smb exports on the local network) Yes, it does work! So it seems browsing is broken. Just to check, can you please try these: smb: smb:// smb:/// And write down exactly what the dialog tells you for each of them. Now this is interesting.. smb: -> Nautilus cannot display "smb:///". smb:// -> Nautilus cannot display "smb:". smb:/// -> Nautilus cannot display "smb:///". But it doesn't say "smb:///" is not a valid location. Please check the spelling and try again. which would have indicated that smb support wasn't found. So, something goes wrong while trying to browse the lan. strange. Nope, I don't get any error messages about not being a valid location. This used to work, and reinstalling the packages did not fix it, so I think there's probably some configuration or state information squirrelled away somewhere that's messing it up. Any idea on where to start looking? Other people who have seen this had a firewall set up that was in the way. Can you try: /sbin/service iptables stop /sbin/service ipchains stop as root, and then retry. Stopping and restarting iptables worked. Thanks Alex! Was there ever a solution to this? I am running Redhat 9 and I am encountering the exact same behavior. |