similar to: NT 4 workstation joining Samba domain

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.

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, I'm trying to setup Samba. The goal is to have my tow Linux PC's and my two Windows PC's connected together on a LAN. My setup is as follows: Router as LAN hub and Internet access, Windows 8.1 PC, Windows 7 PC, Ubuntu 12.04 LTS PC, Ubuntu 14.04 LTS PC. I have installed Sanba 3.6.3 on the 12.04 PC and 4.1.11 on the 14.04. Configured the smb.cof on

Hi, I've reported this before but I guess I'll have to do it again, since it's not fixed yet or I'm understanding something wrong here. The problem is that smbldap-useradd -w 'machinename' will add only posixAccount entrys into ldap but it should add both posixAccount and sambaSAMAccount entrys. So if one doesn't add correct machine account entrys manually to ldap

There is a program called VNC (virtual network computing -- http://www.uk.research.att.com/vnc/) which is basically an opensourced cross-platform replacement for pc anywhere type software. It's excellent. But it's authentication is lacking. It asks for a single password, and has no support for usernames (at least none that is useful to me). VNC is distributed under the GPL. Sanba has

On 11.10.2016 17:22, Harry Jede via samba wrote: > Am Dienstag, 11. Oktober 2016 schrieben Sie: >> On 11.10.2016 13:52, Harry Jede via samba wrote: >>> On 10:43:49 wrote Gavrilov Aleksey via samba: >>> Until now, you have destroyed your domain. >>> Is the ldap directory on localhost in production or is this pc in a >>> test lab? >> a copy of the

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

Migration was held in connection with the breakdown of the old server after setting up a new server stopped working to add windows pc to a domain root at pdc:/var/log/samba# cat /etc/samba/smb.conf [global] # Default options allow nt4 crypto = yes client ntlmv2 auth = no disable spoolss = yes dns proxy

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 \

I know I am getting tiresome to this list, but I can't see what I am doing wrong, which is obviously something. I am new to samba as far as setting it up as a PDC. I am not having trouble accessing sanba shares when I set my computer to be part of a workgroup, but when I try to configure samba server as a PDC, i get the following message: The account used is a computer account. Use

I have 10 computers running win98 and a Linux server. I need to control de login and logout (total time of use) on each one. Can anyone tell me if I can do it with Samba/Netlogon, and how to do that? Thank you Daniel junghans@netpar.com.br

I know these systems work with AD, the problem is the migration, I don't think is easy to migrate 5000 accounts from current systems to new systems. I will need to learn the sintaxes of all these new systems and this would take huge time because I know nothing of samba4, or AD, or dovecot, or kerberos and the boss whants the emails for students for next month. We don't plan to

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

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

A lot of administrative systems made by the institution, current domain, fileservers, glpi, cyrus mail, horde, gosa, svn, freeradius, dotproject, vcenter. Thats what I remebmber for now. Citando Rowland Penny via samba <samba at lists.samba.org>: > On Mon, 02 Apr 2018 12:09:39 +0000 > Rodrigo Abrantes Antunes via samba <samba at lists.samba.org> wrote: > >> I need

I think I have narrowed this down even further. I have been working through getting rid of error messages in the logs, and I have updated Samba to 3.4.3. This might have fixed the issue, and I won't know for some time, but I can still see the following error appearing in the logs, which seems to line up with the core issue of machine trust accounts expiring.

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