similar to: User verification problem using password = server [2.0.0beta1]

We run a Network of Suns (running Samba) and PC-NT (version 4, sp3) machines, at work, and find it very annoying to be unable to change the file permissions of files from NT on the Suns. Is there any way to change the permissions from NT file explorer or otherwise ? Dave Kirkby

Pam_SMB allows Linux clients to validate their passwords against an NT PDC, so the only thing you have to do is set up the accounts on the Linux side with an '*' in the /etc/passwd entry. This can be done using a list of users: #!/bin/bash for i in `cat myuserlist`; do /usr/sbin/adduser -p '*' $i with various other command line options, such as "-s

Let me first apologise for asking on two lists, but this problem is (of course) urgent because prior to this afternoon I was unaware of the problem and it has been affecting production users for two days despite me having warned everyone that they should be looking out for possible Samba problems! I have just upgraded most of our samba servers from 1.9.18 (various patch levels) to 2.2.2 on

I'm trying to build samba 2.2.7 (latest tarball) downloaded about 2 hours ago. System is SunFire 3800, Solaris 8 (Generic_108528-16) and gcc 3.2 (downloaded from Sunfreeware). Gcc -v output is: Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version

================== platform ===================== Linux version: RHEL-3 resp. Scientific Linux 305 Samba vesrion: 3.0.9-1.3E.3 Samba operating mode: security = SERVER ================== problem ===================== 'net use n: \\smbs1\public' on Windows XP, always asks for a password. 'smbmount //smbs1/public /mnt/public -o password=' does not. This all used to work fine

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

> I have just upgraded to Samba 2.0.6 and can no longer connect to Samba > shares on my FreeBSD 3.4-RELEASE machine. When I attempt to connect, the > smb.log contains the following information: > > [2000/01/04 17:54:42, 3] libsmb/namequery.c:resolve_lmhosts(566) > resolve_lmhosts: Attempting lmhosts lookup for name > NTWEB2.AIS.MSU.EDU<0x20> > [2000/01/04

I have installed samba 2.2.7 on freebsd from the ports collections. I had a previous installation of samba 2.0 and I used my old smb.conf file to duplicate the funcationality I had. Trouble is, printing from winNT/2K clients doesn't work. Printing from win9x machines still does. I've been through the docs on samba.org and looked in chap6 of HOWTO collection on printing and the

Hi All, We have been running samba-1.9.18p10 beautifully for the past year or so. Finally decided to upgrade to samba-2.0.6 and am having no luck. We are using security=server such that the users are using their NT login/password to authenticate. When I test the 2.0.6 installation with smbclient, I get the "protocol negotiation failure" message. Does anyone know what this means? I

I am using Samba 2.0.9 on S1 SuSE box and Samba 2.2.5 on S2 Suse box. S1 is acting as PDC for 98, NT clients. (logon script, shares from S1, and S2). Users's passwords are stored on S1, S2 uses security = server and password server = S1 options in smb.conf. I have upgraded both to Samba 2.2.8, but the logon script wants to connect to share from S2, it is prompted for a password. I have

Hello, I am having a very speific problem with my samba interface. We just migrated to a new IBM pSeries server with AIX 5.3. The older server was a RS6000, with AIX 5.2 and everything I'm about to describe below worked without fail. We have a Windows 2000 Server that runs IIS. There is a web-based program (programmed in VB Script) that calls test.sh AIX script (through samba) on our AIX

Hi, I'm trying to get Samba on a Linux box to work. Authentication via user level worked fine, but what I really want is it to take user authentication from a win2k box, which is our "primary local server". The win2k box is not a pdc, (the real pdc is 2000km away, close to the polar circle), but according to the docs it doesn't have to be. So in smb.conf I put: security =

SAMBA was installed on a SCO 5.0.6 several years ago. Logins were validated by an NT server ("DOMAIN") at the time. In March, the NT 4 server was replaced with a Windows 2003 server and the SAMBA sercurity was changed to "SERVER". Most of the users are not listed in the smbpasswd file and security is set to use the Samba user. Since then, most users can attach to the

Hello together! I run Samba 3.0.9-2.3 on Suse 9.2. This Server is in an Active Directory Domain, but it is not able to make it a domainmemberserver. So i uses the following configuration: /etc/samba/smb.conf ********************************* [global] security = Server domain logons = no NIS homedir = no encrypt passwords = yes update encrypted = no password server = EMEA guest account = nobody

I am (unfortunately) still employing an NT 4.0 single domain for my company's network. There is a single Samba 2.2.8a FreeBSD host I have on the network. It's been active for the past year or so. Everything runs smoothly, but I run into issues every so often that seem kind of odd. And the root cause appears to involve the Samba host. Here's a quick rundown: o The Samba box isn't

I have samba 3.x running on FreeBSD 5.3, configuration info follows. One machine, mine, can connect to any share on the FreeBSD machine that i have access to. But no one else can connect, inclusive of me with the same credentials from the other computuers. All clients are WinXP Pro, some have SP2, some dont, mine does not. I had been running samba2.2 and was expierencing the same issue.

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

Hi: I am running Samba 2.5 because SCO's skunkware version of 2.6 just would not run. I am running SCO OpenServer 5.04, which I wish there was a smbclient so that I could perform more adequate server side testing. I am currently faced with three issues which I have not found solutions too. 1. I the log.user name I have found the users do connect to the server but the log is full of the

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,

I'm trying to get Samba 2.2.3a (as distributed with SuSE 8.0) working inside our NT domain . I'm prompted for a username and password when I try to map the share to a network drive from my Windows PC, but my Windows logon and the matching password are rejected. Stepping through DIAGNOSIS.txt and using smbclient on the Samba server itself, I've got as far as step 7 before things