Share does not work properly

English Network/Internet
1

The following is quit long, however, I am trying to show the environment they exist in.

I am in no way a network guru, however, over the years I have been able to set up my home networks
quit successfully! I am presently setting up a replacement machine and have installed Linux 13.1 on
one disk drive and Linux 13.2 the other (both being OpenSuse). One drive has two partions (1) Win
8.1 and (2) Linux 13.1 the second drive has three partions (1) win 10 (2) ntfs (3) Linux 13.2…

I wan’t both Linux systems to mount and use the (ntfs) (Which is to store both Win and Linux files)
which works fine.

However, on both Linux systems I am running various virtual machines in both vmware and vbox and wan’t
them to be able to connect to the mounted (ntfs) drive/dir. On the 13.1 system I do! On the 13.2
I do not and can’t make it do so!

On the 13.1 system going to Yast-samba-samba configuration has listed under “Available Shares”
it has the line “Enabled no Linux-10 /srv yes My-files” In 13.2 This line does not Note: Linux-10 is name for ntfs partition mount point /srv
exist. So In 13.2 I selected (add) and entered this as a share, however, after selecting (OK)
This Pops up
[Enter the username and the passwork
for joning the domain (my workgroup)

 To join the domain anonymously, leave
 text entries empty

 Username   etc.]

I have no clue what it want’s, so I put in my username and password and selected OK won’t accept
that, so cleared Username and password and selected OK wouldn’t accept that either so selected
(do not join) and OK and I’m returned to the Yast control center. Later after determining that
it does not work wen’t back to Samba configuration and deleted that line and selected OK and
the same events happened but the line was gone.

Next I compared each of the “smb.conf” files

LINUX 13.1

[global]
workgroup = rj2611
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = Yes
idmap gid = 10000-20000
idmap uid = 10000-20000
security = domain
usershare max shares = 100
wins support = No
wins server =

LINUX 13.2

[global]
workgroup = rj2611
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = No
domain master = No
security = domain
usershare max shares = 100
wins support = No

I should point out that the “Samba configuration” window does not reflect the “smb.conf” file

Would it be advisable to edit my smb.conf file and if I could, how to get it reflected in the “Samba configuration share” window?
In general, What can be done to correct or repair my problem any ideas would be accepted.

2

Sounds to me that you want to access a drive on your machine from multiple OS (running on the same machine)?

To do that, you don’t need to use SAMBA.
SAMBA provides network connectivity to resources on different machines, not necessary on the same machine.

You only need to modify the NTFS permissions to either allow specific Linux User Account access (preferred) or simply go into the file permissions using your Windows and set your NTFS permissions to allow full access to all (As you might expect, this raises some security concerns but YMMV).

Once your permissions issues are addressed, you can then mount the drive in your Linux systems.

TSU

3

Those smb.conf files do not have stanzas for the directories that you want to share over the network. Can you paste the full smb.conf files please? The [global] stanzas need work, but let’s see the whole smb.conf files first so we can see the real root of the problem?

4

Also, are you really trying to create a complex domain (in the microsoft windows sense of “domain”) or are you simply trying to create a home-style LAN (ie a so-called workgroup)?

5

ahhh swerdna at last! Yes, a home-style LAN. Since my initial posting I have edited my smb.conf file [Global] to match my 13.1 sys smb.conf file [Global], and things appear to be all right. However, can’t get the central drive [Linux-10] to be shared (A partition which is mounted via /srv and I store common files). I have discovered that there may be a problem with (networkmanager).

	 	 	 	   In 13.1 sys.

Configure desktop – network connections - system settings it lists [network connections] [Proxy]
[connection preferences] service discovery] However, 13.2 does not contain [network connections] Reminder; 13.2 is the problem child and 13.1 works great!

13.1 sys Yast2 – software management – network package lists networkmanager-kde4-(etc) 13.2 has no kde4 listings. As an example sys 1 contains networkmanager-openvpn and networkmanager openvpn-kde4 - Sys 2 has openvpn and doesn’t have openvpn-kde4

In Yast2 -network settings - Global Options – network setup method I’m offered networkmanager Service or wicked services or networkmanager Service Disabled - there is no option for either using or not using networkmanager. If I select [networkmanager Service Disabled] I lose my network and can not get into [Overview] to edit or to setup the network with out networkmanager. Actually on my system [global options] is a misnomer! I really have no options. Hope this gives you some food for thought?

6

Re. wicked / Networkmanager: in your case, use wicked. Treat the configuration like you did on 13.1 , if you use a static IP, don’t forget to add DNS’s ( google’s 8.8.8.8 and 8.8.4.4 always work ) and the gateway ( most probably your router’s ip address.). Check /etc/resolv.conf.

7

Thanks for the input! I tried using wicked but could not get on the internet or any thing. I have a wireless network. Later in the day I was reading wiki features which listed a discussion about wicked and it pointed out it was a replacement for ifup (which is what my 13.1 sys was using). I opened YaST2 network settings - overview and deleted my wifi adapter. I then closed YaST2 and went to “panel options” and removed “networkmanager” from the “taskmanger” – Logged off system restarted then went back to YaST2 network settings - overview and edited and set up my wifi adapter and it works. I then started a vmware session and I can use the internet from it and can gain access to my shared Dir [linux-10]. as I pointed out to swerdna the problem had to do with the networkmanager, why? I don’t know, but for now I have things working as I want them. So thanks for pushing in the correct direction.

8

Just now spotted this again. Glad you’re happy.