similar to: Why isn't "<Domain>\<User>' = to <User> on PDC? Isn't it supposed to be?

Emmanuel Florac wrote: > id TESTAD\\testuser > returns "no such user" and > > getent passwd TESTAD\\testuser > > returns a "2" code. > ---- On linux, to get 'domain\user' to resolve, I had to have those entries in my /etc/passwd (and /etc/group for groups). I.e. *w/o krb*, (in samba 3.x), I had entries like:

Linda Walsh <flac at tlinx.org> wrote: ... > That brings up another question then... What is 'hi' (v. low?)... Zero, or close to zero, is low. 12 is high. ... > What's a subset stream? This is explained at: http://flac.sourceforge.net/format.html in the bulleted point beginning, "FLAC specifies a subset of itself as the Subset format." ... > Another

I've been getting these in my log for some time and was wondering what I had to do to get 'pam_winbind' to 'work' with my samba 'DC'? In looking around the net, others w/this error message were having a problem with blocking login's and password changes, completely. In my case, I have the 'pam_winbind.so' module in '/etc/pam.d/common-passwd' setup

I'm trying to use 'ssh' as a domain user from a workstation into my server. When I ssh as a non-domain user, it doesn't tack on a domain (or workstation) name, so it just works, but when I log in from from my Samba domain, it tacks it on (and the linux security stuff doesn't like "domain\" either. Should the pam_winbind module be able to authenticate this type of

Among various problems since I upgraded to 3.6 (none of which got answered really, -- so I backgraded to 3.5.10 and started debugging from there, considering 3.6.0 too unstable/too incompatible for 'whatever' reason... One of the probs I had was 'root' couldn't use "net rpc" <anything> -- kept getting auth failures. Wasn't the passwd, -- could reset it via

It would be 'nice' if there was an option for rsync to ignore case -- Windows is real lax about what case files are, and often files will end up with different cases depending on what util installed a font last. When you transfer to linux, you end up with 2 (or more) copies of files with different case(s). Sometimes only the extension is different case, thus resulting in more than 2

In the smb.conf manpage, there is a notation used, (G) or (S) for global or share. Does (S) mean it can only be used in a Share section (i.e. - will be ignored in the global section), or is that they *can* be applied at the share level, and, possibly set a default in the 'G'lobal section? example: "ea support = yes" Seems like that could mean that extended attrs are

Emmanuel Florac via samba wrote: > Unknown parameter encountered: "winbind enumerate users" > Ignoring unknown parameter "winbind enumerate users" > Unknown parameter encountered: "winbind enumerate groups" > Ignoring unknown parameter "winbind enumerate groups" It may be irrelevant, but I have: winbind enum groups = Yes winbind enum users

"Linda A. Walsh" <flac at tlinx.org> wrote: > what does the exhaustive model search do? I am not an expert on the guts of FLAC, but there is some information about this at: http://flac.sourceforge.net/documentation_format_overview.html and scroll down to "MODELING". > Does it try all of the functions listed under "-A" to find the 'best', >

Why is someone not setting up an email server conform RFC's and seems to be you have an ipv6.. so set the ptr record. Hai Linda, I do have ipv4 and ipv6 on my server, and im never blocked.. but i did setup conform all rfcs.. i block servers in the same way. so yes, i did set my reverse for ipv4 and ipv6.. what most people do wrong.. 1) the hostname must have A and RR (PTR) and MX

Yves Goergen wrote: > The issue still exists. Can anybody explain to me why dovecot creates > IMAP folders with the wrong filesystem permissions? On a lark, I looked through my dirs @ permissions. Shorted lines a bit so they'd fit w/o extra lines between them using: (get rid of text before permissions, and shorten user/group to a few letter) find . -type d -ls|sed -r

On 10 November 2016 at 15:37, Linda W <samba at tlinx.org> wrote: > Erick Ocrospoma via samba wrote: > >> On 10 November 2016 at 07:51, Vinicius Bones Silva via samba < >> samba at lists.samba.org> wrote: >> >> >> >>> PROBABLY its a problem with your reverse dns resolution. >>> >>> >> ​Hi, >> >> DNS

FYI, the same bug apears if one mounts the file system using "cifs": -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* Linda W wrote: > Summary: > There appears to be a bug in the "time range" Samba is using on > dates where time is scheduled to "Spring Forward"

Greeting- I have a mixed network of ms-windows, macintosh and freebsd systems. I am setting up a FreeBSD 9.0 system as a PDC using samba. I can from a FreeBSD box attach to the SMB server as a user that is defined on the Samba Server. [wynkoop at dt0 ~]$ smbclient -L hp1 Enter wynkoop's password: Domain=[HARAPARTNERS] OS=[Unix] Server=[Samba 3.6.4] Sharename Type

> We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the linux server but we are having problems with blank > passwords or the user can type any password. We are using pam modules for > the authentication on the client machines. > I have included the config files for

I hope this is the right list, as I'm desiring a feature addition in openssh. I would like the option to have a 'null' cipher (after the initial authorization, similar to 'delayed' for compression). It would have to be enabled on both client and server and server would never use it unless it was both enabled and asked for by the client. I'd strongly prefer it be able to

> -----Original Message----- > From: Reed, Tameika > Sent: Monday, November 17, 2003 5:56 PM > To: 'samba@lists.samba.org' > Subject: Samba PDC trying rid null logins > > > > > We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the

On May 1st, Chuck Sullivan posted the following: https://listman.redhat.com/pipermail/k12osn/2003-March/007755.html No mention was made of /etc/pam.d/passwd, which is what I think we need to set to enable a user to change their domain password. Our current settings are: /etc/pam.d/passwd: #%PAM-1.0 auth required /lib/security/pam_stack.so service=system-auth auth sufficient

I realized in looking at my smb.conf, I'm not using these in a consistent manner, and .... well I just don't understand what the differences are between them. Sure I can read the smb.conf page: %U session username (the username that the client wanted, not necessarily the same as the one they got). vs. %u username of the current service, if any. ---

To be honest, I can't follow you. I see that I have inconsistent permissions (but all the same owner and group). I did use a different mail server software in the past, but that's long ago and I can't even remember when I switched to Dovecot. I think it was Courier-IMAP before. Maildirs for new mailboxes are still created by one of my own scripts so maybe that script creates the