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 545885 - Can't browse Windows shares in Domain
Can't browse Windows shares in Domain
Status: RESOLVED DUPLICATE of bug 524485
Product: gvfs
Classification: Core
Component: smb backend
0.2.x
Other All
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-08-01 17:11 UTC by Steve Lougheed
Modified: 2014-05-29 06:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Steve Lougheed 2008-08-01 17:11:28 UTC
Please describe the problem:
I'm running Ubuntu 8.04.
We have a domain environment.
I can find the servers using the Places>Network nautilus app.
When I select one of the servers I'm not prompted for a password and I do not see any of the shares. 
I can see the servers but the shares are not shown. If then I then add a share name to the end of the address ie. smb://jehu/trillium "trillium" is a share on server named "Jehu". Doing this prompts the authentication dialog and I then can access the share.



Steps to reproduce:
1. Click Places>Network
2. Select a server from the list
3. No shares are listed.


Actual results:
I see a blank white window with no shares listed, no prompting for authentication to the network share is given. No shares are seen.

Expected results:
I expect to be prompted for authentication to the network share, upon successful authentication I expect to see the shares on the server I've selected.

Does this happen every time?
yes without fail

Other information:
This doesn't happen when using Kubuntu, the issue seems very much part of Gnome and Nautilus only.
Comment 1 Renzo Bagnati 2009-01-24 09:12:00 UTC
I believe this is a duplicate of bug #524485
Comment 2 Ross Lagerwall 2014-05-29 06:24:58 UTC

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