Displaying 20 results from an estimated 2000 matches similar to: "samba 4.2.1 strange connection problem"
2014 Sep 01
0
Samba 4 dns-resolv-prob with different subnets [SOLVED]
Hello all,
The prob is solved. The dns-answer only seemed to come from the asked
nameserver. Between the two endpoints of the vpn the gateways have a
transparent dns-proxy which forwarded my dns-request not the wanted
dns-server but sent not-found-answers pretending to be the intended ns.
Not easy to find such a pitfall :(
Thanks again,
-Peter
-----Urspr?ngliche Nachricht-----
Von: Peter
2014 Aug 29
1
Samba 4 dns-resolv-prob with different subnets
Hello,
I?m using one Samba4-dc ?d-02? (IP 192.168.1.100) on subnet (192.168.1.0).
Internal dns works for clients and other servers at subnet 192.168.1.0.
Now I want to join another dc ?dc-01? (IP 192.168.0.101) at subnet
192.168.0.0 which is connect over routed openvpn. Ping the first dc an vice
versa works but ?host ?v dc-02? results in the following message:
Trying ?dc-02?
Host
2015 Apr 21
4
sernet = dead?
> On 21/04/15 09:17, Peter Grotz - Obel und Partner GbR wrote:
> > Hallo,
> >
> >
> >
> > samba 4.2 is released for some time now. Sernet usually doesn?t take a lot
> > of time to release their new packages.
> >
> > But now we haven?t heard a peep from them. Are they gone or will there be
> > another fine release?
> >
> >
2015 Apr 21
2
sernet = dead?
Hallo,
samba 4.2 is released for some time now. Sernet usually doesn?t take a lot
of time to release their new packages.
But now we haven?t heard a peep from them. Are they gone or will there be
another fine release?
In great expectation of a fine new sernet-samba-package-release
-Peter
2015 Apr 21
5
sernet = dead?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The packages are online :-)
Am 21.04.15 um 16:53 schrieb L.P.H. van Belle:
> thats still the case with the packages but.. 4.2.1 wil build on
> jessie fine. ( from source ) Did that today.
>
>
> Gr,
>
> Louis
>
>
>> -----Oorspronkelijk bericht----- Van: rowlandpenny at googlemail.com
>>
2018 Dec 12
5
error with joining new DC to domain
On Wed, 12 Dec 2018 16:01:52 +0100
"peter.grotz--- via samba" <samba at lists.samba.org> wrote:
> Thanks Rowland for your answer.
>
> these are sernet-packages from their subscription.
>
> There are 4 DCs (all with last sernet-rpms) 2 are demoted with probs
> (dc-01 and dc-02 both centos6) and 2 are running (dc-10 and dc-11 on
> centos 7)
>
>
2018 Dec 12
0
error with joining new DC to domain
Thanks Rowloand for the hint!
I installed sernet-samba 4.7 and give it a try. Now I get:
[root at dc-12 1]# samba-tool domain join obel.lan DC --realm=obel.lan -Uadministrator
Finding a writeable DC for domain 'obel.lan'
Found DC dc-11.obel.lan
Password for [OBEL\administrator]:
workgroup is OBEL
realm is obel.lan
Adding CN=DC-12,OU=Domain Controllers,DC=obel,DC=lan
Adding
2018 Dec 12
0
error with joining new DC to domain
may I extend the issue with some strange behaviour? Look here:
installing the sernet 4.7 as mentioned above I can´t join the domain in a regular way. ONLY it works when I asked BOTH of the working DCs with 4.9.3 before I try without explicit naming of a server... ^^
Follow me here:
[root at dc-02 etc]# samba-tool domain join obel.lan DC -U"OBEL\administrator" --realm=obel.lan
2018 Dec 12
2
error with joining new DC to domain
On Wed, 12 Dec 2018 15:43:09 +0100
peter grotz via samba <samba at lists.samba.org> wrote:
> I forgot: this is samba 4.9.3 on centos 7
Where did you get Samba 4.9.3 from ?
>
> Thanks
>
>
> Hello,
>
> I got a problem with adding an new dc to a domain. when I try to join
> I get the following:
What are the other DC(s) ?
Rowland
2018 Dec 12
3
error with joining new DC to domain
Hello,
I got a problem with adding an new dc to a domain. when I try to join I get the following:
[root at dc-12 etc]# samba-tool domain join obel.lan DC -Uadministrator --server=dc-11
Password for [OBEL\administrator]:
workgroup is OBEL
realm is obel.lan
Adding CN=DC-12,OU=Domain Controllers,DC=obel,DC=lan
Adding
2014 Aug 26
1
Samba 4 fsmo-handling on crashed dc-server
Hallo,
we have two dcs in one domain which is located in separate subnets. These
subnets are connected by a routed vpn.
How must I handle fsmo roles when one of these dcs fails and will maybe be
repaired and reconnected?
A transfer of the fsmo roles is not possible until the dc is repaired, so
should the fsmos be seized from the other dc? Can anybody give me a hint how
to handle this
2015 Apr 21
0
sernet = dead?
thats still the case with the packages but.. 4.2.1 wil build on jessie fine. ( from source )
Did that today.
Gr,
Louis
>-----Oorspronkelijk bericht-----
>Van: rowlandpenny at googlemail.com
>[mailto:samba-bounces at lists.samba.org] Namens Rowland Penny
>Verzonden: dinsdag 21 april 2015 16:51
>Aan: samba at lists.samba.org
>Onderwerp: Re: [Samba] sernet = dead?
>
2015 Apr 21
0
sernet = dead?
On 21/04/15 16:06, Stefan Kania wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The packages are online :-)
>
> Am 21.04.15 um 16:53 schrieb L.P.H. van Belle:
>> thats still the case with the packages but.. 4.2.1 wil build on
>> jessie fine. ( from source ) Did that today.
>>
>>
>> Gr,
>>
>> Louis
>>
>>
2013 Jun 24
1
Deprecation notice on custom type?
Deprecation notice: Resource references should now be capitalized on
line 101 in file /etc/puppet/manifests/templates/basenode.pp
This is the specific line of code:
realize (users::useraccount[hiera(''users'')])
When I capitalize Users, I get the following error:
Error 400 on SERVER: Could not parse for environment production: Syntax
error at
2018 Dec 12
0
error with joining new DC to domain
Thanks Rowland for your answer.
these are sernet-packages from their subscription.
There are 4 DCs (all with last sernet-rpms) 2 are demoted with probs
(dc-01 and dc-02 both centos6) and 2 are running (dc-10 and dc-11 on
centos 7)
dc-11 has all fsmo. joining with the old dc-01 and dc-02 doesn´t even
work.
dc-01 joins but gives me this:
Deleted
2014 May 19
0
Samba How to kill the locked files from a useraccount by multiple smbd pids
Hello,
I would like to how to do to kill the locked files from a useraccount by multiple smbd pids automatically when the session is closed?
####
Details Samba server:
Release: 5.10
Kernel architecture: sun4u
Application architecture: sparc
Hardware provider: Sun_Microsystems
Kernel version: SunOS 5.10 Generic_142909-17
Samba version:
Samba version 3.5.6
Smb.conf file section Global:
#
2019 Jan 21
3
force re-authentication when accessing different shares
hello & thx for your fast response!
i need a way to create samba shares without creating system user accounts:
- add users via smbpasswd with unique password
- no need for a corresponding useraccount in /etc/passwd
- access to the corresponding shares should be independent from any domain
(i.e. the share should be accessable
via windows client)
to come around the useraccount-restriction (as
2008 Oct 29
0
Installation: not creating necessary directories
I have tried installing R on a web server on which I have a user
account but not root access.
I checked and the PERL, Fortran, etc. prerequisites all seem in order.
The compiling of R with:
% ./configure --with-x=no
This works fine without errors.
I try a "make check", however, and soon get an error as it cannot find
files which should have been made. Most of the files seem to
2019 Jan 21
0
force re-authentication when accessing different shares
On 1/21/19 10:24 AM, Harald Glanzer via samba wrote:
> hello & thx for your fast response!
>
> i need a way to create samba shares without creating system user accounts:
>
> - add users via smbpasswd with unique password
> - no need for a corresponding useraccount in /etc/passwd
> - access to the corresponding shares should be independent from any domain
> (i.e. the
2014 May 27
2
CentOS 6.5 + Samba 4.1.6 - Variable Substitution (smb.conf)
Hello everyone.
So, I come to you because I have a little problem when setting up my domain controller based on CentOS 6.5 and Samba 4.1.6.
Everything works well, except for one small detail, which in my case blocking me.
I
would like to automatically generate the home directory of the user
during the first connection (from Win or Linux), but the problem is that
for some unknown reason,