similar to: Samba can't resolv password

I have samba-1.9.18p7-2 smb.conf says: # Configure smbpasswd passwd chat debug = yes # Default passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed* passwd program = /usr/bin/yppasswd Using smbpasswd, my encrypted password is changed, but yppasswd is not even touched (as per ls -lu /usr/bin/yppasswd). Furthermore, running smbd with -d 100 didn't seem to show

Server: Slakware Linux 2.0.30, GNU C 2.7.2.1 Samba 18p7 Server is not using PAM and is a ypclient. Client PC's are DOS 6.20 with MS Client 3.0 and Windows 95. I am having trouble changing passwords using the "net password \\<server>" command from either DOS or Win95 command prompt. Changing passwords worked fine using Samba 17p3. The compile switch -DALLOW_CHANGE_PASSWORD

> Date: Mon, 27 Apr 1998 18:00:15 +0100 > From: "Robert Koruna" <robert.koruna@tiwag.co.at> > To: samba@samba.anu.edu.au > Subject: DOS-Client using SAMBA-Server > Message-ID: <199804271600.SAA22065@mail.tiwag.co.at> > > Hello, > > I read some of your latest articles depending on DOS and Samba. > You always mentioned TCP/IP 32,

Hello, now I've set up a linux samba password server using Samba 1.9.18p4 on a linux 2.0.33. File and password serving works ok now, but I can't change my passwords with any Win95 utility. Samba always tells me "Wrong password" an d in the logs it says: "Disallowing access to user due to null password check_lanman:password: old password doesn't match" But I know

Hello, I read some of your latest articles depending on DOS and Samba. You always mentioned TCP/IP 32, LANMANAGER-Client from IBM and this mysterios MS Client 3.0. What I would like to know is, if there is a MS-DOS IP stack available, which could use a WINS-server and connect to Samba using NETBEUI over IP ??? I use TCP/IP 32 at the moment for my old windows-clients. Problem is, I have some

Hi, I run samba very happily, but now I recognized problems with restoring files from a tape. If I use certain german characters, like ??? (hope you can read them), it builds file this "Verkn\201pfung". I can use this files from the sambaclient, but I can't access or delete this files out of Linux. I used client codepage = 850 Now I found out, that if I use the options

I've just installed a new DEC Unix 4.0d machine and downloaded the binary version of samba 1.9.18p8 for DEC Unix. I am able to get it up and running, but I am having problems with passwords. I am being prompted for a password when I try to connect to a non-public share, and when I type in my password it is being rejected. I did set security=share in my smb.conf file. I also tried the

Hello, I need to serve one fileshare to different users in different groups ( I do so ). I gave different users different groups and told samba to make new files owned by user:group, mod 775. But now some users have the need to write in the directory of another group. Is it possible to force user and group per directory and not per share, or is it possible to create links in the filestructure

It would appear that Samba <-> Samba across subnets works fine, but Samba <-> NT is a problem. Does anybody else concur with this statement? Specifically, running Samba 1.9.18p10 (Solaris) and directing all password authenication to an NT server on a subnet causes the following output in the log file: ---------------------------------------------------------------------------

I have been trying to make password changing work with Samba from a Windows 95 clients. All the workstations use nonencrypted passwords. The server is SCO Open Server, Samba 1.9.18p10. The relevant lines of smb.conf are passwd chat = *Old*password* %o\n "1):" \n *New*password* %n\n *Re-enter*password* %n \n passwd chat debug = yes passwd program = /bin/passwd unix password sync = yes

I'm having lots of hassles and troubles since I moved to 1.18p10: 1\ Why do I need a smbpasswd and have to have a user equivalent on the unix machine when an NT user wants to print via an smb printer? My NT/Win users shouldn't need to know anything about unix and I don't want to tell them "you have to log into my unix machine and invoke

Here's my setup: Caldera Open Linux Lite (kernel 2.0.29) Samba 2.0.4a Windows Domain (Two Windows NT 4.0 Servers -- one PDC, one BDC -- and numerous Windows NT 4.0 Workstations) I can see my Linux box in Network Neighborhood on my Windows NT boxes. I can open the Linux box and see the top level shares available. When I try to open a share I see one or two anonymous folders. Anyone

Samba is causing a couple huge problems for the NT admins here since we switched a bunch of machines to security=server and started running nmbd. We're running Samba 2.0.2 and 2.0.3 on a mix of Solaris, HP-UX, and OSF1 machines. One, selecting a Samba server in Server Manager, then selecting Computer/ Services causes Server Manager to crash ("An application error has occurred, blah blah,

Hi, I'm running samba-2.0.4b rpm package on Redhat 6.0. I was able to setup samba just fine along with the printer. I can print from the linux box just fine both text and postscript. My NT 4.0 server(SP3) running PDC saw the printer fine. I was able to install the printer as a network printer with no problem. But I just cannot print to it. When I turned on the debug level to 10. I got the

Hi, I have a problem with Samba on an OSF1 v4.0d machine. I get an "INTERNAL ERROR" and a core dump when trying to connect to a share from an NT 4.0 SP3 or W95 machine. I configured Samba to use encrypted password and I set the parameter "security=user". My Samba server is in a workgroup on its own, no PDC and BDCs around. I can see it in my Computer Neighborhood from the NT

I'm trying to figure out how I can change to SMB password and UNIX password together. On the Win98 I change the password via : Control Panel - Passwords - Change Windows password (select also Microsoft Networking) After a few seconds I get the message 'The password you typed is not correct for MS Networking' Are there any known problems with password sync ? I read the digest 2112 till

Dear all, I have a problem synchronizing my Windows98 network password (i.e. samba password) with my Unix NIS+ password. The Unix station is running Solaris 2.6. This is a copy of what I have in smb.conf to enable password change: password level = 2 domain logons = yes logon script = %U.bat debug level = 100 encrypt passwords = yes unix password sync = yes passwd program = /usr/bin/passwd -r

Hello, i've some problems with the plp printer spooler on linux: I changed from bsd printing to plp printing. Previously (with bsd style printing) i was able to browse and delete active printjobs, stop and activate printers from within the win9x/winnt boxes. After changing to plp this is no longer possible. The printjobs themself are still printed. Some output in the log.smb (with debug

'llo, Sorry to barge in like this, but is there someone out there who can tell me what kind of error I'm looking for if the log files say : ... 05/19/1999 12:51:06 Transaction 2 of length 113 switch message SMBsesssetupX (pid 3952) Domain=[IEPER] NativeOS=[Unix] NativeLanMan=[Samba] sesssetupX:name=[THOIEP] SMB Password - pwlen = 24,

I'm trying to get Unix passwords to synchronize on my Red Hat Linux server when users change their passwords in Windows '95. Everything is working quite well, except under a few, key conditions. When a user enters a password that's "too short", Samba doesn't seem to call the routines to change the unix password, but it does change the Windows encrypted password. At this