Optional Information Needed to Connect to Samba Share

[Michael Devenish]

I'm using a fresh install of hardy beta on a desktop pc with today's (28 Mar) updates applied. If I try to connect to a samba / windows share, on my link station, using Places -> Connect to Server... and only enter the service type (windows share) and server name / ip address, I get the following error message:

'Can't display location "smb://192.168.0.4/"
No application is registered as handling this file'

However, if I then go back to the connect to server dialog box and enter the same details, but also include the share name, it connects and I get the "Enter Password" dialog box. I then enter the username, domain and password and the shared folder opens up in nautilus as expected.

On my main machine running gutsy, if I only enter the service type (windows share) and server name, nautilus opens up and shows all available shares.

Also (not sure if this is related or is another issue), before I've connected to the samba share, if I select Places -> Network then double click on "Windows Network" nothing displays in nautilus. This also happens in gutsy. Once I've connected to a samba share, going to Places -> Network and double clicking the "Windows Network" then shows all the shares on my network and I can browse the folders.

Thanks

[Klass (dan-djohnson)]

Exact same problem on Hardy Heron with latest updates as of (28th of Mar). This problem has been here since Alpha 4.

[Kevin Williams (bthylafh)]

This is happening for me as well, latest updates as of 8 Apr 2008, on a fresh install from the beta CD. I'm running AMD64 version.

[Justin Bowes (daft-angus)]

I can confirm this too. AMD64, latest updates, upgrade from Gutsy.

As a workaround, entering the same path that is returned in the error dialog (e.g. smb://192.168.1.135/) into Nautilus with Go > Location (ctrl+L) works, and any share I subsequently browse into on the specified host is shown on my desktop.

Even when I do not use the workaround, if I perform the Places > Connect to Server... (enter hostname only) procedure a second time, I get a different error message:

Cannot display location "smb://192.168.1.135"
Location is already mounted

[[e-mail] (smileypaul)]

I can confirm this as well.

Connect to server doesnt work.
Also cannot browse windows network.

Listing the shares in the terminal via smbclient works just fine.

[Emanuele Olivetti (emanuele-relativita)]

Quite the same problem for me: a fresh install of Hardy Heron (amd64)
updated until today (21 Apr 2008). Everything works well with some other Gutsy box.
In any case smbclient works well. It seems a gnome issue...

Places -> Connect to Server... -> Windows share
I fill these entries:
- Server : 192.168.235.8
- User name : *******
- Domain name : *******

Then I got an error:
'Can't display location "smb://192.168.235.8/"
No application is registered as handling this file'

If I repeat I got:
'Can't display location "smb://192.168.235.8/"
Location is already mounted'
But there is no evidence in Nautilus or on Desktop about that
connection.

If I provide the 'Folder' information too, so:
Palces -> Connect to Server... -> Windows share
- Server : 192.168.235.8
- Folder : public
- Unser name : *******
- Domain name : *******
After the password prompt I got the usual message
'Can't display location "smb://192.168.235.8/"
No application is registered as handling this file'...
but a "192.168.235.8" icon appears on Desktop (it's the smb
connection)! If I double click it I get the authorization request (login,
password and domain) and then a _second_ icon appears on the screen,
identical to the previous one. Now nautilus shows successfully
the content of the windows share.

If I unmount the 'first' smb connection (left click on the first icon
on Desktop) it disappears but the connection to the windows
share still holds. Unmounting the second smb connection removes
the actual connection.

Even more strange: If I use gnomevfs from command line everithing
works ok, even without specifying the target folder:
gnomevfs-ls smb://192.168.235.8
(asks for login, domain and password)
then it shows the required information.

[Alex Zhou (zhou-zheng)]

I can confirm this too. also with latest updates, upgrade from Gutsy into Hardy.

[sidorka (sidorka)]

the problem is still present in final release 8.04

[Brian Murray (brian-murray)]

Reviewing this bug report and its comments it seems that multiple people are experiencing this problem. Subsequently, I am confirming this bug report. For future reference you can manage the status of bug reports by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

[Shawn vega (svega85-gmail)]

I'm Having the same problem aswell.

[Alex Karpenko (alexkarpenko)]

I can also confirm the bug with Hardy amd64 and all the latest updates applied.

[WilliamLassen (raculot-gmail)]

Bug is still present, and I can still confirm that it occurs in Hardy x86.

Is anything being done?

[Tiago Faria (gouki)]

This bug is a duplicate of 216104[0]

[0] - https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/216104

[nabdan (nabil2)]

Same issue with fresh install Ubuntu hardy install.

[Piraja (piraja-deactivatedaccount)]

I confirm. In my home network, I have a desktop with WinXP on internal HDD and Ubuntu on an external HDD partition. Both systems have Samba shares and a shared printer.

I can connect out-of-the-box to the server, access shares and remote print from my laptop using Linux Mint installed on one partition, but not from the Hardy (x86) partition.

[Piraja (piraja-deactivatedaccount)]

In my case it was not a bug after all, it seems. I installed Guarddog (having used it earlier but, for some reason, having also uninstalled it) and fixed the problem by changing the firewall settings. So the "bug" was due to restrictive iptables settings, as it seems.

Sorry for the unnecessary post.

[Piraja (piraja-deactivatedaccount)]

I'm afraid I rejoiced too early, i.e. the problem persists. Yesterday I could mount the shares after checking a few boxes in Guarddog, but the host machine (my desktop acting as a file and print server, as well as my kids' gaming machine) was running Windows at that moment. Today I tried mounting the shares and printing from my Ubuntu laptop while also the desktop was running Ubuntu (installed on an external HDD partition), but could not.

Is this bug really a duplicate of #216104? I wonder, because the error message differs slightly (here "No application is registered as handling this file", there "The specified location is not mounted"). Perhaps I'm just ignoring something (as a strictly non-technical — but well-meaning — user).

[Piraja (piraja-deactivatedaccount)]

In the latest automatic Samba updates (Sept. 6, 2008) the bug seems to have been fixed. Now I can access the shares on my Ubuntu desktop from my Ubuntu laptop with no hassle in my home network. I'm so pleased I thought I must post thanks for that. Great work!!

[Michael Lueck (mlueck)]

I fetched down those updates to Samba on my Hardy 8.04 32-bit system, rebooted, and now this morning see your comment Pajari.

So I tested creating a connection, filling in:
server
share
userid
domain

At the next dialog entered my password, and selected the radio button to "remember password until I logout".

As usual, up came the usual error dialog, which I closed.

Clicking on the desktop icon, it opens but it also doubles up that icon creating a second icon "exactly" the same as the first.

Looks the same to me.

[richbl (richbl)]

I can concur with Michael Lueck in the comment above: I'm also seeing identical incorrect functionality.

DOES:

0. Go to Places \ Connect to Server...
1. Service type: Windows Share
2. Fill in Server, Share, User Name, Domain Name
3. Click Connect

An error dialog is displayed:"Can't display location smb://.... The specified location is not mounted"

In Nautilus with side pane (tree view), I see two identical share icons listed.

SHOULD:

Not generate an error message.
Not create two identical share icons.

[Piraja (piraja-deactivatedaccount)]

I must add one more thing: if I do "gksudo nautilus" I still cannot mount the shares (the error message states that Nautilus cannot handle network places; writing this in another environment, I cannot check the precise formulation of the message now), but as a regular user everything works fine.

[kafkalias (osfp-andreas)]

This might help. It seems that you might not have nautilus.
So try and run:

sudo apt-get install nautilus

hope this helps

[Michael Devenish (mdevenish)]

I still have the same issue as per my initial message, this time using Jaunty beta with the latest updates applied. Selecting Places -> Connect to Server... and only entering the service type (windows share) and server name / ip address, I get the following error message:

'Can't display location "smb://192.168.0.4/"
No application is registered as handling this file'

As before, if I enter the share name (i.e. it isn't optional) I then get the dialog box to enter username, domain and password and everything displays correctly (I think this is the fix described in bug #216104 - https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/216104).

However, if I now (before or after connecting to the samba share) select Places -> Network then double click on "Windows Network" I see the server and I can then browse to my network shares. Double clicking a share brings up the login dialog box and everything is working as expected. I'm really happy to see this finally working in nautilus.

Thanks