similar to: NT User Account Locked Out By Samba

Using Samba v2.0.10 on a RedHat v7.1 box, I see that the Win98 clients on our network are making sporatic requests for user "nobody" (as shown below). Anyone know what's going on here? My network has both Linux and Win98 clients, but only the Win98 clients are showing this behavior. Both the Linux and Win98 clients access the same shared drives, but only the Win98 clients use

Hello, I'm having a problem configuring samba (2.0.5a) on a Linux system using NIS+ as the password system. Samba complains that it cannot find the smbpasswd file, which is not surprising as I'm not using one. I tried 'smb password file = passwd.org_dir' that sort of worked, except that it creates a directory called passwd.org_dir from whatever directory I ran the smbd from.

Hi all, sorry if this has been asked before, but as far as I could see there's no similar entry in the archive. I'm using version 2.2.7a on a HP machine running HP-UX 11.11. The binaries have been created for PA-RISC 2.0 supporting 64Bit mode. The SAMBA has been configured to use securty = server. Password servers has been 'defined'. For a certain user (Service account used to

We are seeing erratic behaviour from Samba for connecting Unix drives to an NT terminal Server. Samba version 2.0.6 Solaris 2.6 NT Server 4.0 Terminal Server Edition with service pack 4 running WinCenter NIS Logon Utility. The NT server is not part of a domain and uses the WinCenter Logon Utility to authenticate username and passwords from my Unix NIS server. Samba is set up for server level

Hi all, Set-up: Local NT4-RESOURCE domain which the Samba server is a member off. One NT4-ADMIN domain with users accounts and one W2K domain with some other user accounts. A one way trust from NT4-ADMIN to NT4-RESOURCE and a one way trust from W2K to NT4-RESOURCE. Samba version 2.0.7 running on Solaris 2.6. According to the NT admins, the W2K domain is in native mode, but they still use

Hi there, I ran into a weird problem. 2 machines, one with an NE2000 clone (W95) card and the other with an Etherworks203 (linux with Samba). Samba: from W95 client file shares ok, home shares ok, can read and write files. Printing: I *can* configure a printer up to the printing of the testpage, that fails. At starting of W95 it succesfully connect to the printer share. Printing something fails,

Hi I have Win2k servers connecting to the samba server by mapping a windows user to unix user. We never had any problems with thsi connectivity but for past 2 weeks we have an erratic problem which causes the windows account to lock thus making samba unfunctional. When I get the windows account unlocked then samba starts functioning properly again. I do not have a scenario to reproduce the

We need to give a user in another domain access to our printer: our domain: OURDOM (samba) other domain: OTHERDOM (AD?) user's workstation: \\OTHERDOM\WKSTN, in other domain printer: in our domain user: JOEBLOW - an account in each domain with the same login/password We're getting this error in wkstn.log: [2003/05/28 20:44:20, 1] smbd/password.c:server_validate(1101) password

Hi, we are using Samba 2.2.5 in a somewhat larger configuration: a big NFS file server and a separate box acting as a NFS/SMB gateway. Usually there are about 200-250 connected clients. The box is a Sun Netra T1 AC200 with Solaris 8. Sometimes we get the following (loglevel 1): [2002/07/01 11:48:50, 1] smbd/service.c:make_connection(615) si17062 (10.2.202.88) connect to service mrd8si as user

Try another console like ALT-F2. See if you have a black screen login prompt. I opened a bug with RedHat for a system that when I went from 6.7 to 6.8 booted but would not start the X server. Problem was in the MACH64 driver. It is missing an external symbol that the X server requires. -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Leroy Tennison

Hi Using samba-2.0.0 on aix3.2.5.. Was using 1.9.18p10 before with no problems. I am authenticating through an NT domain (HCHQ) and have smb.conf set so most shares are public (though one gets updated by me every now and then). We never used encrypted passwords. I had 'read only = true' and 'write list = andreww jons' (I also 'force user' so that files are owned by me..)

Hi all I am sure that there is some mention of this error in the docs somewhere but I could not find it. So, sorry for repeating it here. I have installed samba 2.0.3 on solaris 2.5.1 I carried out all the tests described in the documentation. They were all successful. Bu from an NT server I can't do this net use z: \\server_name\\tmp System error 86 has occurred The specified network

I am also using CentOS, but to get a bug fixed, you have to go upstream to RedHat. I think John Pierce is right, I had to change my run level to get the alternate consoles to work. I still have the machine at run level 3 hoping that a bug fix lets me go back to run level 5. Other machines work fine, just the 2 with the MACH64 video on the motherboard will no longer run X. Bob S.

I have been running RedHat 5.2 and Samba 2.0.3 for the past week or so. My network is made up of NT servers and 95/98 clients. So far Samba has been running beautifully - I can use my Samba shares just like they are NT shares. My only problem is from time to time my Win98 machine "goes to sleep" and asks me for either a password or an IPC$ password. Generally this happens after a

Due to a problem with a crash bug in smbd in 2.0.5, we have released Samba 2.0.5a containg a fix for this problem (which was causing problems for people using macro expansions in print scripts). Here are the notes for what we fixed between 2.0.5 and 2.0.5a, which should now be available on all worldwide mirror sites. Changes in 2.0.5a ----------------- 1). Fix for smbd crash bug in

How do i unsubscribe??

I figured out that the system boots OK and it is possible to login remotely. However the monitor does not start up. Do you know how to fix it? On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana < srosenthal at cfa.harvard.edu> wrote: > You are right it is a Dell PowerEdge. However as I said it stops in the > middle of booting with no message. > > > > On Mon, Mar 20,

The problem: Strangely, the PDC rejects user password challenges from Samba. The user account gets locked. After unlocking the account, everything is back to normal. This happens several times a day to different users and from different Samba servers. All Samba servers have the same [global] configuration. Is this a Samba problem? Is samba perhaps not passing along the correct password? If I add

Good morning, I am posting msgs on the NON OPERATION of WINBIND. GOOD I should say that without I had made any change in the system it started to work in an of my facilities. INCREDIBLE but it worked. The problem now is that I tried log in the samba not previously using an user servant in the smbpasswd and him of autentication mistake. But should not WINBIND facilitate that? Do I need to have user

Hi all, I just released Samba 2.0.7pre2, available from : ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz This is the second snapshot of the code that should become the official Samba 2.0.7 and is feature complete (ie. I'm only going to accept bug fixes, not more features). This is *not* production code, but should work well as a file and print server, and contains fixes for all