After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 129890 - 'Sorry, couldn't display all the contents of "smb:///"'
'Sorry, couldn't display all the contents of "smb:///"'
Status: RESOLVED DUPLICATE of bug 132933
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-23 11:21 UTC by Esteban Llácer Ripoll
Modified: 2005-02-12 08:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Esteban Llácer Ripoll 2003-12-23 11:17:44 UTC
Package: nautilus
Severity: normal
Version: GNOME2.2.2 2.2.4
os_details: Ximian, Inc.
Synopsis: Sorry, couldn't display all the contents of "smb:///"
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Description:
Description of Problem:

 on windows network folder, i recive this message:

                Sorry, couldn't display all the contents of "smb:///".


Steps to reproduce the problem:
1. open Nautilus
2. Enter in teh windows network folder or  smb://
3.

Actual Results:

                 Sorry, couldn't display all the contents of "smb:///".

Expected Results:

		Smb machines on LAN

How often does this happen?

    Always

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-23 06:17 -------

The original reporter (ellacer@grupoazahar.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Esteban Llácer Ripoll 2003-12-23 11:31:38 UTC
trace:

*** attempt to put segment in horiz list twice
<-- smb module init called -->
LOCK
UNLOCK
do_is_local(): smb:///
do_is_local(): smb:///
do_get_file_info() smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_open_directory() smb:///
do_open_directory() smb://
LOCK
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
UNLOCK
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
 
** (nautilus:12039): WARNING **: Hit unhandled case 4 (Parámetros no
válidos) in fm_report_error_loading_directory
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
do_is_local(): smb:///
Comment 2 Luis Villa 2003-12-30 02:17:14 UTC
Do you have samba installed?
Comment 3 Esteban Llácer Ripoll 2003-12-30 09:19:24 UTC
Yes, i have de samba installed, and in the past time i could open the
window machines
Comment 4 Ben Williams 2004-05-27 14:02:14 UTC
I have the same problem with Fedora Core 2. I'm happy to provide any requested
debug info. Some relevant package versions:
gnome-vfs-1.0.5-18
samba-3.0.3-5
nautilus-2.6.0-4
samba-client-3.0.3-5
gnome-vfs2-smb-2.6.0-8
gnome-vfs-extras-0.2.0-8.1
gnome-vfs2-2.6.0-8
samba-common-3.0.3-5
Comment 5 Matthew Gatto 2004-05-27 18:22:47 UTC
you sure you don't have a firewall blocking smb ports?
Comment 6 Ben Williams 2004-05-27 18:31:45 UTC
Yes, I've turned off the firewall. Also, "findsmb" at the command prompt
correctly lists all the machines on my network and I can access shares with
"smbclient".
Comment 7 Danielle Madeley 2004-06-01 17:09:08 UTC
Just to check a list of issues I've encountered.

You're not trying to browse a domain controlled by a Windows 2003 domain
controller are you? or
You're not trying to browse a list of shares on a Windows 2003 server itself.

I have found that I can access a specific share on a Windows 2003 machine if I
name it explicitly, but there are issues browsing. This appears to be related to
digital signatures and as far as I know, is a Samba limitation.
Comment 8 Ben Williams 2004-06-01 17:45:00 UTC
I've managed to get browsing working by setting the /system/smb/workgroup gconf
key, but I still get the message when I try to access shares (either by clicking
on the machine or entering the URL).

The domain is controlled by a Windows 2000 domain controller. I get the error
try to access all versions of Windows.
Comment 9 Ben Williams 2004-06-02 17:28:40 UTC
I got this working with the help of the folks on samba-list. They suggested
making sure name resolution was working. I ended up setting my domain name in
/etc/hosts to be the same as the other machines on the network, which solved my
problem.

Perhaps the error dialog can be made more descriptive to help people solve this
problem?
Comment 10 Carlos Rodrigues 2004-07-09 18:59:21 UTC
I see this problem too, and the other machines on my network are running
samba... (well, those that are on right now anyway). The samba command line
tools work fine though.
Comment 11 Matthew Gatto 2004-08-05 04:36:10 UTC
Ben: So nautilus/gnome-vfs samba browsing didn't/doesn't work if your domainname
isn't the same as the other samba file share hosts, yet, it _does_ work with
findsmb in such a scenario?

Can anyone else verify that?

For reference, here's Ben's message to the samba list for reference as well as
his post to nautilus-list:
http://mail.gnome.org/archives/nautilus-list/2004-June/msg00025.html
http://lists.samba.org/archive/samba/2004-June/087024.html
Comment 12 Ben Williams 2004-08-05 14:13:49 UTC
Actually, I'm back to not working at all, really. I did a fresh Fedora Core 2
install and now my domainname fix doesn't even work. All I can see in Windows
Networking is "workgroup" (even though my workgroup is set to something else),
which contains only my own machine. findsmb still shows all of the machines on
the network.

HEAD works slightly better. I can see all the machines on the network but I
can't connect to any. It tells me I don't have permissions without asking me for
username/password.
Comment 13 dch 2004-09-16 14:46:21 UTC
See  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122292

for a fix to this issue.
Comment 14 dch 2004-09-16 14:47:22 UTC
See  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122292

for a possible fix to this issue.
Comment 15 Denny Figuerres 2005-02-06 23:47:33 UTC
testing workaround given of editing gnome-vfs config file to see if that works.

this is a pain in the A$$ to have to try and figure out.
Comment 16 Denny Figuerres 2005-02-06 23:48:37 UTC
testing workaround given of editing gnome-vfs config file to see if that works.

this is a pain in the A$$ to have to try and figure out.
Comment 17 Denny Figuerres 2005-02-06 23:57:15 UTC
still broken!

if I open naut* as a file browser and enter a location as:

smb://192.168.0.123/Name/ it then asks for my auth and works.

but any attempt at browsing for the share fails.

servers can be shown, the domain is shown.

shares are not listed.
Comment 18 Martin Wehner 2005-02-12 08:26:08 UTC
This is a bug in the gnome-vfs smb auth code. It should be fixed in 2.10.

*** This bug has been marked as a duplicate of 132933 ***