similar to: How to delete a printer

smbldap-tools-0.9.1-1 & Samba 3.0.21a This is what I have in my smb.conf: passwd program = /opt/IDEALX/sbin/smbldap-passwd "%u" passwd chat = "*New password :*\n" %n "*new password :*\n" %n unix password sync = Yes According to "man smb.conf", smbldap-passwd is invoked as root so the passwd chat should be fine. Problem is it

Some of Shorewall''s features manipulate routing tables. Linux removes routes involving interfaces that disappear (namely pppX). When these interfaces are restore the routing tables are not restored. Just wondering how people are dealing with this situation.

Been trying to run this on FC3 pulling stuff off a NT4 PDC - it just segfaults on 3.0.21 & 3.0.21a I'm building the RPMS from the tar ball on the host using the makerpms.sh script Reverted to the 3.0.10 issued by Fedora and no segfault. From what I can see (with strace) it segfaults while reading from the socket connecting the PDC - not the first read, but after quite a few

1. The printers are Samba/CUPS. 2. Clients are Windows XP Pro & 2000 Workstations. 3. "Access denied, unable to connect" appears in the printers window on the clients - nearly always. Very occasionally, it displays what it's supposed to. 4. Seems to be a cosmetic problem since it does not affect actual printing. 5. Can some guru advise what level of debugging to

Do these programs still exist? They don't seem to be part of the samba3x package on RHEL5.

There has been a low continuing level of confusion over the terms "Source NAT" (SNAT) and "Static NAT". To avoid future confusion, all instances of "Static NAT" have been replaced with "One-to-one NAT" on the web site and in the CVS configuration files (Shorewall/ project). The documentation in 1.4.9 will also contain this change. -Tom -- Tom Eastep \

Hi, especially John H. T :) I'm yet again plodding through chapter 14 of the Samba-HOWTO-Collection.pdf. Not because I can't make what's in it work for me, I did that long ago, I found out for myself, because a great deal of what's in it is wrong. I just got fed up with trying to get Nagios to work - I gave up, for various reasons and started on the Samba doco. At the risk of

Environment is Samba as a PDC, OpenLDAP backend, with smbldap-tools providing the scripts to manipulate the data. What are the recommended/mandated organizational units (OU=) for user, computer, group info. I'm pretty sure that groups go in ou=Groups, but I am confused about where user and computer data goes. I have seen ou=People, ou=Computers, and ou=Users in various places. Which is it

This is some ramblings on why using proxy ARP (on a host in a DMZ) is a good or bad thing. The good is that a computer X retains a public IP address which makes it easy to connect it directly to the net if the firewall has to be taken down for extended periods. Thus, if computer X is a mail server for example, it can still function in a reduced capacity until the firewall is restored. The bad

Hi All, Yesterday, I've upgraded my Samba server from 3.021c to 3.023 through yum upgrade samba*. I'm running Fedora Core 4 Kernel 2.6.17-1.2142 on this server. After upgrade has been completed, I lost the attributes of ownership and groups. I noticed that the uids/gids have changed for all AD accounts. This means that users can't have total access for their files and no access

On the firewall, what is the rationale for giving eth1 an IP address that is also assigned eto eth0? (Rather than a private one.) -- Taso Hatzi caesar 17 <<-salad cjbx jc vdwwjar jc xi jc jd salad

The problem scenario I describe was reported previously in the Shorewall lists but its resolution does not seem to have made it into the lists. Scenario: Windows XP client seeking to establish a VPN connection to a Windows 2003 Server located behind a Shorewall firewall (running on Mandrake kernel 2.4.22-37mdk). The connection cannot be made, the client reports error code 721. Discussion:

hello when I try to connect to a share from my windows xp client, it does not work. In linux via smbclient, there's no problem. see below for the error log version = 3.0.21a security = server (the problem only seems to occur on servers that rely on another samba server for authentication). any ideas? werner [2006/01/27 09:30:32, 2] auth/auth.c:check_ntlm_password(307)

We have 2 Samba Domain Controllers and 1 Samba Domain Member Server, running on Solaris 9. The Solaris servers are native LDAP clients to two OpenLDAP servers. All user-info is available on these servers (getent passwd). Before upgrading to Samba 3.0.21a, we were running Samba 3.0.14a. On the Domain Member Server, when selecting the security-tab of a file or folder, the users were listed as

Is there a trick to being able to access shares via \\domain\dfsroot\.. rather than \\computer\dfsroot\... ? Only the latter works for me - samba 3.0.22

Scenario: a) Samba with an ldap backend. b) The ldap database becomes irretrievably corrupted. c) I roll in a new ldap database from a known good copy. d) Problem is the passwords for the machine accounts are out of date. e) Is it possible to coax Samba & the clients (mostly XP) to resynch their passwords? f) I want to preserve the client computers SIDs & names. g) I really

Samba 3.0.21b with LDAP backend The transfer to the Sanba hosted domain appears to work, ie success message, but I can't log on to a domain account from that workstation, complains about missing machine account or incorrect password. Only NT4 workstations seem to be a problem, Win2k and XP are Ok. NT4 is maximally patched, updated and etc - no registry hacks however. I checked the LDAP

I have been having a problem with 'net getdomainsid' on a machine that I set up to be a BDC. # net getdomainsid Could not fetch local SID tdbdump shows that there is no machine SID in secrets.db, so I'm thinking that I overlooked the step that creates a machine SID. What creates the machine SID and when? Also, is it the hostname or the netbios name that samba uses as the machine

Are there any scenarios that require traffic from a zone to itself to be blocked? If not, Shorewall should possibly allow it as a matter of course. It seems strange having to explicitly create such a policy & it''s not immediately obvious when it is required. -- Taso Hatzi caesar 17 <<-salad cjbx jc vdwwjar jc xi jc jd salad

I don''t think this has anything to do with Shorewall but I am not too familiar with iptables stuff yet so I''m not sure. Running Shorewall shorewall-1.4.9 on Mandrake Linux release 9.2 (FiveStar) for i586 Kernel 2.4.22-37mdk. Run "nmap -sP 192.168.x.x/24" (for example), where 192.168.x.x/24 is the LAN. You can do this from a firewall/router, or even from a