Problem attaching to a Samba web server with share setting security

I'm establishing a Samba web server on Ubuntu 9.04 Server Edition.

What I'm attempting to do is have a share that is legible by every person, and also writable by a select couple of.

I have the ability to login from my computer system making use of smbclient //server/security -U brad,. yet I am incapable to connect making use of [Places->Connect to Server... ] with a username and also password.

One idea I thought of is that I'm making use of lower instance letters in the password.

This is a section of the /etc/samba/smb.conf documents that was created by swat.

/etch/samba/smbd.conf

[global]
  preferred master = Yes
  domain master    = Yes
  wins support     = Yes

  security               = SHARE
  usershare allow guests = Yes
  guest ok               = Yes
  null passwords         = Yes
  guest account          = samba
  map to guest           = Bad User

  unix password sync     = Yes
  lanman auth            = Yes
  client plaintext auth  = Yes
  lanman auth            = Yes
  client NTLMv2 auth     = Yes
  client lanman auth     = Yes
  client plaintext auth  = Yes


[Security]
  comment = Security and Antivirus software
  path                = /share/security
  write list          = brad
  inherit permissions = Yes
  inherit owner       = Yes
  hide special files  = Yes
  hide unreadable     = Yes

/var/log/samba/log.192.168.0.5

# smbclient //server/security -U brad
[2009/05/04 09:45:31,  1] smbd/service.c:make_connection_snum(1111)
  192.168.0.5 (192.168.0.5) connect to service Security initially as user brad (uid=1000, gid=1000) (pid 3129)
[2009/05/04 09:48:49,  1] smbd/service.c:close_cnum(1323)
  192.168.0.5 (192.168.0.5) closed connection to service Security

# smbclient //server/security -U brad
[2009/05/04 09:48:53,  1] smbd/service.c:make_connection_snum(1111)
  192.168.0.5 (192.168.0.5) connect to service Security initially as user brad (uid=1000, gid=1000) (pid 3177)
[2009/05/04 09:48:58,  1] smbd/service.c:close_cnum(1323)
  192.168.0.5 (192.168.0.5) closed connection to service Security

# smbclient //server/security -U brad # giving null password at prompt
[2009/05/04 09:49:45,  1] smbd/service.c:make_connection_snum(1111)
  192.168.0.5 (192.168.0.5) connect to service Security initially as user samba (uid=1024, gid=1024) (pid 3189)
[2009/05/04 09:49:51,  1] smbd/service.c:close_cnum(1323)
  192.168.0.5 (192.168.0.5) closed connection to service Security

# connect with [Places->Connect to Server...] # with username and password
#
#

# connect with [Places->Connect to Server...] # without username
[2009/05/04 09:50:29,  1] smbd/service.c:make_connection_snum(1111)
  192.168.0.5 (192.168.0.5) connect to service Security initially as user samba (uid=1024, gid=1024) (pid 3310)

When I visit making use of smbclient //server/security -U brad, I can delete a documents I place there by various other methods.

All documents and also folders are presently possessed by the username samba, yet I agree to transform the proprietor if it would certainly aid.

I would actually favor to maintain it under share setting security.

This is what I wound up doing :

[Security]
  comment  = Security & Antivirus software
  path     = /share/security
  readonly = Yes

[Security$]
  comment   = Security & Antivirus software +rw
  path      = /share/security
  browsable = No
  administrative share = Yes
0
2019-05-09 11:21:54
Source Share
Answers: 2

I assume that you require to re - check out whether share - setting protection is what you in fact require for this trouble. Share setting protection suggests that a password is made use of to confirm to a share, not a username/password mix.

If you intend to permit numerous customers (visiting as themselves) accessibility to change the documents after that you require to make use of customer degree protection.

If you intend to permit any person that recognizes the magic password to see the share, after that share setting protection is appropriate for you.

See the Samba Documentation for additional information on share degree protection.

0
2019-05-17 13:40:34
Source

The ideal means to debug this is examine/ var/log/messages or comparable to see what auth mistakes Samba is creating. If you can upload that this is mosting likely to be less complicated.

You can tail - f/ var/log/messages as well as additionally examine/ var/log/samba/ *

Post your outcomes when you attempt to connect. You're more than likely curious about smbd and also nmbd mistakes, so you can grep for those.

0
2019-05-11 17:18:38
Source