[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Samba Problem



No, change the share type to USER and make sure that your passdb backend has all the user accounts and passwords for the users you want to authenticate.  I haven't worked with Samba 3.0 yet, but from reading about it I know you don't need machine accounts unless you are trying to use Samba as a PDC.

In a message dated 7/23/03 8:43:20 PM Central Daylight Time, johnny@kfn.ddns.ms writes:

I believe you will have to either change your share type to "share" or you will have to add the machines you want to grant access into the smbpasswd database.
 
- Johnny -

----- Original Message -----
From: Jerry_Bash@spectral-sys.com
To: debian-user@lists.debian.org
Sent: Thursday, July 24, 2003 7:11 AM



I am having a problem with samba on a machine using debian sid. I have loaded samba version 3.0.0beta2-1 for Debian, and am trying to share the linux drive to windows machines (win 2000).  I have set the smbpasswd, but still, when I get the dialog from windows asking for a username and password, and am told that the username and password are incorrect.

I have not tried to set up printers yet, so that section is not important at this time.  It is the home directories I am trying to use at this time.
The bottom, from log.smbd looks wrong, but I am not sure, and do not know how to fix it.

If anyone can help, I'd appreciate it.

Thanks,
Jerry Bash

From log.nmdb, after rebooting, I get:
*****
[2003/07/23 18:43:53, 0] nmbd/nmbd.c:terminate(54)
Got SIGTERM: going down...
[2003/07/23 18:45:49, 0] nmbd/nmbd.c:main(642)
Netbios nameserver version 3.0.0beta2-1 for Debian started.
Copyright Andrew Tridgell and the Samba Team 1994-2003


testparm yields:

Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

# Global parameters
[global]
    workgroup = SSI
    server string = %h server (Samba %v)
    obey pam restrictions = Yes
    passdb backend = tdbsam, guest
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
    syslog = 0
    log file = /var/log/samba/log.%m
    max log size = 1000
    dns proxy = No
    panic action = "" %d
    invalid users = root

[homes]
    comment = Home Directories
    path = /home/jlb
    valid users = jlb
    read _only_ = No
    create mask = 0700
    directory mask = 0700

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


This is from log.smbd, and looks like something is wrong, but I don't know how to fix it. 

[2003/07/23 18:59:12, 0] smbd/server.c:main(747)
smbd version 3.0.0beta2-1 for Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2003
[2003/07/23 18:59:12, 0] printing/pcap.c:pcap_printer_fn(361)
Unable to open printcap file /etc/printcap for read!
[2003/07/23 18:59:12, 0] smbd/server.c:main(781)
standard input is not a socket, assuming -D option
[2003/07/23 18:59:12, 0] lib/pidfile.c:pidfile_create(84)
ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 304 is running.
[2003/07/23 19:02:55, 1] sam/idmap_tdb.c:db_idmap_init(487)
idmap uid range missing or invalid
idmap will be unable to map foreign SIDs
[2003/07/23 19:02:55, 1] sam/idmap_tdb.c:db_idmap_init(499)
idmap gid range missing or invalid
idmap will be unable to map foreign SIDs
[2003/07/23 19:02:59, 1] sam/idmap_tdb.c:db_idmap_init(487)
idmap uid range missing or invalid
idmap will be unable to map foreign SIDs
[2003/07/23 19:02:59, 1] sam/idmap_tdb.c:db_idmap_init(499)
idmap gid range missing or invalid
idmap will be unable to map foreign SIDs
[2003/07/23 19:02:59, 1] sam/idmap_tdb.c:db_idmap_init(487)
idmap uid range missing or invalid
idmap will be unable to map foreign SIDs
[2003/07/23 19:02:59, 1] sam/idmap_tdb.c:db_idmap_init(499)
idmap gid range missing or invalid
idmap will be unable to map foreign SIDs




Reply to: