similar to: Anaconda: inst.repo doesn't work.

On 02/04/2015 04:06 PM, dE wrote: > Although you can choose this in the installer, isnt the provided values > supposed to be the default? > > I tired the following > > inst.repo=hd:/dev/sdb1:/repo > > Result: /dev/sdb1 is not mounted. > > inst.repo=nfs:[fc00::6009]:/home/auser/repo > > Result: NFS is not mounted even the correct ip is set by passing ip=

hello, the topology is like this: centos v0:eth1 <------> centos v0: eth2 fc00:2:3:4::1 fc00:2:3::4 i turned the packet forwarding ping6 -i eth2 fc00:2:3:4::1 the output is PING fc00:2:3:4::1(fc00:2:3:4::1) from fc00:2:3::5 eth2: 56 data bytes >From fc00:2:3::4 icmp_seq=1 Destination unreachable: Administratively prohibited >From fc00:2:3::4 icmp_seq=2

Am 05.10.2016 um 22:12 schrieb Rob via samba: > On Tue, 4 Oct 2016, Rowland Penny wrote: > >> This is very strange, have you tried running 'net cache flush' on the >> domain member ? >> >> Have you compared the users AD objects ? > > Running 'net cache flush' on the member does fix things, albeit only > for a while: > > # wbinfo -i

On Tue, 4 Oct 2016, Achim Gottinger wrote: > Am 03.10.2016 um 18:57 schrieb Rob via samba: >> [...] >> >> This generally works fine... user mappings are like: >> >> $ wbinfo -i auser >> auser:*:10028:10000:User Name:/home/auser:/bin/bash >> $ id auser >> uid=10028(auser) gid=10000(agroup) groups=10000(agroup),10007(othergroup) >>

Hi all, I've been experiencing an intermittent problem where some UIDs on a member server spontaneously change from being their AD-derived values to being allocated from the default idmap space, even when there is no change to the AD user information. Specifically, I have a member server running Samba 4.4.5 on CentOS 6.8. AD service is provided by two Samba 4.4.5 servers. The member

Hi, I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5 bringing across all the user accounts. The samba 3.6.23 we set up with smbldap as an NT Domain with OpenLDAP. After a lot of effort the classic upgrade worked well but now I'm a bit stuck with idmapping. The new AD DC is running 4.6.5 on CentOS7 and I can connect using ADUC. I set up a separate AD DM on a another CentOS7

On Tue, 4 Oct 2016 02:35:21 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 03.10.2016 um 18:57 schrieb Rob via samba: > > Hi all, > > > > I've been experiencing an intermittent problem where some UIDs on a > > member server spontaneously change from being their AD-derived > > values to being allocated from the default

On Tue, 4 Oct 2016 15:16:17 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 10:21 schrieb Rowland Penny: > > On Tue, 4 Oct 2016 02:35:21 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 03.10.2016 um 18:57 schrieb Rob via samba: > >>> Hi all, >

On Wed, 5 Oct 2016 16:12:41 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > On Tue, 4 Oct 2016, Rowland Penny wrote: > > > This is very strange, have you tried running 'net cache flush' on > > the domain member ? > > > > Have you compared the users AD objects ? > > Running 'net cache flush' on the member does fix things,

On Tue, 4 Oct 2016 12:29:19 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > > On Tue, 4 Oct 2016, Rob wrote: > > > On Mon, 3 Oct 2016, Rowland Penny wrote: > > > >> On Mon, 3 Oct 2016, Rob wrote: > >>> # idmap config for domain > >>> idmap config MY.AD.REALM.COM:backend = ad > >>>

Ubuntu 8.04lts Dovecot 1.2.6 So, further to the 'deliver' problem posted yesterday I've also discovered another issue regarding permissions: files and directories are being created 0600/0700 by the IMAP and deliver process (depending on who gets there first!) preventing use of shared mailboxes. According to documentation: "When creating a new mailbox, Dovecot v1.2+ copies the

On Tue, 4 Oct 2016 16:09:40 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: > > On Tue, 4 Oct 2016 15:16:17 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 04.10.2016 um 10:21 schrieb Rowland Penny: > >>> On

Hi! I installed CentOS 7 today, it's a minimal install, so it didn't have ifconfig command. So I installed net-tools, however I can't add ipv6 address to it. # ifconfig enp0s3 add fc00::1002/124 SIOCSIFADDR: Permission denied. Yes, I'm running as root. CentOS is running in a Qemu instance with e1000 ethernet card.

I have a samba PDC running 2.0.20c I installed Samba 2.0.23 on a client joined to the domain. With this combination, when I attempt to connect to a share on this client from any host even the localhost results in the following: $ smbclient //localhost/atest -U auser Password: Domain=[DOMAIN] OS=[Unix] Server=[Samba 3.0.23-SerNet-RedHat] tree connect failed: NT_STATUS_ACCESS_DENIED Windows

I *think* I may have encountered a bug, or a feature, in the idmap/winbind area. I have recently added rfc2307 attributes to my AD, and am in the process of switching over. This means that I still have (unintentionally) some files/directories/etc. around with old UIDs e.g. 3000007, rather than my rfc2307 specified UIDs. What I am seeing is that the SID2XID mapping is initially correct for a

Hi there, I set up my company's back up server using rsync. And I've got a strange problem. I searched in the archives of this list, but none of them seems not giving me an idea to solve the problem. If anyone can help, it would be grateful. I'm using cron by a user (non wheel/admin) to rsync everyday during the night. The cron is set in the server to transfer the backing-up

https://bugzilla.netfilter.org/show_bug.cgi?id=1188 Bug ID: 1188 Summary: nft fails to parse own output; unable to save-restore active state Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft

hi all! back in Aug several of you assisted me in solving a problem where one of my drives had dropped out of (or been kicked out of) the raid1 array. something vaguely similar appears to have happened just a few mins ago, upon rebooting after a small update. I received four emails like this, one for /dev/md0, one for /dev/md1, one for /dev/md125 and one for /dev/md126: Subject: DegradedArray

So I had dhcp, radvd and bind working together nicely and now I threw in a wrench of setting up an AD DC I want to change my dhcp server setting to put client's into the new AD Domain but am a little hesitant as it is all working so nicely with DDNS I'm starting to think all I need to do is edit just my dhcpd.conf and change occurrences of DOMAIN1.SUBDOMAIN.TLD to

Hello, Firstly THANK YOU for the IPv6 NAT support merged in 6.5. It has been almost impossible to get IPv6 into a VM on a laptop that switches between wifi and wired (dock) connections, because you can not add a wifi interface to a bridge. I know NAT is against the IPv6 end-to-end xen but it makes this "just work" for the vast majority of people like me who need to ssh/curl/talk to