similar to: Urgent RHL Samba problem update

We have a Red Hat linux 3.0 ES server. I downloaded upgrades for this server from the Red Hat website and installed them, including samba upgrades. Now users cannot mount network drives from this server onto their PC's. I upgraded to samba-3.0.9-1.3E.3 and users are now getting "system error 1326 has occurred - logon failure unknown username or password". The previous

Hello all, I'm using the attached patch. With it, if you add OPTIONS="-6" in /etc/sysconfig/sshd (this kind of sysconfig/<name> is a pretty normal RHL practice), then you can enable ipv4 and ipv6 on RHL without problems and without having to modify the init.d/sshd script. This or something like should IMO be added. Removing 'noreplace' from sshd_config

The RHL 6.2 command "/etc/rc.d/init.d/crond start" prevents clean logout from compiled version of OpenSSH-2.5.1p1 on all hosts. The command "/etc/rc.d/init.d/crond stop" is OK. This occurs for interactive or command line requests. ssh remotehost /etc/rc.d/init.d/crond stop --- works every time ssh remotehost /etc/rc.d/init.d/crond start --- hangs every time Control-C will

Hello all, A few days ago I noticed that the following seems to happen when upgradign OpenSSH on Linux-based (/etc/rc.d/init.d/sshd) based systems: - sshd is restarted with 'sshd restart'; however sshd serving in port 22 is not replaced. - you have to kill the old one (netstat -ltp | grep :ssh ; kill ...) first, then restart sshd. - This might happen only when performing the upgrade

Hello! I just joined this mailing list because I experience extreme problems in a network where I added now a Linux-box. Because I must get this fixed urgently, I describe here what I have. If somebody has a solution (must be something with the configuration), please help. -- THANKS ! SETUP: ====== Server : SuSE Linux 8.1 with SAMBA 2.2.5 Clients: Windows-NT4.0 Workstation with SP4/5/6 PDC

Hello, I am having some problems understanding a few concepts in Samba while trying to use samba-common-3.0.0-14.3E, samba-client-3.0.0-14.3E and samba-3.0.0-14.3E on RHE 3.0. Basically, I have security = domain. My system is running winbind, I've added the winbind calls to nsswitch.conf. I can get my wbinfo -u and wbinfo -g commands to show me what I want. That all seems happy. I have a

Hi all, after the news that samba 4 is now supporting user lockouts after bad password attempts we need to plan our roadmap on migrating from Samba 3 to samba 4. We currently have Samba version 3.0.7-1.3E.1 installed with (passwd) database as a backend. I would appreciate if anyone can guide me on the migration process. Our old server Centos 4.4 Samba 3.0.7 (Master browser)

I have installed RedHat ES 3.0 It came with samba 3.0.0-14.3E.i386 I have no SWAT. Which one can I use? I downloaded samba-swat-3.0.0-1.test.rh90.i386.rpm and an rpm -i said it needs: samba 3.0.0-1.test.rh90 I downloaded samba-swat-2.2.7a-8.9.0.i386.rpm and an rpm -i said it needs: samba 2.2.7a Which SWAT do I need and where can I download it? thanks, in advance. Dean

I wouldn't normally hurry you guys about a package release, (because you're doing an excellent job), but any eta on the above? samba-3.0.9-1.3E.1 is in the current repos and that install seriously fubar'd my ADS + winbind setup. samba-3.0.9-1.3E.2 (which requires krb5-libs-1.2.7-31) fixes the problem. NB, samba-3.0.7-1.3E.1 (the old version) was fine for me, its only this

All, Smbpasswd -j DOMAIN is no longer the way to join a Windows domain instead one needs to use net join. However, net utility, although it's a part of Samba release, is not present on the system. Samba was installed using rpm packages. Here is what's on the system: samba-3.0.9-1.3E.1 samba-common-3.0.9-1.3E.1 samba-swat-3.0.9-1.3E.1 Any thoughts? Thanks, Jarek

I am currently running Red Hat v 3 samba rpm's. samba-common-3.0.9-1.3E.14.3 samba-3.0.9-1.3E.14.3 samba-client-3.0.9-1.3E.14.3 I would like to run the current release version to see if I can clean up some of the problems I am having. File locking and not releasing are the most troubling. I am looking for advice for executing this upgrade without breaking too much, such as,

--- Weitergeleitete Nachricht / Forwarded Message --- Date: Wed, 3 Dec 2003 15:48:13 +0100 (MET) From: "Thomas Bork" <knuffelmail@gmx.de> To: Jeremy Allison <jra@samba.org> Subject: Re: [Samba] fcntl lock failed at large offset: pretty urgent Hi Jeremy, > > More info of setup: > > The version of Samba I have is a precompiled Debian package, and > >

Hi ALL, I recently withed from CentOS 3 X server to CentOS 4.5. It works fine other than printers. there are many printers connected to it. We have configured the commnad printconf queue type is Networked UNIX (LPD) Some times, we will be able to print , But, some times, We will NOT be able to print. We can ping its ip address. Even, when we can't print, We can ping its ip address.

Hi All, [2005/04/11 11:26:58, 0] smbd/service.c:make_connection_snum(620) '/tmp' does not exist or is not a directory, when connecting to [IPC$] This wierd and wacky thing has just started for no apparent reason no upgrades were done no system mods were performed, the file server is just never played with except to add shares, testparm says all OK. This also happens when a user

Debian Woody with security updates Linux kernel 2.2.25 Samba 3.0.0 libc6 2.2.5 The problem I have is with a windows application that uses samba. This application is crucial for the organization, so if this is not fixed, and soon, we will have to ditch Samba and move to a windows server. I *really* don't want to do this, as Samba has been working so well for years now and billg is rich enough

David A. Morrow wrote: >Hi all. I wonder if someone might be able to help with an issue which has recently begun plaguing >my network. All of my Linux machines are configured as domain member of a Windows 2000 Active Directory domain. Up until recently, all of these boxes were working correctly but all of a sudden, they have all stopped. All are Redhat Enterprise 3. All are using

I am using Samba with Active Directory. I have successfully joined my Samba server to the domain D1 ( net ads join -U username@D2.DOMAIN.COM ). I am able to succesfully connect from Windows XP clients ( with no password ), but not from Windows 2000 ( even when specifying a password ). With w2k, I always get "Failed to verify incoming ticket!". I think it has something to do with

I'm running samba-3.0.9-1.3E.3 and the manpage for smb.conf does not mention anything about 'map to guest = Bad Uid'. However I did add the line 'map to guest = Bad Uid' an run 'testparm /etc/samba/smb.conf'. No complaines but 'testparm' removes the entire line 'map to guest = Bad Uid' from the config file. Hmmmm???

Hi there, anybody here to help me with: "user_info->client_domain.str" and "user_info->domain.str" Problem: check_ntlm_password: Checking password for unmapped user [FRSTPRV.DE]\[SambaAdmin302]@[HEARTOFGOLD] with the new password interface check_ntlm_password: mapped user is: [FRSTPRV]\[SambaAdmin302]@[HEARTOFGOLD] Where from does samba receive the

Hello all, I am having some serious problems getting winbind to recognize secondary group memberships. I have a samba server version samba-3.0.0-14.3E running on RHES v.3. This is running on a 2x Xeon 2.4 Ghz IBM Server with 2G Ram. nscd is not running. See below for smb.conf. cat /proc/version: Linux version 2.4.21-9.ELsmp (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.3 20030502