similar to: Swat shows smbd as not running when it is and had worked fine the day before.

I am sure that I don't quite have LDAP setup with the proper Samba entries, but I only need a "bread crumb" to get me pointed in the right direction. Where do I find some information on how and where to place the sambaGroupMapping, sambaUnixIdPool, sambaIdmapEntry (automatically created?), and sambaSidEntry in the LDAP tree. Could someone just give me a little hint as to where the

I can NOT find any information on how to get the following into the LDAP tr= ee (and where they should be located) from the documentation. I am definite= ly an LDAP beginner and assembling the tree from reading schema's is still = over my head. I am able to connect to samba using only LDAP authentication = and can add users, but that is all I can successfully do, "net groupmap add=

Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. >From that point (but maybe it is

hi all, I just installed samba 2.2.0 on a Digital SMP server and I can tell that administering it via SWAT is the bigest step since man walking on the moon. but... SWAT eroneously reports smbd/nmbd not working while they are working. And even more, the smbd/nmbd [start]/[restart] buttons have dissapeared. Why is that ? Claudiu premises: hardware: Digital server 2xPII 266/128MB/2x4GB SCSI

I am having a problem with my Samba machine, here are the details. The machine in question is running FreeBSD 4.5-RELEASE on a Dual PIII/XEON 550. I downloaded the source for Samba-2.2.3a and compiled without a hitch. I also setup SWAT to run through an stunnel(ssl) pipe. SWAT configuration of Samba worked great, but if I start the daemons(smbd & nmbd) from SWAT, smbd seems to keep creating

On May 25, 2010, at 8:25 PM, Whit Blauvelt <whit at transpect.com> wrote: > On Tue, May 25, 2010 at 07:55:12PM -0400, Whit Blauvelt wrote: >> On Tue, May 25, 2010 at 04:33:53PM -0700, Jerry Franz wrote: >> >>> Are you running with SELinux on? > > You were right Jerry! > > echo 0 > /selinux/enforce > > and then /etc/init.d/smb restart works! Thank

Hi, I downloaded the binaries for samba yesterday for redhat 9.0, and installed them without error. Managed to get swat up and running and configured samba, the same way I configured my other linux (slackware 10.2) box, and started samba thru swat. But when the status page reloads, it shows smbd and winbindd as not running, although it shows nmbd running. When i check the ps list, it shows

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

Update: I tried with 2.0.21 and this also works just fine. So it must be something which came in with 2.1.x PS: Where is the documentaion for 2.1.x - i.e. for all the nice additions Timo made? The Website "only" has 2.0.x, as far as I can tell? (might be wrong here - hadn't touched the whole thing for a while, as my "civil life" had occupied me :-) Greetings, Clemens

All, I had updated to 1.2.4 right when it came out. I had been working just fine. Today I seem to be having recuring seg faults. can explain it. How can I find why? Anyone else experiencing this? I am running (2) TDM04B cards (has been working since 1.0.9) I have a handfull of UIP200 phones and 1 cisco 7960. I have a unused broadvoic connection that I commented out the registration statement

Hello, I wanted to relaunch my problem with a quite precise and small question. Could the command "lsusb" affect interrupts when executing it regularly (cron) and if the zaptel pci card is sharing an interrupt with a usb bus? I have a Digium PRI card and a few Xorcom USB Devices. The Digium card seems to share the IRQ with some USB bus. cat /proc/interrupts CPU0 CPU1

Hi folks; I have an odd one. I recently upgraded from 3.3.x to 3.4.3 and suddenly lost both the old "smbpasswd" file AND the ability to connect to printers from Windows 7 clients. File server is fine, and everything else is working - I can connect to printers from XP machines, but not from Windows 7 any more. I get an "0x00000000d" error from Win7 when I try to connect....

Ok, here's a toughie: Out of a whim (and because of the bad weather) I today decided to upgrade my completely functioning 2.0.15 installation on my Mac OS X 10.6.7 system. NB: It's not a Mac OS X "Server", as sold by Apple - I have compiled my dovecots myself for quite a while. Anyhow: At first everything appeared to work fine after the upgrade. Up until I created a new user

On 11/06/2015 06:30 PM, Jobst Schmalenbach wrote: > What troubles me that a simple restart of the daemon fixes everything but it does not come up on reboot. Running the service script manually may not give you the same selinux context as on boot. Services should be started using "run_init" to ensure they get the correct context. I think this is legitimately the most confusing

On 11/06/2015 06:30 PM, Jobst Schmalenbach wrote: > Putting selinux into permissive mode starts the server right from boot. > Looking at all the logs I cannot see anything. Which logs? You should see AVC denies logged in /var/log/audit/audit.log, unless you've disabled audit logging. The AVCs should indicate which files are labeled incorrectly, and what their current label is. You

On Mon, Nov 09, 2015 at 06:08:11AM -0800, Mark Milhollan wrote: > It allows (even forces) a "dirty" environment to be provided to the > service (which is seldom wanted or expected), does not ensure that the > current tty cannot be the controlling tty for the service (which > sometimes matters) and leaves the CWD unchanged instead of ensuring / is > used (which

Our Samba server running on CentOS 5.1 (upgraded from 5.0) with Samba 3.0.25b-1.el5_1.4 has been in place for about a year and a half. We had no issues till about 2 months ago. This may have coincided with the upgrade of CentOS 5.0 to 5.1 (which would have brought a new Samba version with it). Anyway, the server will be fine and snappy for a week or so, then out of the blue, nobody can

On Sat, 7 Nov 2015, Fred Smith wrote: >On Fri, Nov 06, 2015 at 07:23:59PM -0800, Gordon Messmer wrote: >>On 11/06/2015 06:30 PM, Jobst Schmalenbach wrote: >>>What troubles me that a simple restart of the daemon fixes everything but it does not come up on reboot. >> >>Running the service script manually may not give you the same >>selinux context as on boot.

Hi. I am stuck with this one and I do not know where and how to search for this problem nor do I know how to fix it. When I reboot one of our servers (CentOS 6.7, selinux target, yum fully updated) the http server loads fine (no erros) but when accessing one of the server's websites it displays "Forbidden", restarting the httpd server (command line) will give full access and all is

On Fri, Nov 06, 2015 at 07:23:59PM -0800, Gordon Messmer wrote: > On 11/06/2015 06:30 PM, Jobst Schmalenbach wrote: > >What troubles me that a simple restart of the daemon fixes everything but it does not come up on reboot. > > Running the service script manually may not give you the same > selinux context as on boot. Services should be started using > "run_init"