LinuxQuestions.org - Cannot connect to my Snake OS NAS with Ubuntu 14.04

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - Cannot connect to my Snake OS NAS with Ubuntu 14.04 (https://www.linuxquestions.org/questions/linux-networking-3/cannot-connect-to-my-snake-os-nas-with-ubuntu-14-04-a-4175504266/)

Cannot connect to my Snake OS NAS with Ubuntu 14.04

Have a strange problem with my new install of Ubuntu 14.04, firstly I cannot browse my (wifi) network through the file system, even though it shows the Windows Network and then MSHOME (the correct network designation), MSHOME is empty. I can link to the different servers on the network by means of Gigolo except for one: a little NAS that runs Snake OS (a cut-down Linux variant) which has a hard drive that holds all the update and transfer data for the network and is the hub of my network. Try as I may I cannot connect to this even though two other Windows XP machines and one notebook that runs Salix Linux OS have no such problems; and my previous install on the same machine Ubuntu 13.10 was fine. Any suggestions for a fix or a work-around?

You need to post some useful information.

Can you ping the NAS form the failing system?

Have you updated the /etc/hosts file on the failing system?

Open a command prompt, run the command 'ifconfig wlan0' ( wlan0 I'm guessing that is the name of your wifi card ) put the correct name in if its not waln0. Post the results here.

Are you using static IP addresses or are you using DHCP?

Are all the devices on the same sub-net?

Thanks for the response.
Here are what I know or have found.

Quote:

Originally Posted by camorri (Post 5166654)

Can you ping the NAS form the failing system?

Yes, under its IP address 192.168.1.3, ping time is under 4 ms.

Quote:

Have you updated the /etc/hosts file on the failing system?

No, am pretty new to all this, had no idea about it. Only fiddled with smb.conf.
This is the contents of that file: (are those IP addresses correct?)

Code:

127.0.0.1        localhost

127.0.1.1        Hermes-III



# The following lines are desirable for IPv6 capable hosts

::1    ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

Quote:

Open a command prompt, run the command 'ifconfig wlan0' ( wlan0 I'm guessing that is the name of your wifi card ) put the correct name in if its not waln0. Post the results here.

Code:

paul@Hermes-III:~$ ifconfig wlan0

wlan0    Link encap:Ethernet  HWaddr 48:02:2a:f5:02:9e  

          inet addr:192.168.1.7  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::4a02:2aff:fef5:29e/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:237 errors:0 dropped:0 overruns:0 frame:0

          TX packets:174 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:24688 (24.6 KB)  TX bytes:23885 (23.8 KB)



paul@Hermes-III:~$

Quote:

Are you using static IP addresses or are you using DHCP?

I am using DHCP in the router and have reserved the IP addresses of most - but not all - of the devices that connect to it.

Quote:

Are all the devices on the same sub-net?

I have up to 11 devices connected to my network. Three of these are desktops, two with Windows XP and one with Linux, and two Notebooks one with Linux and one with Windows XP, and two printers. All the computers are on the Windows Network "MSHOME" and the printers are on "Workgroup". The actual network is called "merlin" and covers all devices.
Paul.

Most things look normal. Thank-you for your detailed answers.

First of all, you might benefit from updating the 'hosts' file on each system, unless you are running your own DNS server. On a linux system you will find the file in the /etc directory. This file is a simple text file listing host names and IP addresses. It is used by the kernel to route packets if the DNS service does not know where the target IP address is. It saves the user from needing to know IP addresses. Depending how your windoze networking is configured, it may be using names to find targets in your network.

The host file. Here are few lines from mine, as an example.

Quote:

127.0.0.1 localhost
192.168.1.26 duelie.cliffshome.org duelie.cliffshome.org
192.168.1.22 Presto presto
192.168.1.23 snail Snail

You can use IPv4 or IPv6 addresses in the file. The format is:

Quote:

IP_address canonical_hostname [aliases...]

You have the same file on any windoze system. If you do a 'find' on windoze, you should be able to locate it.

Can you tell us what kind of program 'Gigolo' is? Not at all familiar with it.

Since this seems to be a samba problem, can you post the configuration for your server?

I have a NAS, I connect to it with ssh, and configure it. The original code was set up for configuration through a web browser. I found ssh to be much more effective at managing the NAS. Can you connect to the NAS with ssh, or telnet?

IMHO it is a client not server problem.

You can see shares on every computer on the network except for the NAS box?
Have you tried any other means besides Gigolo to view shares on the NAS box? Nautilus, or via console utilities?

Try the following command. (Just press enter at the password prompt) You should see the NAS shares.
smbclient -L NAS-IP-address

Thanks for all that.
That is correct, I can see and mount all other shares except the Snake OS NAS box.
Anyhow, I tried a few things.
Included the IP addresses into the "hosts" file as suggested above, although I only entered the host's name once unlike the example, because I could not understand as to why this was entered twice and in that case what the correct format should be. I used the network names that came up on a Windows Network Scanner on my Windows XP machine to ensure I had the syntax and capitalization right.
Anyhow, this appear to have changed nothing.
I also did an "smbclient -I--192.168.1.3" to see if the little NAS (server gwydion) could be seen by Samba and that seemed happy. No timeouts, nothing.
Then I tried to connect and I got this:

Code:

Failed to mount Windows share: connection timed out

I just wonder whether it could be a timing problem and the shares of the little NAS don't mount because Samba does not give it enough time to do so.
I am still a little baffled by it all.
I have provided below my "smb.conf" file with the comments removed to make it a little less unwieldy, in case that harbors the problem and needs changing:

Code:

#### Debugging/Accounting ####

log file = /var/log/samba/log.%m

max log size = 1000

syslog = 0

panic action = /usr/share/samba/panic-action %d



####### Authentication #######

server role = standalone server

passdb backend = tdbsam

obey pam restrictions = yes

unix password sync = yes

passwd program = /usr/bin/passwd %u

passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

pam password change = yes

map to guest = bad user



########## Domains ###########

;  logon path = \\%N\profiles\%U

;  logon drive = H:

;  logon script = logon.cmd

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

; add group script = /usr/sbin/addgroup --force-badname %g



############ Misc ############

;  include = /home/samba/etc/smb.conf.%m

;  idmap uid = 10000-20000

;  idmap gid = 10000-20000

;  template shell = /bin/bash

;  usershare max shares = 100

usershare allow guests = yes



#======================= Share Definitions =======================

;  [homes]

;  comment = Home Directories 

;  browseable = yes

read only = no

create mask = 0775

;  directory mask = 0700

;  valid users = %S



;[netlogon]

;  comment = Network Logon Service

;  path = /home/samba/netlogon

;  guest ok = yes

;  read only = yes



;[profiles]

;  comment = Users profiles

;  path = /home/samba/profiles

;  guest ok = no

;  browseable = no

;  create mask = 0600

;  directory mask = 0700



[printers]

comment = All Printers

browseable = yes

path = /var/spool/samba

printable = yes

guest ok = no

read only = yes

create mask = 0700



[print$]

comment = Printer Drivers

path = /var/lib/samba/printers

browseable = yes

read only = yes

guest ok = no

;  write list = root, @lpadmin



[Downloads]

path = /home/paul/Downloads

create mask = 0775

browseable = yes

writable = yes

valid users = paul

Thanks in advance,
Paul.

Quote:

Included the IP addresses into the "hosts" file as suggested above, although I only entered the host's name once unlike the example, because I could not understand as to why this was entered twice and in that case what the correct format should be.

Let me clear up this point.

As far as the format, it is a plain text file, up to three columns per entry. The first column, is the IP address of one system. Next is the domain name example duelie.cliffshome.org and the last column is an alias. It can be a shorter name you wish to refer to the machine by, for example 'duelie'. In the case of the domain name, a short name also works just fine. You do not need to provide an alias though.

I'm no expert when it comes to samba. That said, it looks like you are trying to implement pam. I have never used it, so I don't know anything about it.

There are some things you can try. First of all, here is the way I config my servers.

Quote:

[global]
workgroup = CLIFFSHOME
server string = Samba Server %v
map to guest = Bad User
log level = 3
log file = /var/log/samba/%m.log
max log size = 50
printcap cache time = 60
printcap name = cups
os level = 65
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
ldap ssl = no
idmap config * : backend = tdb

Try adding these lines :

Quote:

preferred master = Yes
domain master = Yes

in the global section. I found they helped me 'see' the shares from other systems. What ever you use for a workgroup name is fine, as long as all systems use the same name.

Possibly others will be able to spot another thing you can try? Hope this helps.

Quote:

I also did an "smbclient -I--192.168.1.3" to see if the little NAS (server gwydion) could be seen by Samba and that seemed happy. No timeouts, nothing.

What does happy mean?
You should see something similar to

Quote:

Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba ]

Sharename Type Comment
--------- ---- -------
my_shares disk

Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba ]

Server Comment
--------- -------
READYSHARE readyshare
SERVER Samba Server Version

Workgroup Master
--------- -------
WORKGROUP SERVER

Some progress but still no NAS access.

Hello camorri, your suggested additions to my smb.conf did work, I can now see the hosts under the Ubuntu file manager "Browse Network", which I could not before; although the little NAS is also shown there, I cannot open it, it still times out; but I can open all the other hosts and look at and open their shares, copy files, etc. So that is a little progress in this puzzling saga.
I have listed the "hosts" file here, I hope this is now correct; "merlin" is the name of the network.

Code:

127.0.0.1        localhost

127.0.1.1        merlin        Hermes-III

192.168.1.2        merlin        magus.Home

192.168.1.3        merlin        GWYDION

192.168.1.4        merlin        DELL-D530

192.168.1.5        merlin        SORCERER-II



# The following lines are desirable for IPv6 capable hosts

::1    ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

Here is also the modified smb.conf, just in case the problem still resides there:

Code:

#======================= Global Settings =======================



[global]

workgroup = MSHOME

name resolve order = wins host lmhosts bcast

preferred master = Yes

domain master = Yes

server string = %h server (Samba, Ubuntu)

wins support = Yes

;  wins server = w.x.y.z

dns proxy = No



#### Networking ####

;  interfaces = 127.0.0.0/8 eth0

;  bind interfaces only = yes



#### Debugging/Accounting ####

log file = /var/log/samba/log.%m

max log size = 1000

syslog = 0

panic action = /usr/share/samba/panic-action %d



####### Authentication #######

server role = standalone server

passdb backend = tdbsam

obey pam restrictions = Yes

unix password sync = Yes

passwd program = /usr/bin/passwd %u

passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

pam password change = Yes

map to guest = bad user



########## Domains ###########

;  logon path = \\%N\profiles\%U

;  logon drive = H:

;  logon script = logon.cmd

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

; add group script = /usr/sbin/addgroup --force-badname %g



############ Misc ############

;  include = /home/samba/etc/smb.conf.%m

;  idmap uid = 10000-20000

;  idmap gid = 10000-20000

;  template shell = /bin/bash

;  usershare max shares = 100

usershare allow guests = yes



#======================= Share Definitions =======================

;  [homes]

;  comment = Home Directories 

;  browseable = yes

read only = no

create mask = 0775

;  directory mask = 0700

;  valid users = %S



;[netlogon]

;  comment = Network Logon Service

;  path = /home/samba/netlogon

;  guest ok = yes

;  read only = yes



;[profiles]

;  comment = Users profiles

;  path = /home/samba/profiles

;  guest ok = no

;  browseable = no

;  create mask = 0600

;  directory mask = 0700



[printers]

comment = All Printers

browseable = Yes

path = /var/spool/samba

printable = Yes

guest ok = No

read only = Yes

create mask = 0700



[print$]

comment = Printer Drivers

path = /var/lib/samba/printers

browseable = Yes

read only = Yes

guest ok = No

;  write list = root, @lpadmin



[Downloads]

path = /home/paul/Downloads

create mask = 0775

browseable = Yes

writable = Yes

valid users = paul

Thanks so far, Paul.

Hello michaelk

Quote:

What does happy mean?
You should see something similar to

I saw nothing similar to that, the line just went down one and as I got no errors I thought that was it.
Obviously there is a problem. I still wonder whether it is a timing problem (timing set too short) that prevents the shares from being mounted. But of course I am only guessing and at any rate I would not have a clue how to fix this.
So any help would be greatly appreciated.
As you can see from my other reply, we made some progress but being able to connect to the little NAS remains elusive.
Thanking you, Paul.

Quote:

I have listed the "hosts" file here, I hope this is now correct; "merlin" is the name of the network.
Code:

127.0.0.1 localhost
127.0.1.1 merlin Hermes-III
192.168.1.2 merlin magus.Home
192.168.1.3 merlin GWYDION
192.168.1.4 merlin DELL-D530
192.168.1.5 merlin SORCERER-II

No, this is not correct. The second field is the same for all your entries.

The use of the /etc/hosts file is to simplify the need to use IP addresses when the DNS ( Domain Name Server ) does not know the IP addresses of your network. Each entry has to be unique.

First of all, from a terminal, to determine what hostname you have set, type hostname and press enter. The system will return the value you have set for hostname. The value returned should be in column 2. Right now, you have several set to merlin.

If you typed 'ping merlin' your kernel wouldn't know which merlin to ping.

The names should be meaningful to you, and who ever uses your network.

What would work is something like this:

Quote:

192.168.1.2 magus.Home
192.168.1.3 GWYDION
192.168.1.4 DELL-D530

These names, if they match the results by checking each hostname on each system, will work. The simple test is to try to ping a system using just the name in the /etc/hosts file. Example 'ping GWYDION' should work the same as typing 'ping 192.168.1.3'.

The third column is optional. An alias is just another nick name for the system. If the real hostname of a system is GWYDION, and you find that too difficult to remember, adding an alias like 'dion' would work. Then the line would look like:

Quote:

192.168.1.3 GWYDION dion

Hope that clarifies the hosts file.

Corect Hosts file?

Quote:

Originally Posted by camorri (Post 5168329)

My misunderstanding.
So here is the - I hope now correct - code:

Code:

127.0.0.1 localhost

127.0.1.1 Hermes-III

192.168.1.2 magus.Home magus

192.168.1.3 GWYDION gwydion

192.168.1.4 DELL-D530 dell

192.168.1.5 SORCERER-II sorcerer-II



# The following lines are desirable for IPv6 capable hosts

::1    ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

Will try this and get back.
Just realized I missed your previous question:

Quote:

Can you tell us what kind of program 'Gigolo' is? Not at all familiar with it.

Gigolo is a program that mounts shares automatically, it can be configured to run at bootup. It is very handy in setting automated access to parts of the network. Gigolo runs fine now and mounts each share, except for the little NAS on 192.168.1.3, that remains elusive.
Thanks, Paul.

Just a quick added note:
I have activated the inbuilt FTP server in the little NAS and found that I could mount and access this fine in Ubuntu 14.04
I can also use Firefox to browse the NAS by means of HTTP.
But any attempt to browse it from the file manager still comes up with:

Code:

Failed to retrieve share list from server; connection timed out

As my NAS is the hub of my network, I am still hoping that this last problem can be resolved, so if anyone has any suggestions............

This is a problem in the samba server config. First thing I would do, is make a very simple config file. Get that working, and then add what else you need.

I see you have pam in there. That the first thing I would get rid of. Do you really need that on a home network?

Quote:

Originally Posted by camorri (Post 5169291)

This is a problem in the samba server config. First thing I would do, is make a very simple config file. Get that working, and then add what else you need.

I have replaced smb.conf with the original unembellished smb.conf file and just modified the information to suit my computer. As I am hardly an expert in all this, I would not have the foggiest idea as to what I should leave and can remove from the smb.conf file.
But as it stands, we have made some progress.
1. I can now browse all servers on my network from the Ubuntu file system, where before they did not show up. The exception of course is the little NAS (gwydion) which I can see but not open; although FTP from the Ubuntu machine works fine and I can see and copy stuff from the FTP directory to my Ubuntu machine on the little NAS. But I cannot access the NAS from my file system, and thus cannot mount any of its directories. I have changed the setup of the shares in the NAS, but that made no difference, so I doubt the NAS setup is the problem, although its tendency to take time to open may be a problem; but I am only guessing here.
2. Directories on other servers (apart from the NAS) will now mount automatically with Gigolo at boot, without error messages.
3. But some problems remain, as can be seen from the errors shown in the output of smbtree -d3:

Code:

paul@Hermes-III:~$ smbtree -d3

lp_load_ex: refreshing parameters

Initialising global parameters

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)

params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"

Processing section "[global]"

added interface wlan0 ip=192.168.1.7 bcast=192.168.1.255 netmask=255.255.255.0

Enter paul's password: 

tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied

name_resolve_bcast: Attempting broadcast lookup for name MSHOME<0x1d>

Got a positive name query response from 192.168.1.7 ( 192.168.1.7 )

Connecting to 192.168.1.7 at port 445

Doing spnego session setup (blob length=74)

got OID=1.3.6.1.4.1.311.2.2.10

got principal=not_defined_in_RFC4178@please_ignore

Got challenge flags:

Got NTLMSSP neg_flags=0x608a8215

NTLMSSP: Set final flags:

Got NTLMSSP neg_flags=0x60088215

NTLMSSP Sign/Seal - Initialising with flags:

Got NTLMSSP neg_flags=0x60088215

SPNEGO login failed: Logon failure

MSHOME

name_resolve_bcast: Attempting broadcast lookup for name MSHOME<0x1d>

Got a positive name query response from 192.168.1.7 ( 192.168.1.7 )

Connecting to 192.168.1.7 at port 445

Doing spnego session setup (blob length=74)

got OID=1.3.6.1.4.1.311.2.2.10

got principal=not_defined_in_RFC4178@please_ignore

Got challenge flags:

Got NTLMSSP neg_flags=0x608a8215

NTLMSSP: Set final flags:

Got NTLMSSP neg_flags=0x60088215

NTLMSSP Sign/Seal - Initialising with flags:

Got NTLMSSP neg_flags=0x60088215

SPNEGO login failed: Logon failure

        \\MAGUS                          College Desktop

name_resolve_bcast: Attempting broadcast lookup for name MAGUS<0x20>

Got a positive name query response from 192.168.1.2 ( 192.168.1.2 192.168.50.1 )

Connecting to 192.168.1.2 at port 445

Connecting to 192.168.1.2 at port 139

samba_tevent: EPOLL_CTL_DEL EBADF for fde[0xb7d831d0] mpx_fde[(nil)] fd[12] - disabling

Doing spnego session setup (blob length=0)

server didn't supply a full spnego negprot

Got challenge flags:

Got NTLMSSP neg_flags=0x628a8215

NTLMSSP: Set final flags:

Got NTLMSSP neg_flags=0x60088215

NTLMSSP Sign/Seal - Initialising with flags:

Got NTLMSSP neg_flags=0x60088215

                \\MAGUS\HPLaserjn              HP LaserJet M2727 MFP Series PCL 6

                \\MAGUS\Temp                  

                \\MAGUS\Printer4              Epson LQ-500

                \\MAGUS\DOWNLOAD              

                \\MAGUS\LANIERLP              Lanier SP C811DN PCL 5c

                \\MAGUS\Multimedia            

                \\MAGUS\My_Documents          

                \\MAGUS\Deskjet930c            HP DeskJet 930C

                \\MAGUS\SharedDocs            

                \\MAGUS\print$                Printer Drivers

                \\MAGUS\IPC$                  Remote IPC

                \\MAGUS\My Documents          

                \\MAGUS\CD_FILES              

        \\HERMES-III                    Hermes-III server (Samba, Ubuntu)

name_resolve_bcast: Attempting broadcast lookup for name HERMES-III<0x20>

Got a positive name query response from 192.168.1.7 ( 192.168.1.7 )

Connecting to 192.168.1.7 at port 445

Doing spnego session setup (blob length=74)

got OID=1.3.6.1.4.1.311.2.2.10

got principal=not_defined_in_RFC4178@please_ignore

Got challenge flags:

Got NTLMSSP neg_flags=0x608a8215

NTLMSSP: Set final flags:

Got NTLMSSP neg_flags=0x60088215

NTLMSSP Sign/Seal - Initialising with flags:

Got NTLMSSP neg_flags=0x60088215

SPNEGO login failed: Logon failure

                \\HERMES-III\Hewlett-Packard-HP-LaserJet-M2727nf-MFP        Hewlett-Packard HP LaserJet M2727nf MFP

                \\HERMES-III\Lexmark-E260dn        Lexmark E260dn

                \\HERMES-III\LANIER-LP440c-SP-C811DNCMD:PS        LANIER LP440c/SP C811DNCMD:PS

                \\HERMES-III\HP-Deskjet-930c        HP Deskjet 930c

                \\HERMES-III\print$                Printer Drivers

                \\HERMES-III\Downloads              

                \\HERMES-III\IPC$                  IPC Service (Hermes-III server (Samba, Ubuntu))

        \\GWYDION                        gwydion

name_resolve_bcast: Attempting broadcast lookup for name GWYDION<0x20>

Got a positive name query response from 192.168.1.3 ( 192.168.1.3 )

Connecting to 192.168.1.3 at port 445

Connecting to 192.168.1.3 at port 139

convert_string_talloc: Conversion error: Incomplete multibyte sequence()

Conversion error: Incomplete multibyte sequence()

paul@Hermes-III:~$

Quote:

I see you have pam in there. That the first thing I would get rid of. Do you really need that on a home network?

I am not sure what "pam" is, but as you can see from the following listing of my smb.conf, this has been disabled as suggested, Unfortunately this seemed to make no difference.

Code:

#======================= Global Settings =======================



[global]



## Browsing/Identification ###



# Change this to the workgroup/NT-domain name your Samba server will part of

  workgroup = MSHOME

  netbios name = Hermes-III

  name resolve order = bcast host lmhosts wins

  preferred master = yes

  domain master = yes

  client lanman auth = yes

  lanman auth = yes

  server string = %h server (Samba, Ubuntu)

;  wins server = w.x.y.z

  dns proxy = no



#### Networking ####



;  interfaces = 127.0.0.0/8 eth0

;  bind interfaces only = yes



#### Debugging/Accounting ####



  log file = /var/log/samba/log.%m

  max log size = 1000

  syslog = 0

  panic action = /usr/share/samba/panic-action %d





####### Authentication #######



  server role = standalone server

  passdb backend = tdbsam

  encrypt passwords = yes

  obey pam restrictions = no

  unix password sync = yes

  passwd program = /usr/bin/passwd %u

  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

;  pam password change = yes

  map to guest = bad user



########## Domains ###########



;  logon path = \\%N\profiles\%U

;  logon drive = H:

;  logon script = logon.cmd

;  add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

;  add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

;  add group script = /usr/sbin/addgroup --force-badname %g



############ Misc ############



;  include = /home/samba/etc/smb.conf.%m

;  idmap uid = 10000-20000

;  idmap gid = 10000-20000

;  template shell = /bin/bash

;  usershare max shares = 100

  usershare allow guests = yes



#======================= Share Definitions =======================



;[homes]

;  comment = Home Directories

;  browseable = no

;  read only = yes

;  create mask = 0700

;  directory mask = 0700

;  valid users = %S



;[netlogon]

;  comment = Network Logon Service

;  path = /home/samba/netlogon

;  guest ok = yes

;  read only = yes



;[profiles]

;  comment = Users profiles

;  path = /home/samba/profiles

;  guest ok = no

;  browseable = no

;  create mask = 0600

;  directory mask = 0700



[printers]

  comment = All Printers

  browseable = no

  path = /var/spool/samba

  printable = yes

  guest ok = no

  read only = yes

  create mask = 0700



[print$]

  comment = Printer Drivers

  path = /var/lib/samba/printers

  browseable = yes

  read only = yes

  guest ok = no

;  write list = root, @lpadmin



[Downloads]

path = /home/paul/Downloads

create mask = 0775

browseable = Yes

writable = Yes

valid users = paul

As I said, it is probably my lack of understanding that is a part of the problem here, so I am afraid I will need some concise guidance in order to solve this knotty problem. Regards, Paul.

The posted smb.conf file is just for configuring the samba server/shares on Hermes-III and does not have any bearing on connecting to the NAS. Have you tried to manually mount a NAS share?

I agree with bab1 in your thread on the ubuntu forum it could be a bug in the samba 4 client and whatever version of samba is running on the NAS.

Quote:

Originally Posted by michaelk (Post 5169690)

The posted smb.conf file is just for configuring the samba server/shares on Hermes-III and does not have any bearing on connecting to the NAS. Have you tried to manually mount a NAS share?
I agree with bab1 in your thread on the ubuntu forum it could be a bug in the samba 4 client and whatever version of samba is running on the NAS.

Yes, I have tried that numerous times, from the file manager and by means of Gigolo, without success.
I have just found out the the Ubuntu firewall is also part of the problem.
One post suggested that this should be disabled:

Code:

sudo ufw disable

But that seems to change nothing as far as access to the NAS is concerned.
But when I enable it again

Code:

sudo ufw enable

I can no longer see or browse any of my shares in the Ubuntu file manager.
Is there a way to register the network with the firewall?
Paul.

Just a follow up, have "excluded" the ports from the Ubuntu Fire Wall (thanks to info in someone else's post) and all appears to be running OK now; I again have access to all my network shares excepting those on the little NAS.
Just as an aside, as I understand it the NAS is running a cut-down version of Samba. I just wonder whether the problem is related to some protocol changes or restrictions from Ubuntu 13.10, which had no problems linking to the shares of the little NAS, and Ubuntu 14.04 which is the version giving me all these problems. Paul.

Cannot connect to my Snake OS NAS with Ubuntu 14.04

The flow of TCP is processed at a pace slower compared to the accuracy of the net. TCP offload engine solves this issue through getting rid of the burden or offloading from the I/O subsystem as well as the microprocessor.

Quote:

Originally Posted by johnsoto (Post 5169770)

OK.... I am not sure what this means, how that explains the problem I am experiencing and how this can be applied for a potential solution. So please, any help in the form of explanation will be appreciated. Paul.

Just a follow up.
I have set up basic FTP via the "Snake OS" operating system of the little NAS (WLX-652 gwydion). This is mounted at boot by Gigolo on the Ubuntu machine and works to a fashion as it allows me to update files from the network by FTP download. But it is one way only and hardly ideal.
I also noted the setup of the little NAS and have listed this below in case the problem lies there.

Code:

HTTP Web Admin Port: 80

DNNS - not running

FTP - running

SFTP/SSHD - SSH Server Port: 22

Samba - running - Password only or anonymous access

Telnet - not running

Web Server port: 8081

Opkg - enabled

If anyone can see any problems, incompatibilities or potential conflicts with Ubuntu 14.04 Samba please let me know; in which case some directions on how to solve this would be greatly appreciated. Thanks, Paul.

Has anyone figured this out? I have the same device and same problem. Not sure if it is a permissions issue. I am somewhat new to Linux as well. I have done all the above recommended, which did help with getting my other computer to show up in the browse networks. And my NAS device shows up. But I get the same timeout message. And when I do the smbclient -L 192.168.1.106 I get:
Conversion error: Incomplete multibyte sequence()
protocol negotiation failed: NT_STATUS_INVALID_PARAMETER
It asks me for my system password first.
I can connect to my NAS via FTP, but like paul1945 mentioned it does not allow for the update of the files? Any ideas? Thanks.

anonku,

I recommend you open a new thread. This is an old thread, and is unlikely to draw much attention.

It would help if you posted more details about the NAS you have, and how its configured.

Quote:

I can connect to my NAS via FTP, but like paul1945 mentioned it does not allow for the update of the files? Any ideas?

Have you created users on the NAS for ftp and windows networking?

No resolution to Samba but FTP works fine.

I have not been able to come up with a resolution to this problem, even though I have tried many different approaches. I had also posted the problem on the Ubuntu Forum, but no-one there seemed to be able to come up with an answer. The suggestion was made that the little NAS has a cut-down version of Samba that is not compatible with the later versions of Samba (probably relates to security features lacking on Samba of the NAS).
I therefore use FTP which works fine and with some help have been able to set it up so it works both ways and therefore fulfills my needs the same way Samba would have done.
If you want the details of setting up access via FTP on the NAS, I have kept a copy of the instructions, please let me know. Paul.

think I will just make due

Thanks Paul for the reply. I have the FTP setup as the work around as well. Thanks for the info, but perhaps will just make due. It is only for home use anyhow. Thanks for all your work and to all others on this issue. Might be time for a NAS upgrade.