SuSE 9.0, connected to a D-Link residential router. Connections to our ADSL work fine. Can see and touch the shared directories on my wife's NT machine. No problem. I started a samba server so her machine could see the SuSE box. Created a "shared" directory using Konq ( /home/myuser/shared ) In the Properties dialog I set Permissions to "Others can view and modify content". In the Local Net Sharing tab, I click "Configure File Sharing", which launches the root password request. Once I'm authenticated as root I get this two-option dialog: Configure File Sharing Do not allow users to share files x Allow users to share files from their HOME folder I don't have any other option, so I select the second one. From the Windows box, point NT Explorer at Network Neighborhood. This shows: Network Linux homes nobody printers If I double-click "printers", I see the printer that's attached to my SuSE box. Therefore I know the connection is good. I double-click "homes", and get an authentication dialog for \\Linux\homes. It wants a user and a password before it will let me see my own shared directory on the SuSE box, or my wife's shared directory on the SuSE box. This is where I have a problem. I have not created any such user/group or other entity as "homes". At first, I thought it was just NT's whimsical way of referring to /home directory on the SuSE box, which in turn contains my account home directory and her account home... both of which DO have names and passwords associated, if only I could get past this authentication step for \\Linux\homes. WHAT IS IT LOOKING FOR? I've tried my linux account name and password, her linux account name and password, root's name and password, and even her NT-side account name and password. All fail. I don't have any user called HOMES on my Linux box. There's no group called that, either. What simple, obvious thing am I missing? How do I get past "homes" to the actual account-associated shared directories? I could still telnet or ssh, but I want to get samba working. Thanks, /kevin (half-connected in Ottawa)
From the Windows box, point NT Explorer at Network Neighborhood. This shows: Network Linux homes nobody printers
If I double-click "printers", I see the printer that's attached to my SuSE box. Therefore I know the connection is good. I double-click "homes", and get an authentication dialog for \\Linux\homes. It wants a user and a password before it will let me see my own shared directory on the SuSE box, or my wife's shared directory on the SuSE box. As near as I can see, there *is* no entity "homes", so I can
On Thursday 19 February 2004 21:18, elefino wrote: [...] think of no password to supply for it... so I'm stuck before I can get to my declared shared directories. Further info, from YAST > Network Services > Samba Server x Enable Samba Server (of course...) Sharing Type x File and printer sharing Domain or Workgroup WORKGROUP Server Description Samba Server Authentication Details Authentication Back-end x smbpasswd (Note from me: in the /etc/smbpasswd file, there are settings for my regular users, and one for the "nobody" user. There's no mention of a "homes" user.) ...back to the YAST Samba setup, we have Shared Resources Available Shares x Share Homes x Share Printers ... under the Advanced settings for the shared resources page, there are three Shared Directories configured in the dialog list: Status Name Path Comment Enabled Home Home Directories Enabled Print$ /var/lib/samba/drivers Printer Drivers Enabled Printers /var/tmp All Printers If I edit the one for 'Home', I see: Option Value browseable true comment Home Directories commentout false create mask 0640 directory mask 0750 guest ok true printable false read only false valid users %S ------------------------------------------------- Does that help pinpoint what I'm overlooking? Thank you, /kevin
elefino wrote:
If I double-click "printers", I see the printer that's attached to my SuSE box. Therefore I know the connection is good. I double-click "homes", and get an authentication dialog for \\Linux\homes. It wants a user and a password before it will let me see my own shared directory on the SuSE box, or my wife's shared directory on the SuSE box.
This is where I have a problem. I have not created any such user/group or other entity as "homes". At first, I
Have you set up samba passwords yet? The rules for usernames and passwords are different on unix and windows; so samba can't just use /etc/passwd but has to have it's own list of usernames and passwords, /etc/smbpasswd. Try $ man smbpasswd to start with. -- JDL Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
On Thursday 19 February 2004 22:19, John Lamb wrote:
This is where I have a problem. I have not created any such user/group or other entity as "homes". At first, I
Have you set up samba passwords yet? The rules for usernames and passwords are different on unix and windows; so samba can't just use /etc/passwd but has to have it's own list of usernames and passwords, /etc/smbpasswd.
Try
$ man smbpasswd
to start with.
Thanks. If only YaST's Samba setup had bothered to say: "'homes' is just a placeholder... you can't use it for anything unless you create a system user of the same name. Instead, you should use the command smbpasswd to add a new local samba user for (equivalent to) each of your local system users that wishes to share files/directories on the Win network (see man[8] smbpasswd)." They've got room for a paragraph like that, because some YaST components have very long Help panels. Or better yet, if YaST is going to let you do most of the other stuff involved in starting and configuring a Samba server, why couldn't it include smbpasswd as part of the YaSTprocess? I must still be misunderstanding something. Anyway, your comment got me to re-re-read and to finally catch on to what was needed. It seems to be working, now. Thank you, /kevin
söndag 22 februari 2004 19:42 skrev elefino:
They've got room for a paragraph like that, because some YaST components have very long Help panels.
Or better yet, if YaST is going to let you do most of the other stuff involved in starting and configuring a Samba server, why couldn't it include smbpasswd as part of the YaSTprocess? I must still be misunderstanding something.
Anyway, your comment got me to re-re-read and to finally catch on to what was needed. It seems to be working, now.
The use of smbpasswd, is in reality an additional component that makes user management a dual process. On one side, the /etc/passwd and on the other /etc/samba/smbusers. A far more convenient way, is to use ldap to store users. YaST has the mechanism to do this, and it also has the ability to add samba schema to each user built. However, and here's the drawback ... YaST unfortunately, doesn't hold the scheme to set the two necessary passwords, nt and lanmanager, that are required by samba. One can obtain smbldap tools, and use these to create and maintain user lists, but it would be nice if the entire mechanism would be included in YaST.
participants (3)
-
elefino -
John Lamb -
Örn Hansen