similar to: Passwords fail from Win95 but not from DOS (Samba 1.9.16p11/NetBSD)

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 All, First, I am new to Linux. I am having troubles with NT4 SP3 and samba-1.9.18p5: some NT4 nodes can map Linux and/or Unix drives, some others can't. The errors messages are: - this account is not authorized to login from this station or - incorrect password or unknown username (but I am sure that login/password are ok) I have already check the EnablePlainTextPassword = 1 in the

Hello, I finally switched to the samba-1.9.18p4, and got all my files on this server. But now I have a big problem, all our NT machines can't access the server. They tell wrong user or password. In the debugging mode I see, that the NT machines come to the server and find the right user, then they tell me: lp_file_list_changed() file /usr/local/samba/lib/smb.conf ->

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 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

'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,

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

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: ---------------------------------------------------------------------------

Connecting from WinNT to Samba 1.9.18p10 I have another question: When I have a drive map to my Unix homedir, which should be automatically reconnected during login, I get an error that my password is not correct. If I control the log file of Samba I see: 1998/10/08 17:37:43 changed root to / open_oplock_ipc: opening loopback UDP socket. bind succeeded on port 0 open_oplock ipc: pid = 33822,

I have just replaced an old FC9 server with a new FC14 server as the old one died. Before it died I was having trouble authenticating connections to it. Now I have the new server running I'm still suffering the same problem. Setting up a user and setting the password gives no errors, but then connections fail complaining about the password. It is very much a virgin vanilla setup. All I

I have a Centos 7 server ? ZEPPO - which I use for file sharing. The clients are all Win7 PC's and I use Samba to serve the files. It has been working fine ever since I put it live late last year. Now, all of a sudden, all files are read-only. I recently added a USB WiFi dongle to give the server a presence on the WiFi VLAN. Using this I am able to provide an Air Print service for our

Hi Paddy, I was suspecting the same, and from the output below I think you're right. However, I was hoping I could just repair this problem for now, and worry about replacing the HDD later. I need to resume some services that also seem to generate this same error. Gary [root at zeppo services]# ll /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so -rwxr-xr-x. 1 root root 61976 Sep 15

Hello everyone, I recently built a second PC at home with RH 7.2 and have downloaded and compiled 2.4.13 to my liking and have made smbfs asa module. I am attempting to mount an smb share from my linux file server [running RH 7.1 with 2.2.18 and smbfs as a module as well]. Details: daffy - RH 7.1 - samba works fine - can be mounted from other clients [Win2k,win98,winNT] tweetie - RH 7.2 - can

Hi Gary, That "Input/output error" suggests a disk problem to me. Does that file /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so actually exist and is it readable? Also look the the output of 'rpm -V python-libs' to see if rpm considers the installed files to be corrupt. If it's not that, then you could try 'yum reinstall python-libs'. Paddy On Thu, Nov 07,

I've just tried a yum update on one of my C7 boxes and got the following output. I'm guessing to fix this I need to re-install the RPM, but I can't remove it because of dependancies, so how can I fix the problem? I've managed to download a later version of the RPM, but haven't managed to find the same version as the one installed. Gary [root at zeppo ~]# yum install There

I few weeks back my server started having a problem where all shares are now readonly. AFAIK nothing has changed except a 'yum update' which was probably around the same time. Everyone still has the shares on their Win7 PC's and can see the contents. However, if they try to open a file it opens read only. If the try to create a new file (e.g. right click -> New -> Text

I'm using samba 2.1 pre-alpha. When I right click an .exe file on the most shares, explorer freezes, and must be killed to recover. The problem doesn't show up on the home shares, but appears on any other shares I create. I've experienced this problem on many different workstations. Looking at the logs, it seems to be a problem with oplocks; the part of the log that seems to apply is

Hello all We have experienced some problems with samba recently. People were unable to access their files. Here is the story: [2000/03/02 09:12:26, 1] smbd/service.c:make_connection(535) pdc (192.168.21.210) connect to service Document as user root (uid=0, gid=0) ( pid 1987) [2000/03/02 09:12:51, 0] locking/shmem_sysv.c:sem_change(124) ERROR: sem_change(6,-1) failed (Identifier removed)

I'm attempting to get a Linux box to authenticate users from NT. I think it's possible by writing a PAM module (not hard) and using part of Samba's source to verify the password on the NT server. I'm getting pretty bogged down trying to work out how to do this - it seems like it should be simple - just take the password and username and ask the NT server if it's correct. If

[2001/11/07 11:37:14, 3] smbd/sec_ctx.c:set_sec_ctx(320) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0[2001/11/07 11:37:14, 5] smbd/uid.c:unbecome_user(215) unbecome_user now uid=(0,0) gid=(0,0)[2001/11/07 11:37:14, 6] param/loadparm.c:lp_file_list_changed(2203) lp_file_list_changed() file /usr/local/samba/lib/smb.conf -> /usr/local/samba/lib/smb.conf last mod_time: Wed Nov 7