no connection between omv and w10/w7/android + no e-mail notification possible

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • no connection between omv and w10/w7/android + no e-mail notification possible

      Hello,
      I just installed my new NAS Hardware (ASROCK J4205; 8GB RAM; m2toUSB for system; 2x 10GB WD RED for Data).
      OMV was choosen because of the active forum, which I now need (unluckily) within the first days.

      I installed omv with the help of the "how to" video (github.com/OpenMediaVault-Plugin-Developers/videos) and the guidance of technikaffe (technikaffe.de/anleitung-255-i…iavault_inkl._wake_on_lan).
      Due to the issue of debian 8 I had to use the backport kernel 4.9 for my cpu-speed, which I did at first while my first login via ssh.
      After that I continued the guidance:
      - the omv gets the IP via DHCP (set a fix IP in my router)
      - installed all possible updates via omv web interface (omv 3.0.88)
      - installed the extensions I need (USB-Backup; UPS-Tools; Anti-Virus; Auto-Shutdown )
      - installed the omv-extra extensions
      - tried to configure the notifications => it was not possible to let omv send me a notification email - skipped at first
      - installed the two hard-drives to build up the raid
      - build up a raid 1 with my two hard drives
      - set up a brts file system
      - configured SMART
      - configured hard drive powermanagement
      - configured auto-shutdown
      - configured smb/cifs like in the guidance of technikaffe.

      Unluckily the omv was not shown up at w7/w10 within the private networks settings and even the try to look up for the shares via IP (\\192.168.69.50) was rejected, the same as the try to connect the share (with input of the correct user-name and password).
      Ping inbetween the w7/w10 maschines and the omv are possible, login via ssh and scp are possible, too.
      I tried to set up and ftp-connection without any success.
      I deactivated the firewall in windows and the anti-virus on the omv without any success.
      I updated the kernel to 4.12 without any affect to this issue.
      I set the log-mode to debug in the smb-config, but no log-file is created, thus no connection is established.

      I do not know, if there is a link between the problems about the notification and the refuse of connection between android phone (with filecommander)/W10/W7 and omv.
      Did I made any (big) mistake with my configuration? - I think I will have to reinstall omv, but first of all I want to know what is wrong with my actuall configuration.

      best regards
      Björn

      Here are some configs and outputs: Do you need anything else?

      My Samba-Config-File:

      Source Code

      1. #======================= Global Settings =======================
      2. [global]
      3. workgroup = WORKGROUP
      4. server string = %h server
      5. dns proxy = no
      6. log level = 10
      7. syslog = 10
      8. log file = /var/log/samba/log.%m
      9. max log size = 1000
      10. syslog only = yes
      11. panic action = /usr/share/samba/panic-action %d
      12. encrypt passwords = true
      13. passdb backend = tdbsam
      14. obey pam restrictions = no
      15. unix password sync = no
      16. passwd program = /usr/bin/passwd %u
      17. passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
      18. pam password change = yes
      19. socket options = TCP_NODELAY IPTOS_LOWDELAY
      20. guest account = nobody
      21. load printers = no
      22. disable spoolss = yes
      23. printing = bsd
      24. printcap name = /dev/null
      25. unix extensions = yes
      26. wide links = no
      27. create mask = 0777
      28. directory mask = 0777
      29. map to guest = Bad User
      30. use sendfile = yes
      31. aio read size = 16384
      32. aio write size = 16384
      33. null passwords = no
      34. local master = no
      35. time server = no
      36. wins support = no
      37. #======================= Share Definitions =======================
      38. [test3]
      39. path = /srv/dev-disk-by-id-md-name-bjoern-RAID1/test3
      40. guest ok = no
      41. read only = no
      42. browseable = yes
      43. inherit acls = yes
      44. inherit permissions = no
      45. ea support = no
      46. store dos attributes = no
      47. vfs objects =
      48. printable = no
      49. create mask = 0664
      50. force create mode = 0664
      51. directory mask = 0775
      52. force directory mode = 0775
      53. hide special files = yes
      54. follow symlinks = yes
      55. hide dot files = yes
      56. valid users = "bjoern"
      57. invalid users =
      58. read list =
      59. write list = "bjoern"
      60. [test2]
      61. path = /srv/dev-disk-by-id-md-name-bjoern-RAID1/test2
      62. guest ok = no
      63. read only = no
      64. browseable = yes
      65. inherit acls = yes
      66. inherit permissions = no
      67. ea support = no
      68. store dos attributes = no
      69. vfs objects =
      70. printable = no
      71. create mask = 0664
      72. force create mode = 0664
      73. directory mask = 0775
      74. force directory mode = 0775
      75. hide special files = yes
      76. follow symlinks = yes
      77. hide dot files = yes
      78. valid users = "bjoern"
      79. invalid users =
      80. read list =
      81. write list = "bjoern"
      82. [Test]
      83. path = /srv/dev-disk-by-id-md-name-bjoern-RAID1/Test
      84. guest ok = yes
      85. read only = no
      86. browseable = yes
      87. inherit acls = yes
      88. inherit permissions = no
      89. ea support = no
      90. store dos attributes = no
      91. vfs objects =
      92. printable = no
      93. create mask = 0664
      94. force create mode = 0664
      95. directory mask = 0775
      96. force directory mode = 0775
      97. hide special files = yes
      98. follow symlinks = yes
      99. hide dot files = yes
      100. read list =
      101. write list = "bjoern"
      Display All

      Further outputs:

      ps aux |grep smb
      root 19872 0.0 0.0 12752 2240 pts/0 R+ 01:02 0:00 grep smb

      systemctl status nmbd
      ● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd)
      Loaded: loaded (/etc/init.d/nmbd)
      Active: active (exited) since Mo 2017-09-18 00:07:37 CEST; 55min ago
      Process: 16024 ExecStart=/etc/init.d/nmbd start (code=exited, status=0/SUCCESS)


      Sep 18 00:07:37 bjorn nmbd[16024]: Starting NetBIOS name server: nmbd
      Sep 18 00:07:37 bjoern nmbd[16024]: Warning: Fake start-stop-daemon called, ...g.
      Sep 18 00:07:37 bjoern systemd[1]: Started LSB: start Samba NetBIOS nameserv...).
      Sep 18 00:07:37 bjoern nmbd[16024]: .
      Hint: Some lines were ellipsized, use -l to show in full.
    • In the user tab, change the password for the bjoern user to same password it is currently and let me know if that fixes it.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • unluckily it does not.
      I tried it twice, even to another very simple password.

      After several other tries I found the solution for my smb/cifs issue:
      I had to replaced the FAKE start-stop-daemon with the REAL one:
      mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon


      The omv is not shown in the network list, but I am able to establish a connection with my shares.

      So the next thing to investigate is the issue with the notifications.

      Björn

      The post was edited 1 time, last by bjoern ().