Connect to RHEL SAMBA share without username/password on Windows

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have our smb.conf set up as below



# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
workgroup = SAMBA
security = user

passdb backend = tdbsam

printing = cups
printcap name = cups
load printers = yes
cups options = raw

guest account = samba

[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775

[edi]
path = /dat/101/edi/
public = yes
create mask = 0664
directory mask = 0775


I want Windows users to be able to open \serveredi without being prompted to enter a username and password. I have tried mixture of options from browsable, public, force user, force group etc. with no luck.







share|improve this question



















  • Have you tried making them part of the same domain?
    – Ignacio Vazquez-Abrams
    Jul 3 at 15:23










  • Access them how -- as unauthenticated guests or as authenticated users?
    – AlexP
    Jul 3 at 16:23










  • As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
    – user6888062
    Jul 3 at 16:27














up vote
1
down vote

favorite












I have our smb.conf set up as below



# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
workgroup = SAMBA
security = user

passdb backend = tdbsam

printing = cups
printcap name = cups
load printers = yes
cups options = raw

guest account = samba

[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775

[edi]
path = /dat/101/edi/
public = yes
create mask = 0664
directory mask = 0775


I want Windows users to be able to open \serveredi without being prompted to enter a username and password. I have tried mixture of options from browsable, public, force user, force group etc. with no luck.







share|improve this question



















  • Have you tried making them part of the same domain?
    – Ignacio Vazquez-Abrams
    Jul 3 at 15:23










  • Access them how -- as unauthenticated guests or as authenticated users?
    – AlexP
    Jul 3 at 16:23










  • As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
    – user6888062
    Jul 3 at 16:27












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have our smb.conf set up as below



# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
workgroup = SAMBA
security = user

passdb backend = tdbsam

printing = cups
printcap name = cups
load printers = yes
cups options = raw

guest account = samba

[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775

[edi]
path = /dat/101/edi/
public = yes
create mask = 0664
directory mask = 0775


I want Windows users to be able to open \serveredi without being prompted to enter a username and password. I have tried mixture of options from browsable, public, force user, force group etc. with no luck.







share|improve this question











I have our smb.conf set up as below



# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
workgroup = SAMBA
security = user

passdb backend = tdbsam

printing = cups
printcap name = cups
load printers = yes
cups options = raw

guest account = samba

[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775

[edi]
path = /dat/101/edi/
public = yes
create mask = 0664
directory mask = 0775


I want Windows users to be able to open \serveredi without being prompted to enter a username and password. I have tried mixture of options from browsable, public, force user, force group etc. with no luck.









share|improve this question










share|improve this question




share|improve this question









asked Jul 3 at 15:15









user6888062

214




214











  • Have you tried making them part of the same domain?
    – Ignacio Vazquez-Abrams
    Jul 3 at 15:23










  • Access them how -- as unauthenticated guests or as authenticated users?
    – AlexP
    Jul 3 at 16:23










  • As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
    – user6888062
    Jul 3 at 16:27
















  • Have you tried making them part of the same domain?
    – Ignacio Vazquez-Abrams
    Jul 3 at 15:23










  • Access them how -- as unauthenticated guests or as authenticated users?
    – AlexP
    Jul 3 at 16:23










  • As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
    – user6888062
    Jul 3 at 16:27















Have you tried making them part of the same domain?
– Ignacio Vazquez-Abrams
Jul 3 at 15:23




Have you tried making them part of the same domain?
– Ignacio Vazquez-Abrams
Jul 3 at 15:23












Access them how -- as unauthenticated guests or as authenticated users?
– AlexP
Jul 3 at 16:23




Access them how -- as unauthenticated guests or as authenticated users?
– AlexP
Jul 3 at 16:23












As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
– user6888062
Jul 3 at 16:27




As guests. I just want anyone on the network to be able to open \serveredi without the Windows username/password prompt.
– user6888062
Jul 3 at 16:27










2 Answers
2






active

oldest

votes

















up vote
1
down vote













You need guest ok = yes and guest only = yes on each service definition.



From the man page:




guest only (S)



If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.



See the section below on security for more information about this option.



Default: guest only = no




Note that either or both of these can be in the [global] section instead of the service definition. Also public is a synonym for guest ok and only guest is a synonym for guest only.






share|improve this answer






























    up vote
    -1
    down vote













    add "guest ok = yes" to your share definition. Also check folder rights.



    To recheck your configuration log out and in on your windows client, that the connection is closed.



    Also your should know, that your have to add the authenticated user to your guest share (when you have them), because windows only use one authentication session.






    share|improve this answer























      Your Answer







      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );








       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453251%2fconnect-to-rhel-samba-share-without-username-password-on-windows%23new-answer', 'question_page');

      );

      Post as a guest






























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      1
      down vote













      You need guest ok = yes and guest only = yes on each service definition.



      From the man page:




      guest only (S)



      If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.



      See the section below on security for more information about this option.



      Default: guest only = no




      Note that either or both of these can be in the [global] section instead of the service definition. Also public is a synonym for guest ok and only guest is a synonym for guest only.






      share|improve this answer



























        up vote
        1
        down vote













        You need guest ok = yes and guest only = yes on each service definition.



        From the man page:




        guest only (S)



        If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.



        See the section below on security for more information about this option.



        Default: guest only = no




        Note that either or both of these can be in the [global] section instead of the service definition. Also public is a synonym for guest ok and only guest is a synonym for guest only.






        share|improve this answer

























          up vote
          1
          down vote










          up vote
          1
          down vote









          You need guest ok = yes and guest only = yes on each service definition.



          From the man page:




          guest only (S)



          If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.



          See the section below on security for more information about this option.



          Default: guest only = no




          Note that either or both of these can be in the [global] section instead of the service definition. Also public is a synonym for guest ok and only guest is a synonym for guest only.






          share|improve this answer















          You need guest ok = yes and guest only = yes on each service definition.



          From the man page:




          guest only (S)



          If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.



          See the section below on security for more information about this option.



          Default: guest only = no




          Note that either or both of these can be in the [global] section instead of the service definition. Also public is a synonym for guest ok and only guest is a synonym for guest only.







          share|improve this answer















          share|improve this answer



          share|improve this answer








          edited Jul 3 at 19:04


























          answered Jul 3 at 18:56









          garethTheRed

          22.9k35777




          22.9k35777






















              up vote
              -1
              down vote













              add "guest ok = yes" to your share definition. Also check folder rights.



              To recheck your configuration log out and in on your windows client, that the connection is closed.



              Also your should know, that your have to add the authenticated user to your guest share (when you have them), because windows only use one authentication session.






              share|improve this answer



























                up vote
                -1
                down vote













                add "guest ok = yes" to your share definition. Also check folder rights.



                To recheck your configuration log out and in on your windows client, that the connection is closed.



                Also your should know, that your have to add the authenticated user to your guest share (when you have them), because windows only use one authentication session.






                share|improve this answer

























                  up vote
                  -1
                  down vote










                  up vote
                  -1
                  down vote









                  add "guest ok = yes" to your share definition. Also check folder rights.



                  To recheck your configuration log out and in on your windows client, that the connection is closed.



                  Also your should know, that your have to add the authenticated user to your guest share (when you have them), because windows only use one authentication session.






                  share|improve this answer















                  add "guest ok = yes" to your share definition. Also check folder rights.



                  To recheck your configuration log out and in on your windows client, that the connection is closed.



                  Also your should know, that your have to add the authenticated user to your guest share (when you have them), because windows only use one authentication session.







                  share|improve this answer















                  share|improve this answer



                  share|improve this answer








                  edited Jul 3 at 18:56


























                  answered Jul 3 at 18:50









                  Thomas

                  344




                  344






















                       

                      draft saved


                      draft discarded


























                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453251%2fconnect-to-rhel-samba-share-without-username-password-on-windows%23new-answer', 'question_page');

                      );

                      Post as a guest













































































                      Popular posts from this blog

                      How to check contact read email or not when send email to Individual?

                      Bahrain

                      Postfix configuration issue with fips on centos 7; mailgun relay