Can't view SAMBA shares on 3.0.58

nickkay · 17. Januar 2017

Yeah it sure is. Thanks for all your suggestions so far. I might have to rollback to the latest stoneburner release or just use FTP to copy files off.

subzero79 · 17. Januar 2017

Do you have an antivirus or third party firewall running there?

nickkay · 17. Januar 2017

Just windows defender, I've tried disabling that. No third party firewall.

XShocker22 · 17. Januar 2017

Sorry for my bad english at first. Look in the hosts-file of Windows 7/8/10 and write in there the server IP and the Name.

Gesendet von meinem Aquaris X5 Plus mit Tapatalk

tinh_x7 · 18. Januar 2017

@nickkay,

Not sure if this work, but try to un-install the smb_cifs 1.0 from your Windows computer.
And restart your computer.
Then access: \\192.168.0.50\Completed\

Another thing, ensure your workgroup name in OMV is same as your Windows 10 computer.
Your Windows 10 client(s) need to be on the same subnet as your OMV (Wifi/Wired).

nickkay · 21. Januar 2017

Thanks for your help there tinh_x7, tried your steps there still not visible on my win 10 machines. Also checked the subnet. I'ts somewhat of a mystery at this stage.

tinh_x7 · 22. Januar 2017

Are you connecting through Wi-Fi or wired?

nickkay · 3. Februar 2017

Wired connection

tinh_x7 · 3. Februar 2017

Are you able to connect to your share drive on another computer or device?
How about turn off the Samba shares, delete the share, and turn off Samba service.
Then turn Samba service back on, re-add the shares folder to Samba.
Restart OMV, and restart your computer.

nickkay · 1. April 2017

Ok, I've come back to this as I'm getting frustrated using FTP to copy files from my server.

I've completed all the steps listed above, no cheese.

On my Ubuntu machine I get the error message 'Failed to retrieve share list from server: Connection refused' when I try and access my OMV appliance, which rules out a windows based problem.

Any other ideas guys?

donh · 2. April 2017

Is the time set corectly on both machines?

nickkay · 2. April 2017

Yes it sure is on both machines.

tinh_x7 · 2. April 2017

Maybe your firewall in your router or OMV or a misconfiged network setting that blocking the access.
Can you ping OMV from your client side?

donh · 2. April 2017

Is samba running? Should look something like this.

Code

root@omv3beta:~#  ps aux |grep smb
root      3454  0.0  0.3 292404 14840 ?        Ss   Apr01   0:04 /usr/sbin/smbd -D
root      3506  0.0  0.4 300564 17072 ?        S    Apr01   0:00 /usr/sbin/smbd -D
root      3807  0.0  0.4 300532 17024 ?        S    Apr01   0:00 /usr/sbin/smbd -D
root     25996  0.0  0.0  12732  2228 pts/0    S+   09:11   0:00 grep smb

There is also samba update as of this morning.

nickkay · 4. April 2017

This is the output:

root 8379 0.0 0.0 12728 2092 pts/1 S+ 20:19 0:00 grep smb

donh · 4. April 2017

So for some reason samba is not running. I am not the best with systemd yet.

Code

systemctl status smb.service  -l    ### shows status


systemctl start smb.service  -l    ### starts


systemctl stop smb.service  -l    ### stops


systemctl restart smb.service  -l    ### restarts

Status may show a reason or you might need to look in the logs. Might be something in /etc/samba/smb.conf, did you edit that file?

nickkay · 5. April 2017

Hmm very interesting. Its a clean install of OMV, I have not altered anything.

Here's the output:

root@sulaco:/# systemctl status smb.service -l ### shows status
● smb.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
root@sulaco:/# systemctl start smb.service -l ### starts
Failed to start smb.service: Unit smb.service failed to load: No such file or directory.
root@sulaco:/# systemctl stop smb.service -l ### stops
Failed to stop smb.service: Unit smb.service not loaded.
root@sulaco:/# systemctl restart smb.service -l ### restarts
Failed to restart smb.service: Unit smb.service failed to load: No such file or directory.

And here is /etc/samba/smb.conf,

#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log level = 0
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = no
unix password sync = no
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
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
null passwords = no
local master = yes
time server = no
wins support = no
os level = 65
#======================= Share Definitions =======================
[Completed]
path = /media/682ea88d-620b-4480-805c-c0df24472fe9/completed
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
vfs objects =
printable = no
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
hide special files = yes
follow symlinks = yes
hide dot files = yes
valid users =
invalid users =
read list =

donh · 5. April 2017

Told you I was not good at systemd. Will find the right command.

donh · 5. April 2017

systemctl status smbd.service -l

subzero79 · 5. April 2017

Also for windows announce you need running nmbd running. Somehow irrelevant as you should be able to access by \\IP\share

Jetzt mitmachen!