similar to: Changing passwords problem from Win95

Displaying 20 results from an estimated 9000 matches similar to: "Changing passwords problem from Win95"

1999 Jan 11
0
SAMBA digest 1937
TO THE SAMBA TEAM: MAY YOUR TRIBE BE HERE FOREVER! YOU' SIMPLY GREAT BUT i CAN'T AFFORD TO BUY YOU A PIZZA BUT OUR NATIVE PIE "BUKO (YOUNG COCONUT) PIE" IS BETTER! i HAVE BEEN USING SAMBA 1.9.16P9 AND STILL ALRIGHT. PERHAPS I'LL DO CHANGE TO SAMBA 2.0 AND THIS IS A LONG WAY! i DID TRIED SAMBA SINCE MY OFFICE CAN'T AFFORD TO BUY NFS TO SERVE AT LEAST 20 PCs AND
1998 Mar 31
1
changing password from win95 fail
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
1999 Jul 07
0
Migrating from 1.9.19-prealpha
Hi, We have been using 1.9.19-prealpha very successfully for over a year and have just started migrating to 2.0.4b, the environment is Sun Sparc running Solaris 2.5.1 and NT 3.51 & 4.0(/sp3). On the servers that have been upgraded, the log files are filling up with some ominous messages, but curiously, users are not reporting any errors at the moment. The following are characteristic of
1999 Feb 02
1
Limits on smbclient -M?
Greetings- We use smbclient -M to send a Message of the Day to clients every once in a while. The clients are NT4 (SP3), and the server is Samba 1.9.19-prealpha. However, the same problem appears with version 2.0.0. The issue is: once the file to be sent exceeds approximately 675 bytes (smbclient reports sending 975 bytes, presumably including some overhead), the message turns up blank on the
1998 Oct 09
2
Failed to connect NT workstation to Samba2.0alpha8
Hi Folks, I downloaded Samba2.0alpha8 from Samba site. Compiled it and installed it on the Solaris 2.6 unix box. I set up domain logon for both Windows 98 clients and WinNT. There is no problem logging on from Windows98 and the shares are all working alright. Then, I followed Samba NTDOM FAQ and add the NT workstation name into /etc/passwd and smbpasswd (using smbpasswd -a -m
2000 Mar 31
0
TNG-1.0.5 Problems
Hi... I have exactly the same problem with lsarpcd giving the error "ERROR: setgroups call failed!". Anyone know of a fix?? MWP > Hello > > I was just installing the new TNG 1.0.5 and after i installed and cleaned the > logs i started the dameons and was unable to access the shares on win98. The > computer showed up in Network Neighborhood but i would get a \\comp03
1998 Jun 25
3
Cannot change password
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
1998 May 05
0
-DALLOW_CHANGE_PASSWORD and FreeBSD
Hi In usr/ports/net/samba/work/samba-1.9.18p4/source/Makefile is: # -DALLOW_CHANGE_PASSWORD if you want users to be able to set their password # remotely (only works on some systems) and then for FreeBSD port: # This is for FreeBSD # contributed by kuku@acds.physik.rwth-aachen.de # NOTE: You may need to add -DBSD44 if you have password problems FLAGSM = -DFreeBSD
1998 May 11
1
SAMBA-NTDOM
Hi I'm becoming a bit confused. I have been trying out the Samba PDC code from BRANCH_NTDOM on Solaris 2.5.1 (with great success !). I now want to download the latest version and messages on the samba-ntdom list say to download from the main branch. What exactly do I put in my cvs command ? The NTDOM FAQ says 'cvs -d :pserver:cvs@samba.anu.edu.au:/cvsroot co samba '. When I do
1998 Nov 14
2
no updates seen on PC after unix changed (v2.0 alpha)
Hi, I just installed Version 2.0.0-prealpha on a Solaris 2.5.1 machine. We are exporting one filesystem to the PC's. I can connect from my Win95 PC without a problem and I see all the files on the shared drive. If I bring up Windows explore and double click on a text file I can see the file without a problem. I then close the file and go to the unix box and change the text file. If I then
2001 Mar 07
0
Linux box WINS client ONLY
Hi there, I would appreciate some help on the following problem: I am trying to set up Samba on a Linux box to get the only functionality of WINS name resolution as a client. I especially do NOT want to participate in the browsing process. I would like this box to be as invisible as possible regarding to NetBIOS. Here is my smb.conf file: ---- START smb.conf [global] workgroup = WHATEVER
2011 Aug 13
0
3.6.0 rejects new passwords greater than 8 characters
I have passwords stored in passdb.tdb by smbpasswd in Solaris Express 11. For existing accounts, all passwords, including those more than 8 characters, work. However, when I created a new account and assigned it a password greater than 8 characters, I am unable to login from Mac OS X 10.6.8 and Windows Server 2008. The smbclient on the Solaris server still works. Passwords 8 characters or fewer
1999 Jul 08
1
SAMBA digest 2158
Unknown recipient ----- Original Message ----- From: <samba@samba.org> To: Multiple recipients of list SAMBA <samba@samba.org> Sent: Thursday, July 08, 1999 1:02 AM Subject: SAMBA digest 2158 > SAMBA Digest 2158 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) msaccess and samba prob solved -
2009 Feb 20
0
[LLVMdev] libLTO warning
Maurice Gittens wrote: > Hi all, > > I just svn-updated the 2.5 branch on my machine and I noticed this > warning during the build. > > *** Warning: Linking the shared library > /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool > *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o >
2009 Feb 20
2
[LLVMdev] libLTO warning
Hi all, I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build. *** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o
2009 Mar 25
2
[LLVMdev] llvm-2.5 build failure (fedora f10)
Hi all, On my Fedora 10 x86-64 the current svn dies in the following way: /home/maurice/installation/llvm-dev/utils/TableGen/Debug/TGLexer.o: In function `llvm::TGLexer::getNextChar()': /home/maurice/installation/llvm-dev/utils/TableGen/TGLexer.cpp:71: undefined reference to `llvm::TGSourceMgr::FindBufferContainingLoc(llvm::TGLoc) const'
2009 Mar 25
0
[LLVMdev] llvm-2.5 build failure (fedora f10)
On 2009-03-25 15:48, Maurice Gittens wrote: > Hi all, > > On my Fedora 10 x86-64 the current svn dies in the following way: > > /home/maurice/installation/llvm-dev/utils/TableGen/Debug/TGLexer.o: In > function `llvm::TGLexer::getNextChar()': > /home/maurice/installation/llvm-dev/utils/TableGen/TGLexer.cpp:71: > undefined reference to >
1998 Oct 13
0
2.0.0-prealpha*: Only 8.3 filenames with NT 3.51?
Hi all, We've been using the 2.0.0 prealpha's with some success, but now I have run into a problem which I can't seem to solve. The client, an NT 3.51 workstation logged in to an NT 3.51 PDC, can't create long file names on a 2.0.0 prealpha Samba server. For example, when renaming a file from 'readme.doc' to 'readme.pqrst', 'readme.pqr' is created. In
1998 Oct 02
1
Win95 and mixed case passwords (1.9.18p8)
Hi there, I've just tripped over a problem I thought only existed in WfWg3.11. On Win95 clients connecting to a 1.9.18p8 Samba server (IRIX 5.3) the first logon dialog box seems to have a problem with mixed-case passwords. If I have a lower case password, then I can just enter it in the Win95 'Microsoft Network' logon dialog at startup, and all the shares are reconnected. If I
1998 Dec 29
2
Encrypted passwords and OS2/Win95/Win98
My LAN is running Samba v1.9.18p10 under RedHat Linux v5.2. Using the SMB services are Win95 and OS/2 clients. It's all running fine. I will soon be adding Win98, though, and I understand that there is a question of password encryption. I'm concerned how the encrypted/plain-text communication of password will affect my existing configuration. If I reconfigure Samba to use encrypted