[ SOLVED ] Network share not working

[Wirezfree]

No problems...
I hope it works for you, any issues, post back, will see if I can help.

[paul1149]

Wow, thanks Wirezfree. I appreciate you taking the time to show me how to do that. This will make it a lot easier to get things up and running. My friend will be able to move her own recordings between her two units, which is what she needs to do, in addition to my own LAN needs around here. This has gone verbatim directly into my own CherryTree file!

BW,
Paul

[Wirezfree]

@paul1149

Sorry for delay... Been a bit busy and I still have a lot of individual notes files, moving them slowly into Cherrytree.
When I first started with Linux I still had multiple XP PC's and had issues get things to work between XP and Linux by name.
Did lots of Googling & Playing in the end I got everything working by name... So these are my notes & comments

When doing fresh install I always install:

Code: [Select]

sudo apt-get install system-config-samba cifs-utils libnss-winbind winbind gvfs-backendssome of these may actually not be required, I just used what I found.
Note: I only use Samba Tool to check configs, I still use LL Network Share method to set things up


Then,
In the smb.conf file, add the following to all PC's "except" one that is either always on, or is used the most.

local master = no

I put it just "below" name resolve order
This avoids the similar situation that you can get in Windows where sometimes when browsing PC's seem to disappear.
It allows 1 PC to maintain a list of all pc's on network

Then edit & modify the following:

Code: [Select]

gksu leafpad /etc/nsswitch.conf
Then change the line:

Code: [Select]

hosts:          files mdns4_minimal [NOTFOUND=return] dns
To this:

Code: [Select]

hosts:          files mdns4_minimal [NOTFOUND=return] wins dns
Then re-boot


I have done many builds & re-builds, I have yet to be unable to use/reference PC's by name.


All my PC's accessible by name, inc VM's.

Code: [Select]


dave@asus-mini-1:~$ ping hp-lappy1
PING hp-lappy1 (10.10.100.161) 56(84) bytes of data.
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=2 ttl=64 time=1.90 ms
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=3 ttl=64 time=4.97 ms
dave@asus-mini-1:~$ ping jetway1
PING jetway1 (10.10.100.180) 56(84) bytes of data.
64 bytes from jetway1 (10.10.100.180): icmp_seq=1 ttl=64 time=2.22 ms
64 bytes from jetway1 (10.10.100.180): icmp_seq=2 ttl=64 time=2.46 ms
dave@asus-mini-1:~$ ping jetway0
PING jetway0 (10.10.100.166) 56(84) bytes of data.
64 bytes from jetway0 (10.10.100.166): icmp_seq=2 ttl=64 time=1.59 ms
64 bytes from jetway0 (10.10.100.166): icmp_seq=3 ttl=64 time=1.38 ms
dave@asus-mini-1:~$ ping sm-ds87
PING sm-ds87 (10.10.100.148) 56(84) bytes of data.
64 bytes from sm-ds87 (10.10.100.148): icmp_seq=1 ttl=64 time=0.144 ms
64 bytes from sm-ds87 (10.10.100.148): icmp_seq=4 ttl=64 time=0.248 ms
dave@asus-mini-1:~$ ping sm-xh97
PING sm-xh97 (10.10.100.140) 56(84) bytes of data.
64 bytes from sm-xh97 (10.10.100.140): icmp_seq=2 ttl=64 time=0.182 ms
64 bytes from sm-xh97 (10.10.100.140): icmp_seq=3 ttl=64 time=0.194 ms
dave@asus-mini-1:~$ ping VM-XP-LIVE

PING VM-XP-LIVE (10.10.100.138) 56(84) bytes of data.
64 bytes from vm-xp-live (10.10.100.138): icmp_seq=1 ttl=128 time=0.104 ms
64 bytes from vm-xp-live (10.10.100.138): icmp_seq=2 ttl=128 time=0.148 ms



GL

[paul1149]

the Help Manual.

This is a good resource. I either was unaware of or had forgotten about it. Perhaps it should go on the desktop.

[paul1149]

Ok, thanks. Again I appreciate your input. Now that I've got the share working, this is not critical, but it's interesting that it's not working here on either machine.

[Wirezfree]

@paul1149
Yes, I can ping all my pc's and vm's by ip or name, also connect to shares by name.

Code: [Select]

dave@asus-mini-1:~$ ping hp-lappy1
PING hp-lappy1 (10.10.100.161) 56(84) bytes of data.
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=1 ttl=64 time=4.23 ms
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=2 ttl=64 time=1.84 ms
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=3 ttl=64 time=1.82 ms
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=4 ttl=64 time=1.76 ms
64 bytes from hp-lappy1 (10.10.100.161): icmp_seq=5 ttl=64 time=2.59 ms
--- hp-lappy1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 1.760/2.452/4.237/0.943 ms

dave@asus-mini-1:~$ ping 10.10.100.161
PING 10.10.100.161 (10.10.100.161) 56(84) bytes of data.
64 bytes from 10.10.100.161: icmp_seq=1 ttl=64 time=88.6 ms
64 bytes from 10.10.100.161: icmp_seq=2 ttl=64 time=2.58 ms
64 bytes from 10.10.100.161: icmp_seq=3 ttl=64 time=1.75 ms
64 bytes from 10.10.100.161: icmp_seq=4 ttl=64 time=1.82 ms
64 bytes from 10.10.100.161: icmp_seq=5 ttl=64 time=1.93 ms
--- 10.10.100.161 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.754/19.340/88.606/34.634 ms



dave@asus-mini-1:~$ ping jetway0
PING jetway0 (10.10.100.166) 56(84) bytes of data.
64 bytes from jetway0 (10.10.100.166): icmp_seq=1 ttl=64 time=2.02 ms
64 bytes from jetway0 (10.10.100.166): icmp_seq=2 ttl=64 time=1.07 ms
64 bytes from jetway0 (10.10.100.166): icmp_seq=3 ttl=64 time=0.971 ms
64 bytes from jetway0 (10.10.100.166): icmp_seq=4 ttl=64 time=0.990 ms
64 bytes from jetway0 (10.10.100.166): icmp_seq=5 ttl=64 time=3.13 ms
--- jetway0 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 0.971/1.639/3.139/0.848 ms

I have been working late. I will post more later, if nobody else chips in.

[Jerry]

We do not recommend using a configurator, this was ultimately the cause of the issue you were having. We already provide a simple way to set Network Shares in the Help Manual.

[paul1149]

Nailed  it. I found the smbusers.conf file to contain something like this:

<linux>="<linux>"<joyce>="<joyce>"

I've run into this before, but had forgotten about it. It seems to be a flaw of the Samba Configurator. It apparently doesn't see the original "linux" entry and therefore doesn't start a new line. So I changed it to

<linux>="<linux>"
<joyce>="<joyce>"

Then with a restart of the smbd and nmbd services, I was able to log in.
Then I navigated to the other test share, and during the login process was greeted by the keyring prompt, which I've never been so happy to see. On reboot the logins were proved persistent.

Then I tried accessing the shares from other LL and Win8 units, and all went well.

I am getting quite a bit of sluggishness in accessing the LAN and shares, and have been using F5 a lot to refresh the view. Also, samba doesn't seem to auto-poll the remote shares at all. The Refresh is necessary to see changes. But this is another issue.

Thanks for the input!

[paul1149]

ping lappy also produces "unknown host". Since I changed lappy to Dell-1545 I haven't seen it on the LAN in Thunar, over many reboots, so I think that part of it is set.

The more I think about this, the machine's inability to access its own share is at the heart of the problem.

I just tested the problem machine, and it is able to access a share I have on my main LL unit.

[firenice03]

Have you tried pinging "lappy" ?? maybe the netbios hasn't saved?? or its cached., where the name dell-1545 hasn't registered....
Now that its been a few hours it may have updated.

lappy is the LL default netbios, took me by surprise 1st few times I saw it when I look at the network and seen lappy and not the machine

[paul1149]

Can anyone here ping a LAN machine by its hostname on LL? This seems to be a problem in Linux. And the problem machine can't do it either. I tried installing mdns, an adaptation of Bonjour, to no avail. Meanwhile the Win8 machine has no problem in this regard, probably using WINS.

[paul1149]

A Win8 machine can ping the dell-1545 hostname, but also cannot log into the machine. Complicated.

[paul1149]

Hi,

I appreciate your input.

In Samba Configurator, the LL user has been a Samba user as well. I did have to enter that manually. And the shares are set to specific users, with the current and only LL user on that machine checked.

Strange, from my LL PC I can ping the local IP, but not the hostname, of the problem machine. I'm attaching a pic showing that, plus the fact that Thunar sees the shares. There's got to be something to the fact that even the problem machine has to log on to its own share. I've never heard of that before.

[Wirezfree]

Hi,

Just some quick checks.

Open Samba Conf tool.
Goto preferences, Samba Users, Is your LL user name on list.??

Then
Highlight the share, and Goto File > Properties
Check Access Tab, Is it set to "Only allow access for specific users" or "All"

Another quick check:
From your PC, try to ping the other pc by ip-address and hostname,
you can get these via Lite Control on other PC, 1st page

Code: [Select]

ping local-ip-address
and

Code: [Select]

ping hostname

[paul1149]

I've corrected that netbios name to match the server string, and checked it against the machine's hostname, and rebooted. There is no firewall on the machine in question. Very puzzling.