similar to: Workstation member server dhcp changing ip

Displaying 20 results from an estimated 20000 matches similar to: "Workstation member server dhcp changing ip"

2015 Nov 15
1
Workstation member server dhcp changing ip
On Sun, Nov 15, 2015 at 10:29 AM, Rowland Penny < rowlandpenny241155 at gmail.com> wrote: > On 15/11/15 18:17, Lee Brown wrote: > >> Hi all, >> >> I have a working Samba 4.2.4 AD domain on FreeBSD 10.1-releng (DC's) and >> 10.2-stable (workstation). Internal DNS. >> >> I just joined my workstation to the domain and all is great, but when I
2015 Jul 11
2
Problem with Samba 4.2/FreeBSD10.1
Hi Everyone, my first foray into Samba and AD both. Not sure if this is an OS or configuration problem. I've found similar issues, but nothing either recent enough (is related to samba 3) or close enough. FreeBSD-10.1-RELENG, Samba 4.2.2. I have the domain provisioned as rfc2307 I have joined a Win7-virtual machine to the domain I have created a new user with ADUC I have assigned 10000 to
2015 Jul 11
1
Problem with Samba 4.2/FreeBSD10.1
On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.
2015 Dec 16
2
samba4 schema for openldap
On Wed, Dec 16, 2015 at 12:40 PM, Таболин Юрий <tabolin at speechpro.com> wrote: > 16.12.2015 22:47, Rowland penny пишет: > >> On 16/12/15 19:35, Rowland penny wrote: >> >>> On 16/12/15 19:02, Таболин Юрий wrote: >>> >>>> Hi all. >>>> >>>> I have samba 4.2.3 on freebsd 10.1 server. There are three DC and about
2012 Jun 16
2
SA-12:04 commit on RELENG_8_1 incorrect?
Hi, This was the commit of SA-12:04.sysret to RELENG_7_4, which makes sense to me: http://svnweb.freebsd.org/base/releng/7.4/sys/amd64/amd64/trap.c?r1=216618&r2=236953 But when it was applied to RELENG_8_1, it looks wrong, as if it was applied in the wrong place. The indentation is broken, and the code inserted looks like it wouldn't be effective:
2008 Dec 04
1
rc.firewall: default loopback rules are set up even for custom file
I've just realized that I see in releng/7 something that I did not see in releng/6 - even if I use a file with custom rules in firewall_type I still get default loopback rules installed. I think that this is not correct, I am using custom rules exactly because I want to control *everything* (e.g. all deny rules come with log logamount xxx). -- Andriy Gapon
2015 Jul 11
0
Problem with Samba 4.2/FreeBSD10.1
On 11/07/15 04:06, Lee Brown wrote: > Hi Everyone, my first foray into Samba and AD both. > > Not sure if this is an OS or configuration problem. I've found similar > issues, but nothing either recent enough (is related to samba 3) or close > enough. > > FreeBSD-10.1-RELENG, Samba 4.2.2. > > I have the domain provisioned as rfc2307 > I have joined a Win7-virtual
2012 Nov 27
1
virtio for 9.1-R
Hi guys, I can't see virtio in releng/9.1, is there any particular reason why it isn't going to be included given that it works reasonable well (and is optional anyway, so not likely to be detrimental)? Thanks, Joe
2020 Jun 29
3
R 4.0.0 rebuild status
On Mon, 29 Jun 2020 at 14:25, Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > > Again you guessed right, that was the main idea. :-) > As I told above and to reiterate it, the idea of this work is to make it easier to automate the > process. Similarly to how we do the mass builds for all the packages. But the mass rebuild process is very different, because releng doesn't
2019 Jul 16
2
Trouble getting Roline/Powercom UPS recognized
Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at
2013 Aug 07
1
Some missong patches in 9.2-RC2
Hello, I went through my local patches against base/releng/, 9.2 in that case. There are some fixes which are noct in 9.2-RC1: - Regarding kerberized builds: http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043902.html - Regarding mfi and >2TB corruption, seems MFC reminder failed http://www.freebsd.org/cgi/query-pr.cgi?pr=173291 - Regarding mount failok (seems r230226 got lost?)
2009 Jan 02
1
FreeBSD 7.1 svn186551
Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english
2013 Jun 19
2
sshd didn't run after upgrade to FreeBSD 8.4
The version of sshd in FreeBSD 8.4 is not backward compatible with older version from 8.3. OpenSSH_5.4p1 (on FreeBSD 8.3) OpenSSH_6.1p1 (on FreeBSD 8.4) # sshd -t /etc/ssh/sshd_config line 19: Missing argument. On line 19, there is: VersionAddendum It was OK in older versions. It will remove any default text appended to SSH protocol banner (for example 'FreeBSD-20120901'). On
2017 Aug 03
2
pam auth problem
> What is in the pam.d/dovecot file? (Remember to strip passwords if > included) # cat /etc/pam.d/dovecot passdb { driver = pam # args = failure_show_msg=yes # args = max_requests=12 args = %s } and /etc/pam.d/{imap,pop3} were untouched; both as follows # # $FreeBSD: releng/10.3/etc/pam.d/pop3 170771 2007-06-15 11:33:13Z yar $ # # PAM configuration for the "pop3" service
2003 Oct 04
1
Security Fix Confusion
Hi, I'm wondering if anybody could enlighten me about the effect of tracking RELENG? When the Openssh advisory came out (SA-03:12) I allowed a few days for all issues to get ironed out and then used CVSUP to rebuild my boxes with RELENG_4_7 or RELENG_4_8 (as appropriate). The advisory says that the problem with OpenSSH is fixed by 4.7-RELEASE-p16 and a 'uname -a' of one of my 4.7
2016 Jul 15
5
Samba-4.3 on FreeBSD-10.3
I have created a Samab AD-DC on a FreeBSZD-10.3 host. The setup checks out and I am able to join the domain from a Win7 workstation and run the ADUC management console in RAST. I have opened the UNIX Attributed properties tab for "Domain Admins" in the ADUC and set the unix properties. However, I get this notice "UNIX Attributes Unwilling To Perform" and after making the
2012 Aug 23
11
FreeBSD 9.1-RC1 Available...
The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current
2006 Jan 13
1
FreeBSD Errata Advisory FreeBSD-SA-06:03.cpio
Hi there, I'm following the security advisory to patch the cpio vulnerability (update to 6_0_0 RELENG p2, make obj, make depend), yet when it comes to make, it shows some error message as follows: /usr/src/gnu/usr.bin/cpio/../../../contrib/cpio/copyin.c:536: error: redefinition of 'safer_name_suffix' /usr/src/gnu/usr.bin/cpio/../../../contrib/cpio/copyin.c:488: error: previous
2013 Sep 27
1
9.2-RC4 amd64 panic: vm_page_unwire
I'm running 9.2-RC4 on a handful of desktop and server machines (both i386 and amd64). I have seen three panics (all vm_page_unwire) on one of those systems only (amd64 server) during the past week. The first two panics were triggered when shutting down the ntpd daemon (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a later release (p388) has not triggered the panic.
2007 Jul 23
1
sudo + pam_lastlog causes user to appear logged out in logs.
Hi, this was originally reported on ports@. [1] Someone noticed that after after running sudo their session disappeared when running `w` afterwards. I've done a little experimenting and this is caused when pam_lastlog.so is included in sudo's pam file. This results in the user still being logged in though according to the system logs the user has logged out. Here's an example: