similar to: Problems with smbd...

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

Greetings Having fun with Samba 2.0beta1 and security = server Is there something missing in my config? # Global parameters workgroup = COMCARE server string = Samba %v interfaces = <IP_subnet_a.x>/24 <IP>/24 security = SERVER encrypt passwords = Yes password server = pdc.comcare.gov.au username map =

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 Scenario: Lan with opensuse 11.4 Samba and LDAP server. Linux, win-xp and win7 clients. The Linux clients can login fine under TLS: Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=0 STARTTLS Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=0 RESULT oid= err=0 text= Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 fd=23 TLS established tls_ssf=256 ssf=256 Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=1

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

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

I've been running Samba 2.2.2 for a while as a domain controller on my mostly Windows network. It's been working great up to this point. Anyway, I just put together a new Linux server and installed 2.2.2 on it as well. I copied the conf file and pretty much mirrored everything on the existing server, changed the paths and the "workgroup" field in the conf file to match the new

Samba: binary kit from samba.org Samba version: 2.0.6 computer: SGI indigo2 with a 250MHz 4400 CPU, 64MB RAM, Irix 6.5.6m me: tarjei.jensen@kvaerner.com It looks like every time smbd spawns, the child process seems to die a horrible death and leave a core file. As a result I am unable to use any netbios services on the machine. The core file which I have examined says that the process died with

Can anyone explain why this fails? This was applied to source from openssh.org. Thanks, Ryan =========================== bash-2.05a$ /opt/freeware/bin/patch -p1 < ../openssh-3.6.1p2-passexpire20.patch patching file TODO Reversed (or previously applied) patch detected! Assume -R? [n] y patching file acconfig.h Reversed (or previously applied) patch detected! Assume -R? [n] y patching file