From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809
Description of problem:
When I type 'smb:' in the Nautilus location bar I get an error dialog that says
'Nautilus cannot display "smb:///".' If I reboot to (null) this works fine.
This _was_ working in psyche for a while right after I had (fresh) installed.
I have gnome-vfs2-extras-0.99.5-1 installed. I did a forced install of the
Nautilus and gnome-vfs2* packages from (null), this did not help. I reinstalled
the correct Nautilus and gnome-vfs2* packages and renamed my ~/.nautilus and
~/.gconf/apps/nautilus directories, still does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start Nautilus
2. enter 'smb:' in the location bar
Actual Results: I get an error dialog that says 'Nautilus cannot display
Expected Results: Nautilus should display SMB shares.
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:
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.