Can't see contents of windows share on NAS with 8.10

Asked by David Samuels

I have a small workgroup made up of:

1 x Windows XP Pro desktop
1 x Windows XP Pro/Ubuntu dual-boot laptop
1 x Ubuntu desktop
1 x Freecom 250GB NAS drive

all hardwired to a Netgear DGFV 338 ADSL/DSL router, which supplies the DCHP. Both Ubuntu machines load Firestarter automatically at startup

I have just updated Ubuntu from 8.04 LTS to 8.10 but have made no changes to any configuration. Since the upgrade, the Ubuntu machines cannot see the contents of the /Public directory on the NAS drive. Selecting Places|Network from the menu loads Nautilus, which shows 2 entries:

a) the NAS device, named FND
b) the Windows network

Double-clicking FND then replaces the display with an entry for PUBLIC as the single windows share on FND.

So far so good. Now comes the problem: whenever I try to display the contents of PUBLIC folder (e.g. by a double-click), Nautilus immediately reverts to showing the contents of my home directory instead of the contents of //fnd/public. Under 8.04, the contents of /public were shown without problem.

Any ideas, anyone?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu samba Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
A-M Fagertun (amef) said :
#1

I have got the same problem. I have a small home network with both Windows XP and Ubuntu PC:s.
In 8.4 I can get acess to my Iomega Network Drive but after upgrading to 8.10 I got the same problem as David Samuels. Found the same problem when I tested the Beta 8.10 and hoped it to be solved in the new release. I use the Network drive as a "file-server".

Revision history for this message
David Samuels (davidmsamuels) said :
#2

Can we be the only ones with this problem? The world has gone very quiet and I still can't see the NAS drive. There must be a simple explanation or some tweaking via the netwoeking management system but I'm a Linux novice and dodn't know where to start.

Revision history for this message
Braam Wijsmuller (stratofarmer) said :
#3

I'm having the exact same difficulties with the Iomega NAS.

It seems to be the same problem as with this issue: https://answers.launchpad.net/ubuntu/+source/samba/+question/49766
This concerns a different brand NAS, but the symptoms are the same.

I haven't tried the tips mentioned in here yet though:
https://answers.launchpad.net/ubuntu/+source/samba/+question/46427

Revision history for this message
David Samuels (davidmsamuels) said :
#4

I just tried the suggested fix from #46427 but no joy -- trying to open the share just causes Nautilus to change to my home directory. Thanks for the steer, though.

Revision history for this message
A-M Fagertun (amef) said :
#5

I also tried the suggested fix #46427 but nothing changes at all.
My shared folders on Windows PC:s have never been any problem, I still have access to them from my Ubuntu stations... it is the network drive that is the only problem.

Revision history for this message
David Samuels (davidmsamuels) said :
#6

My situation is exactly the same as A-MF for shared folders on Windows PCs -- I can see them and get to them from my Ubuntu machines. It's just that, although I can see the /public directory on my NAS, I can't get to it either with my browser or using Nautilus.

Revision history for this message
Braam Wijsmuller (stratofarmer) said :
#7

The following workaround works for me. (my NAS is a 320gb Iomega network disk)

create te mount dir:
sudo mkdir /media/iomegadrive
sudo chown stratofarmer:user /media/iomegadrive

mount the drive to the folder:
smbmount //192.168.1.37/PUBLIC /media/iomegadrive -o guest,nounix,uid=stratofarmer,gid=users

Now I can browse the local folder to which the network drive is mounted.

I shame we can't use vfs...

Revision history for this message
David Samuels (davidmsamuels) said :
#8

As a workaround, StradoDude, it does the business. Sadly, it's not the answer because I have to go through that every time I start up. It should be available through Nautilus first off, as it was in 8.04.

Revision history for this message
Braam Wijsmuller (stratofarmer) said :
#9

The solution seems to be given here:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/282298

dowloading the following fixed version of the smb library (for intrepid) is said to solve the problem:
http://launchpadlibrarian.net/19559308/libsmbclient_3.2.3-1ubuntu3_i386.deb

Revision history for this message
Braam Wijsmuller (stratofarmer) said :
#10

The 'solution' I mentioned seems to be for a different problem than mine. The Iomega drives seem to have a more specific problem.

Revision history for this message
A-M Fagertun (amef) said :
#11

I dowloaded the following fixed version of the smb library (for intrepid)and it did solve my problem:

http://launchpadlibrarian.net/19559308/libsmbclient_3.2.3-1ubuntu3_i386.deb

Now I am able to use my Iomega NAS as I have used it before!

Thanks for your help and assistance!

Revision history for this message
David Samuels (davidmsamuels) said :
#12

It may work for you, A-MF, but not for me. It seems that, as StratoDude said, <quote>Iomega drives seem to have a more specific problem.</quote> and you seem to have found a solution. Installing the replacement lib actually makes my situation worse: Nautilus now can't find the drive by itself and I have to address it as smb://fnd/ specifically. And even when I can see the PUBLIC folder, clicking it still makes the display revert to my home directory.

What is consistent, however, is that, if I try the "Connect to server" route from the Places menu, the folder appears momentarily on the desktop and immediately disappears again after forcing a repaint of the entire desktop. This behaviour has persisted since I installed Intrepid.

So far, only StradoDude's mounting workaround is any good!

Revision history for this message
Unbuntonaut (dpatrickallen) said :
#13

I am having the same problem with Intrepid 8.10. Trying to mount through Nautilus just flashes and take me to my home directory. I am using an Iomega 500GB Home Network Ethernet drive.

The package listed:
http://launchpadlibrarian.net/19559308/libsmbclient_3.2.3-1ubuntu3_i386.deb
did not help.

I'll try StradoDude's mounting workaround I guess.

I hope that someone is looking into it.

Revision history for this message
Unbuntonaut (dpatrickallen) said :
#14

Well StradoDude's mounting workaround (see above) worked for me (thanks for the workaround Strat).

So, I added the

smbmount //000.000.000.000/PUBLIC /media/iomegadrive -o guest,nounix,uid=XXXXXXX,gid=users

(where 000.000.000.000 is the IP address of the drive and XXXXXXX is the userID. I also trimmed off the "gid=users" option.)

command to the "Startup Programs" (System>Preferences>Session)

Now it mounts automatically on login.

I do get a stop error on shutdown or restart with Startodude's workaround, but hey, at least I have access to the NAS again for now.

Revision history for this message
David Samuels (davidmsamuels) said :
#15

Ubuntonaut:

I've done exactly the same for the time being. I, too, hope that something is being done somewhere about this problem; if you search the various fora for "smb" or "samba", you'll quite quickly find that Intrepid upgraders with NAS devices are all screwed and unhappy!

Revision history for this message
Launchpad Janitor (janitor) said :
#16

This question was expired because it remained in the 'Open' state without activity for the last 15 days.