similar to: using tinc in a mixed ipv4/ipv6 network

On Sat, 16 May 2015, Guus Sliepen wrote: > On Sat, May 16, 2015 at 12:09:52AM +0200, Sven-Haegar Koch wrote: > > > This change is not so good: > > > > Connection with aaa_vpnhub1 (1.2.3.4 port 443) activated > > Error while translating addresses: ai_family not supported > > > > (And then the tinc process exists) > > Hm, I couldn't reproduce

I compiled the 3.0.21a samba software with the following configure options: configure --prefix=/opt/samba --exec-prefix=/opt/samba --with-krb=/usr/krb5 --with-smbwrapper --with-syslog --with-mandir=/usr/man --with-winbind Everything compiled fine; however, I am unable to see the server on the microsoft network. My smb.conf file looks like the this: [global] workgroup = CAREMARKRX

Hi tinc list members, There were some problems with Ivo's email adresses (both zarq@iname.com and zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list. ============================================= Hi Ivo, Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere troepjes zoals een tincd scheduler. Dit werkt wat beter, omdat de

Greetings, I'm using rsync to keep multiple nfs filesystems on two emc nfs serves in sync. Here are the six file systems and their info: Filesystem kbytes used avail capacity Mounted on Number of files burd1p0:/nettmp 258120 37144 220976 15% /nfs/burd1p0/nettmp 2102 burd1p0:/user 29443776 16160480 13283296 55%

Recently we have been having a lot of trouble with time synchronisation between our samba DC and the domain clients. We are not sure what started this issue since the Samba domain went live on October 11, 2016 and the issues only began to surface this past January but at some point the time on the clients and the DC diverged enough that we began to get strange network errors. Once we figured out

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

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.

Hi all Bear with me on this one... We have a problem connecting to a specific port via Oracle TNSPING There are two PC's in our office that are on the same network as the server (i.e. my desktop PC can not get to the server) The server has multiple network interfaces, the primary is a gigabit fibre card on IP xx.16. The secondary is a megabit card on IP xx.80 The tnsping command fails

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

Hi Ivo, --On Freitag, 23. Juni 2000 01:15 +0200 Ivo Timmermans <zarq@icicle.yi.org> wrote: > I'm not sure I fully understand your patch. This is not so important since I'm trying to get 1.0pre2 running. Although I had no luck so far, I'll point out what's going wrong at the end of this mail. > For instance, you force a > key exchange when the connection is made,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm running stock FreeBSD with services running: samba (connections allowed only from local network), lpd (same), bind (all interfaces), apache (all), zope (local) This machine is home gateway/http/printserver. Recently some strange things happened as my printer all of sudden started to print stuff when nobody prints... luckily (or

On Fri, 15 May 2015, Guus Sliepen wrote: > On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote: > > > Another strange and difficult to understand thing - seems like all the > > easy bugs in 1.1 are gone ;) > [...] > > Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak > > -> igor which does not match existing entry (Local

win2k/XP clients can access this fine, but not NT clients. Samba is listening on the netbios-dgm/ns ports and there's no packet filtering: udp4 0 0 atarashii.netbios-dgm *.* udp4 0 0 atarashii.netbios-ns *.* udp4 0 0 *.netbios-dgm *.* udp4 0 0 *.netbios-ns *.*

>>> > Considering any editing/buffering benefits are only marginal (AFAIK) there are not benefits with the current approach.On the other hand the list of potential problems includes: > 1) We cannot use the ubiquitous EFI PXEbc protocol forcing us to rely on the (not always present) EFI Binding Services. > Best,Patrick Speaking utterly ignorantly here... could this switch help

Hello, I've been trying to get a solution (or at least an explanation) from the FreeBSD guys at freebsd-questions lists, but I guess no one knew the answer. I am trying to run Samba 3 (latest) in a FreeBSD 7.0 jail (http://en.wikipedia.org/wiki/FreeBSD_Jail). It seems I cannot convince Samba to answer NetBIOS broadcast requests and therefore Windows machines cannot browse it directly by name

> - Indirectdata finally REALLY REALLY works now! > - More precise debug messages Hmmm ... I can't prove that using the CVS code I checked out this morning. Everything works like yesterday: I can ping the peer but I canot go beyond: *** SERVER *** Jun 27 09:04:56 lemon tinc.9[10186]: tincd 1.0pre3 (Jun 27 2000 08:53:56) startin g, debug level 4 Jun 27 09:04:56 lemon tinc.9[10186]:

On Tue, 2017-02-07 at 13:06 -0500, James B. Byrne via samba wrote: > Recently we have been having a lot of trouble with time > synchronisation between our samba DC and the domain clients.  We are > not sure what started this issue since the Samba domain went live on > October 11, 2016 and the issues only began to surface this past > January but at some point the time on the clients

On Tue, February 7, 2017 13:06, James B. Byrne wrote: > In any case, we have resolved most of these issues. In dealing with > this I ran across > https://wiki.samba.org/index.php/Time_Synchronisation which contains > this instruction: > > Set up the ntpd.conf File on a DC > . . . > ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/ > > Now, on the FreeBSD host I

http://bugzilla.mindrot.org/show_bug.cgi?id=401 ------- Additional Comments From yoshfuji at linux-ipv6.org 2003-01-06 12:20 ------- Created an attachment (id=194) --> (http://bugzilla.mindrot.org/attachment.cgi?id=194&action=view) patch to run openssh-3.5p1 on linux-2.2 & glibc-2.2(or later) This is modified patch for openssh-3.5p1. Patch is simplified. ------- You are

Hello, I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und IPv6 in order to be able to have Samba acting as IPv6 DNS Server. However since I have problem with sysprep domain join as soon as Samba advertises its own Domain Controller Hostname as IPv4 and IPv6 address, I would like to tell Samba to run on both protocols but only resolve to an IPv4 address. So in short: When I