search for: ipadre

Hi We just installed a W server 2008 server as antivirus server. As this server is heavily underused we created a share to backup files from other servers. This share is easily accessed from XP pro Pc's via \\ipadr\share and giving a user/password name on the W 2008 server. We then try to use it from an open suse 9.3 linux server via smbclient. smbclient //ipadr/share -U user%password

...> The DC (with FSMO) Site name = Default-First-Site-Name (samba-tool fsmo show) > > The Default Naming Context = DC=internal,DC=domain,DC=tld (samba-tool fsmo show) > > The Kerberos REALM name used = KERBEROS.REAL (kinit and /etc/krb5.conf and resolving) > > The Ipadres of DC dc1.internal.domain.tld = 192.168.0.1 > > The Ipadres of DC dc2.internal.domain.tld = 192.168.0.2 > > The scripts are nothing fancy but if you have a "incorrect" setup. > > You get errors. Main goal if that with these script we point where the...

Louis, Just wanted to say 'thanks' for your work. I just ran your "old script' (to create a DC02) yesterday so I am familiar with it's content. The (old) script appeared to have processed okay and the DC02 appeared as a 'computer' when I checked thru ADUC on my W7 client. Any other tests you'd suggest to confirm the DC02 is operating properly? (About the new

On Sat, 19 Nov 2016 08:14:58 -0600 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-11-19 07:54, Rowland Penny via samba wrote: > > > On Sat, 19 Nov 2016 07:03:22 -0600 > > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > > > On 2016-11-18 13:19, Bob of Donelson Trophy via samba wrote: > > >

...IP address = 192.168.0.1 > > The DC with FSMO roles = DC1 > > The DC (with FSMO) Site name = Default-First-Site-Name > > The Default Naming Context = DC=internal,DC=domain,DC=tld > > The Kerberos name used = KERBEROS.REALM.TLD > > The Ipadres of DC dc2.internal.domain.tld. = 192.168.0.2 > > The Ipadres of DC dc1.internal.domain.tld. = 192.168.0.1 > > Without fixing hostname > > root at ad41:~# ./samba-info.sh > .... > dns child failed to find name '3(NXDOMAIN)' of type A > finddcs: No matching ser...

...Name (samba-tool > > fsmo show) > > > > The Default Naming Context = DC=internal,DC=domain,DC=tld > > (samba-tool fsmo show) > > > > The Kerberos REALM name used = KERBEROS.REAL (kinit > > and /etc/krb5.conf and resolving) > > > > The Ipadres of DC dc1.internal.domain.tld = 192.168.0.1 > > > > The Ipadres of DC dc2.internal.domain.tld = 192.168.0.2 > > > > The scripts are nothing fancy but if you have a "incorrect" setup. > > > > You get errors. Main goal if that with th...

...= 192.168.0.1 >>> The DC with FSMO roles = DC1 >>> The DC (with FSMO) Site name = Default-First-Site-Name >>> The Default Naming Context = DC=internal,DC=domain,DC=tld >>> The Kerberos name used = KERBEROS.REALM.TLD >>> The Ipadres of DC dc2.internal.domain.tld. = 192.168.0.2 >>> The Ipadres of DC dc1.internal.domain.tld. = 192.168.0.1 >> >> Without fixing hostname >> >> root at ad41:~# ./samba-info.sh >> .... >> dns child failed to find name '3(NXDOMAIN)' of type A >...

We have several Asterisk servers (1.6.2.15) all configured for Realtime, all backed by the same database. The Asterisk servers are all listed under DNS SRV records, and SIP ATAs find us this way. Normally, no matter which Asterisk server an ATA connects to, we get our database fields filled out correctly, such as "regseconds", "lastms", "ipadr", etc. However, with

...     =  DC1 (samba-tool fsmo show) The DC (with FSMO) Site name  = Default-First-Site-Name (samba-tool fsmo show) The Default Naming Context    = DC=internal,DC=domain,DC=tld    (samba-tool fsmo show) The Kerberos REALM name used  = KERBEROS.REAL     (kinit and /etc/krb5.conf and resolving) The Ipadres of DC  dc1.internal.domain.tld        = 192.168.0.1 The Ipadres of DC  dc2.internal.domain.tld        = 192.168.0.2     The scripts are nothing fancy but if you have a “incorrect” setup. You get errors. Main goal if that with these script we point where the error  is expected.   Greetz,...

Hi Louis, Am 30.04.2015 um 15:31 schrieb L.P.H. van Belle: > Hai.. > > After a new setup i was confronted again with the unable to login with RDP. > so here is some extra info for the debugging this. > > I used RDP to connect a Windows 7 64 bit, connected in rdp with ipadres of the pc. > and again unable to login. > > since im trying to setup a smb.conf with minimal changes, i only added : > auth methods = sam, winbind > > restarted samba on both DC's > > and yes.. im able to login again, ADUC works, i can add users .. and DNS tool did also...

Hi all, since the migration of our old Win2k domain to Samba4 some years ago I get a lot of errors like the following when doing a "samba-tool dbcheck --cross-ncs --fix" : ERROR: Normalisation error for attribute whenCreated in CN=rpc-Ns-Group,CN=Schema,CN=Configuration,DC=samdom,DC=com value '19700101000000.0Z' should be '16010101000000.0Z' Fix normalisation for

...= dc1 (samba-tool fsmo show) The DC (with FSMO) Site name = Default-First-Site-Name (samba-tool fsmo show) The Default Naming Context = DC=rotterdam,DC=bazuin,DC=nl (samba-tool fsmo show) The Kerberos REALM name used = internal.example.com (kinit and /etc/krb5.conf and resolving) The Ipadres of DC dc1.internal.example.com = 192.168.1.1 The Ipadres of DC dc2.internal.example.com = 192.168.1.2 SAMBA_SERVER_ROLE: active directory domain controller SAMBA_SERVER_SERVICES: s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate SAMBA_DCERPC_ENDPOINT...

sorry for the noise.. I missed the solution in my mail. just saw it online.. The working version for rdp login.. I can confirm also that after adding these to the smb.conf dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, remote, winreg, srvsvc auth methods = sam, winbind, ntdomain,

Hi, I want to be able to specify actions for different classes of traffic in any of these four ways, and I''d like to use only HTB if possible: 1. No guranteed rate, No ceil 2. Guaranteed rate, No ceil 3. No guranteed rate, Ceil specified 4. Guaranteed rate, Ceil specified For types 2, 3 and 4 there can be several classes of each, with different rates and ceilings. 4 is ofcourse easy.

Hi, My server is under attack allows the attacker to abuse of a php script of a vhost. How can I find what is the script. Regards, maverh

...015 um 15:31 schrieb L.P.H. van Belle: >> Hai.. >> >> After a new setup i was confronted again with the unable to >login with RDP. >> so here is some extra info for the debugging this. >> >> I used RDP to connect a Windows 7 64 bit, connected in rdp >with ipadres of the pc. >> and again unable to login. >> >> since im trying to setup a smb.conf with minimal changes, i >only added : >> auth methods = sam, winbind >> >> restarted samba on both DC's >> >> and yes.. im able to login again, ADUC works, i c...

...FSMO roles        = RY11CITDC (samba-tool fsmo show) The DC (with FSMO) Site name  = Default-First-Site-Name (samba-tool fsmo show) The Default Naming Context    = DC=ry11cit,DC=lan (samba-tool fsmo show) The Kerberos REALM name used  = RY11CIT.LAN    (kinit and /etc/krb5.conf and resolving) The Ipadres of DC 2(SERVFAIL        = 2(SERVFAIL) SAMBA_SERVER_ROLE: active directory domain controller SAMBA_SERVER_SERVICES: s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate SAMBA_DCERPC_ENDPOINT_SERVERS: epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, drsuapi, dssetu...

...er > The DC with FSMO roles        =  (samba-tool fsmo show) > The DC (with FSMO) Site name  =  (samba-tool fsmo show) > The Default Naming Context    =  (samba-tool fsmo show) > The Kerberos REALM name used  = RY11CIT.LAN    (kinit and > /etc/krb5.conf > and resolving) > The Ipadres of DC ry11citsdc.ry11cit.lan        = 10.44.1.9 > The Ipadres of DC ry11citdc.ry11cit.lan        = 10.44.1.10 > SAMBA_SERVER_ROLE: active directory domain controller > SAMBA_SERVER_SERVICES: s3fs, rpc, nbt, wrepl, ldap, cldap, > kdc, drepl, > winbindd, ntp_signd, kcc, dnsupdate &g...

On 12/8/2017 2:54 PM, Taylor Hammerling via samba wrote: > Glad you guys replied, here is my output :D > > root at dc1:~# ./samba-setup-checkup.sh > Check hostnames : Ok > ./samba-setup-checkup.sh: line 89: [: too many arguments > Checking detected host ipnumbers from resolv.conf and default gateway > Ping gateway ip : 172.28.0.1 : Ok > ping nameserver1: 172.28.255.49 : Ok

Hai.. After a new setup i was confronted again with the unable to login with RDP. so here is some extra info for the debugging this. I used RDP to connect a Windows 7 64 bit, connected in rdp with ipadres of the pc. and again unable to login. since im trying to setup a smb.conf with minimal changes, i only added : auth methods = sam, winbind restarted samba on both DC's and yes.. im able to login again, ADUC works, i can add users .. and DNS tool did also work fine. So i hope this info...