Can't connect to my shared drives!

I just upgraded from SuSE 11.3 to 11.4.

For some reason, I can no longer access my shared drive from any other home computer.

I can get out to the internet.

I can ping other PCs on the network.

Other PCs can ping me.

My router sees all computers, and has assigned IP addresses dynamically.

I have a shared folder, exported as an NFS mount point, that used to work!

I’ve tried setting up Samba shares. Nothing!

I disabled the local firewall, as my router already has a firewall running. Nothing!

Nothing I’ve tried seems to work.

I can not see that NFS mount point from any of my windows PCs. (I only have the one Linux server running, so I can’t say whether another Linux box would see it or not!)

Any help, guidance or suggestions would be greatly appreciated!

TIA

jxfish2

jxfish2 I just upgraded from SuSE 11.3 to 11.4.

For some reason, I can no longer access my shared drive from any other home computer.

I can get out to the internet.

I can ping other PCs on the network.

Other PCs can ping me.

My router sees all computers, and has assigned IP addresses dynamically.

I have a shared folder, exported as an NFS mount point, that used to work!

I’ve tried setting up Samba shares. Nothing!

I disabled the local firewall, as my router already has a firewall running. Nothing!

Nothing I’ve tried seems to work.

I can not see that NFS mount point from any of my windows PCs. (I only have the one Linux server running, so I can’t say whether another Linux box would see it or not!)

Any help, guidance or suggestions would be greatly appreciated!

TIA

jxfish2

jxfish2 this could be the nmb problem. Here is a quote from swerdna in another message here on the subject:

You use the GUI with this workaround:

Yast -> Novell AppArmor -> AppArmor Control Panel,

Click on Set profile modes (Configure) button,

Highlight the entries ‘usr.sbin.nmbd’ and ‘usr.sbin.smbd’ in turn and, for each, click the Toggle Mode button to set the mode from ‘enforce’ to ‘complain’.

Click Done, OK etc etc.

Anytime you are sharing an NTFS partition I might suggest you change the mount options to say just defaults like this:

/dev/disk/by-id/ata-WDC_WD3000GLFS-01F8U0_WD-WXL408720641-part2        /Windows    ntfs-3g    defaults            0    0

Here is another quote about a problem with NTFS partitions as well:

If it’s an NTFS hard drive and if you’re using openSUSE 11.4: there’s a bug in openSUSE 11.4 that stops NTFS from being recognised.

Yo have to open the text file “filesystems” located at /etc/filesystems and edit it so it looks like this:
Code:

vfat
hfs
minix
reiserfs
ntfs
*

So, there are three suggestions here. I would use all three and see what happens for you.

Thank You,

On Sun, 24 Jul 2011 17:06:02 +0000, jxfish2 wrote:

> I have a shared folder, exported as an NFS mount point, that used to
> work!

On the server, what do you see recorded in /var/log/messages that relate
to the issue?

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Try this:

In /etc/nfsmount replace “#Defaultvers=4” by “Defaultvers=3”, please not the “#”, it should be removed. Then restart NFS and you should be OK.

Hi James,

I tried the AppArmor and /etc/filesystems suggestions you gave, and I attempted to do the NTFS partition trick you noted, but I don’t know where to put it!

I tried putting it in /etc/exports, but exportfs complained and errored out!

Besides, I don’t think I’m exporting the filesystem as an NTFS filesystem.

Jim,

Now, to your response:

I was getting what looked like a warning: "/etc/exports [1]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “*:/Family”. Assuming default behavior. NOTE: This default has changed since nfs-utils version 1.0.x.

I put “subtree_check” as an option inside of /etc/exports, and am no longer getting the warning inside of /var/log/messages.

However, none of these suggestions has helped!

Here’s what I’m seeing:

Everything looks fine from my Linux box.

But, when I attempt to map the drive to my linux box from within any of my Windows PCs, the PCs don’t see the Linux server at all!

They can all ping it.

The router sees it, and assigns it a static IP address.

I’m not using domain names here at home, just WORKGROUPS.

I can’t get the GUI tools to work like I want them to.

Is there a flat file that I can edit, to update the Windows WORKGROUP entries?

I already did a recursive search of the /etc subdirectory, looking for my WORKGROUP string name, but it came back empty!

TIA

jxfish2

AFAIK You cannot mount an NFS share on a Windows PC. openSUSE 11.4 defaults to NFS4, which is different and needs extra configuration. Therefore, change to NFS3, like writen above.

As for Samba: if I’m unsure, or cannot achieve what I want within the time I have, I change the security option in Samba from “user” to “share”.

File to edit for a samba config: /etc/samba/smb.conf

On Sun, 24 Jul 2011 21:16:03 +0000, jxfish2 wrote:

> I was getting what looked like a warning: "/etc/exports [1]: Neither
> ‘subtree_check’ or ‘no_subtree_check’ specified for export “*:/Family”.
> Assuming default behavior. NOTE: This default has changed since
> nfs-utils version 1.0.x.
>
> I put “subtree_check” as an option inside of /etc/exports, and am no
> longer getting the warning inside of /var/log/messages.
>
> However, none of these suggestions has helped!

That particular message indicates that it’s falling back to the default
behaviour, so adding that to the config wouldn’t change the behaviour
specifically.

Can you telnet to the NFS ports on the server from the other systems?

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

YES! YES! YES!

These last two changes did the trick!

I’ve been fighting with this myself, off and on, for more than a week!

Thank you all SO MUCH!

I’m not sure which of the two did the trick, or if it needed both of them, but I’m finally at peace with the world!

Thanks again, and have a great summer!

jxfish2

YES! YES! YES!

These last two changes did the trick!

I’ve been fighting with this myself, off and on, for more than a week!

Thank you all SO MUCH!

I’m not sure which of the two did the trick, or if it needed both of them, but I’m finally at peace with the world!

Thanks again, and have a great summer!

jxfish2

So what two things was it that you did? Are you using Samba or what to share with Windows machines? I use Samba myself in a Workgroup setup and it works just fine with Windows PC’s but I guess I am unsure of what you are doing.

Thank You,

I modified the NFS4 to NFS3, and set the security entry in the smb.conf file to share. For some reason, it was set to DOMAIN.

Since I could not even see the server before this, I’m assuming that the NFS3 entry allowed me to see the server, while the Samba entry allowed me to actually login.

Of course, it could have been the Samba entry all by itself.

But, it doesn’t matter to me at this point, because I can work now!

jxfish2

I modified the NFS4 to NFS3, and set the security entry in the smb.conf file to share. For some reason, it was set to DOMAIN.

Since I could not even see the server before this, I’m assuming that the NFS3 entry allowed me to see the server, while the Samba entry allowed me to actually login.

Of course, it could have been the Samba entry all by itself.

But, it doesn’t matter to me at this point, because I can work now!

jxfish2

So if the security setting in the smb.conf file is set to DOMAIN, that would be wrong and share option is a better setting for sure. I think that was the problem. Now the other items I mention had to do with sharing a NTFS partition with Samba. I have found it best for any NTFS partition to modify how it is mounted in the fstab file to just say defaults as in my example. Further, there was a known problem with auto-mounting NTFS partitions and the file /etc/filesystems where I show an example of how to fix that file. Finally, there was a problem with outgoing shares in Samba to Windows due to the issue with nmb and AppArmor in openSUSE. And, other issues can also exist with your Firewall settings and more. It is hard to get through all of the potential issues, but I am happy to hear you found a solution.

Thank You,

James, I just wanted to let you know that I was having basically the same problem as the original poster. In my case, I have a simple Linux file server at home which serves 4 Windows boxes. The hard drive with the OS (v11.1) failed Friday night, and I installed 11.4 to a new drive yesterday morning. The server contains a separate RAID 1 volume where all of everyone’s data is stored, so I was anxious to get things back up so I could access it. However, I spent until the wee hours of Sunday morning trying to just get my Windows boxes to see the Linux server with absolutely no success. Wish I’d found your post last night, because I made the changes described above and am now back in business. Man…I spent at least 8 hours chasing my tail on that one and would NEVER have figured it out.

Thank you for the help, it is greatly appreciated!

James, I just wanted to let you know that I was having basically the same problem as the original poster. In my case, I have a simple Linux file server at home which serves 4 Windows boxes. The hard drive with the OS (v11.1) failed Friday night, and I installed 11.4 to a new drive yesterday morning. The server contains a separate RAID 1 volume where all of everyone’s data is stored, so I was anxious to get things back up so I could access it. However, I spent until the wee hours of Sunday morning trying to just get my Windows boxes to see the Linux server with absolutely no success. Wish I’d found your post last night, because I made the changes described above and am now back in business. Man…I spent at least 8 hours chasing my tail on that one and would NEVER have figured it out.

Thank you for the help, it is greatly appreciated!

richj44, I am very happy to hear you were able to solve your problem with information you found in the openSUSE forum. We are here to serve as best we can. Please, if you have any other issues, don’t be shy, just ask away and we will try to help.

Thank You,