similar to: smbpasswd command won't work

What is the trick for having home directories on a samba share be accessible from a windows machine?? I am using winbind with NT to authenticate -- it works fine. I have users with accounts on the samba machine, they have the same usernames and passwords on the NT machine. All users on the samba machine have accounts in /home Is there some sort of trick with the template homedir command, and

I just created a new smbpasswd file, all users with unset passwords. Problem is, users can't set their passwords, only I can as root. Password is not set / blank, but they still get: >test> smbpasswd >Old SMB password: <enter> >New SMB password: Samba >Retype new SMB password: Samba >machine 127.0.0.1 rejected the password change: Error was : RAP86: The >specified

My question is, how come daevid (on XP) sees the following directories: \\linux\dae51d \\linux\homes Shouldn't there just be the home dir only? Why does "\\linux\dae51d" show up (I assume it's b/c that's who I am logged in as on XP which maps to linux)? However, the fact that it does show up, shouldn't it be the actual HOME directory of the linux user account dae51d (as

I just want a simple, globally accessible directory for anyone on my LAN. I don't care who they are, who they're logged in as on their windows machine, I don't care about security (it's my own private LAN!!!). Why is this so difficult to do? I've looked through the archives (which by the way, could someone spend a few minutes and put a SEARCH feature there. Following threads

We've recently started using samba-3.0.23d on Mandriva 2007.0 linux systems and we've noticed a change in behaviour of smbpasswd when a non-root user tries to change their password from "NO PASSWORD". Here's an example smbpasswd entry (all one line): testuser:12345:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX: NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000: The

I'm a little less new to samba now - but having a heck of a time getting authentication to work. I'm running NIS+, configured samba with --with-nisplus --with-nisplus-home and --with-automount. Does anyone have some good nis/samba references? I'm striking out. The smbpasswd file *does* have to become smbpasswd.org_dir for samba to work. I first created the smbpasswd file using

Hi, I'm attempting to migrate an NT4 domain to Samba3, and getting quite frustrated with stuff that seems not to work as advertised. I'd appreciate any help. I've set up an OpenLDAP server, and Samba 3, configured it as a BDC, and tried running "net rpc vampire". This all works, and Samba does the appropriate stuff to try and populate the LDAP database. The scripts I've

Help! (pretty please :) I'm still having the problem described below with samba-3.0.24. Here's an excerpt from the smbpasswd man page: When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new pass word twice, to ensure that the new password was typed correctly. No passwords will be

Hello, I reported problem PR#20895. So - i use encrypted passwords. All new unix users are appended to smbpasswd with one script. Every new user is getting a line like this: s1077347:2006:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000:user name The parameter null passwords is NO. Every user who has not set their password can login into Samba NT

I'm trying to set up a samba box at home to centralize my family's storage into one place. Every time I try to connect to the box I get an incorrect user name or password dialog and it doesn't matter what I put in but it won't let me connect. In the log files every time I connect I see something like (repeated several times)... [2003/07/05 13:20:11, 0]

I wonder whether the following setup is possible with Samba since I have problems to get it running: I want password checking for Samba shares on a Linux Samba server to be done via the NT password server. This is mainly thought for the users home directories. Since the users already have given their password to the local workstation I have thought that they do not need to give it again when

I have been tasked to be one of the main targets, er, I mean, guys to facilitate our changeover from a rather aged Novell server to Samba. My boss set up Samba 2.0.7 (RPM shows "samba-common-2.0.7-4" with an RPM -q). I am trying to convert it to PDC functionality, and am having difficulty. In the log I see this: "smbd/password.c:authorise_login(826) rejected invalid user

Hi, I keep coming across this problem. Samba is samba 2.2.5 Go to join a winxp box to the domain and it all appears to work fine. When you restart you can not login because it wasn't done properly. Here are my obversations from samba. A) In the logs there is always this [2002/10/24 07:12:43.415583, 1] smbd/password.c:pass_check_smb(545) Couldn't find user 'nobody' in

Hello. When I run smbpasswd from samba 3.0.23a on a MIPSEL system running Linux 2.4.20 as root, I'm NEVER asked for a password. Even when I create a new user in smbpasswd, I'm not asked: root@HD.bei.digitalprojects.com:/etc/samba# strings smbpasswd root:0:AAD3B435B51404EEAAD3B435B51404EE:31D6CFE0D16AE931B73C59D7E0C089C0:[U ]:LCT-44D63D42:

Hi, I'am running a small samba server at work with 10+ users in the domain (all of them added with W2KSP1 and 2.2.3 or 2.2.4). I uppgraded to 2.2.5 a while back and has not experienced any problem with it, but when I try to add a newly installed W2KSP1 client to the domain I get the following entries in the log file: Sep 10 13:29:55 linus smbd[17681]: [2002/09/10 13:29:55, 0]

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

This is really bizarre. Running Samba 3.0.4 on SuSE 9.1. The password backend is smbpasswd. Each user has a system and samba account and everything has worked as expected until recently. But now, every new user I create is unable to log into Samba server (older users are still able to log in). Inspecting log.smbd the following messages are displayed: [2004/07/22 11:44:56, 2]

When I used smbpasswd it gives me the following error... root at hayek:~# smbpasswd john New SMB password: Retype new SMB password: Failed to find entry for user john. This is despite the existence of the user root at hayek:~# cat /etc/samba/smbpasswd # # SMB password file. # nobody:65534:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:nobody

mksmbpasswd.sh does not create accounts with the X flag in the password flags field. Does this X matter, and if so, what does it mean? It's not in the man page. ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical