LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Network share not working
#1
I'm stumped on this one. I'm trying to set up a network share on a friend's laptop. I've downloaded the Samba configurator. I created a folder under the user hierarchy, and I pointed the configurator to it as a share. It is writable and requires user credentials to log in.


The share shows up on my own LL machine, but I cannot log into it.


What's more, if I navigate through Browse Network on my friend's machine and go to the share in question, to access the folder I have to navigate the login dialog as if I were on an external machine. And the login fails just as it does on my own machine. It's as if the share were on a different machine. This user uses a password to log into the machine.


Something very basic is wrong here, but I fail to see what. I'm attaching the smb.conf file.
[img height=600 width=450]http://i.imgur.com/JtawoNP.jpg[/img]
Reply
#2
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.
Reply
#3
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:
ping local-ip-address

and
Code:
ping hostname
Upgrades WIP 2.6 to 2.8 - (6 X 2.6 to 2.8 completed on: 20/02/16 All O.K )
Linux Lite 3.0 Humming on a ASRock N3070 Mobo ~ btrfs RAID 10 Install on 4 Disks Smile

Computers Early days:
ZX Spectrum(1982) , HP-150 MS-DOS(1983) , Amstrad CPC464(1984) ,  BBC Micro B+64(1985) , My First PC HP-Vectra(1987)
Reply
#4
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.

[Image: BMiMHIk.png]
Reply
#5
A Win8 machine can ping the dell-1545 hostname, but also cannot log into the machine. Complicated.
Reply
#6
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.
Reply
#7
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 Smile
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
Reply
#8
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.
Reply
#9
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!
Reply
#10
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.
Reply


Forum Jump:


Users browsing this thread: 9 Guest(s)