search for: vsc

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc = false and true. Thanks,...

On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack of outbound replication for non PDC >> emulator DCs...

Changes replicate to it, but not from it. vsc\VSC-DC02 DSA Options: 0x00000001 DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1...

On 3/14/2017 10:29 AM, Arthur Ramsey wrote: > Changes replicate to it, but not from it. > > vsc\VSC-DC02 > DSA Options: 0x00000001 > DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb > DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA ob...

I believe the problem is a lack of outbound replication for non PDC emulator DCs. You'll notice isn't even trying because last successful was epoch (never) yet there are no errors. Inbound replication for this DC seems fine. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt@ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,...

Replication has been running smoothly until I upgraded to 4.5.0. I had various errors with all BDCs and a force sync didn't resolve it. I shutdown all BDCs, demoted them with --remove-other-dead-server then joined new BDCs with new names. At first replication was intermittently failing (consecutive failures counter kept resetting), but it seemed OK, just slow if anything. Now they all

Upgraded to 4.6.0 on all nodes. Still seeing the same issue. If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then it does replicate. On 03/13/2017 12:13 PM, Arthur Ramsey wrote: > > I believe the problem is a lack of outbound replication for non PDC > emulator DCs. You'll notice isn't...

...similar for all other DCs (different UUID values in log). When I run /usr/local/samba/sbin/samba_dnsupdate I get no error messages, but I noticed it reports it isn't the master when it is. [root at dc01 ~]# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom RidAllocationMasterRole owner: CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom PdcEmulationMas...

...I correct that this indicates an outbound replication isn't trying. On 03/13/2017 01:45 PM, lingpanda101 via samba wrote: > On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: >> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. >> >> If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it >> doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then it >> does replicate. >> >> On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >>> >>> I believe the problem is a lack of outbound replication for non PD...

...rent UUID values in log). > > When I run /usr/local/samba/sbin/samba_dnsupdate I get no error > messages, but I noticed it reports it isn't the master when it is. > > [root at dc01 ~]# samba-tool fsmo show > SchemaMasterRole owner: CN=NTDS > Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom > InfrastructureMasterRole owner: CN=NTDS > Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom > RidAllocationMasterRole owner: CN=NTDS > Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,...

Hi all, I''ve a problem when submitting a form : the URL seems to be invalid. I really don''t see the way I should try to solve that problem. I searched on the web, but didn''t found any kind of that problem. Here is the code : require ''mechanize'' agent = WWW::Mechanize.new page =

Well vsc-dc01 is actually dc01 for the host name, sorry I forgot about that. This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are request...

Hello, I'm running Samba 4.5.0 and bind-9.8.2-0.47.rc1.el6_8.1. One DC of four, the PDC, is magnitudes slower running /usr/local/samba/sbin/samba_dnsupdate --verbose --all-names. When that is running on that DC it seems to block any queries. The load average is usually under 0.5. The DC was unsafely halted, which could have corrupted something. I ran a dbcheck with samba-tool and it

This is a resend of the patches yet to be applied. This patch-set addresses some of the bus/driver model cleanup that Greg sugested over the last couple of days. In this patch-set we deal with the following issues: 1) Cleanup error handling in the vmbus_probe() and vmbus_child_device_register() functions. Fixed a bug in the probe failure path as part of this cleanup. 2) The Windows

This is a resend of the patches yet to be applied. This patch-set addresses some of the bus/driver model cleanup that Greg sugested over the last couple of days. In this patch-set we deal with the following issues: 1) Cleanup error handling in the vmbus_probe() and vmbus_child_device_register() functions. Fixed a bug in the probe failure path as part of this cleanup. 2) The Windows

I already tried the manual stop and start already no luck. I just tried deleting the connections as you recommended, but no luck. I also have been checking the samba log throughout my troubleshooting, but haven't found anything. Here's the log from vsc-dc02 anyway: http://pastebin.com/7FMv8pcu. That log includes when I did the showrepl, kcc, manual stop / start and manual replication tests as well as objects created on every DC. This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If y...

...o the blacklist. Looking at the source, I see the same behavior coded in chan_zap, chan_mgcp, and chan_skinny. While *8 isn't hard-coded here, it does seem to be hard-coded in res_features, or at least has the default pickup extension defined there. Looking at the non-asterisk-specific CLASS/VSC page on the wiki, the normal behavior of *80 is defined as "Selective Call Rejection Deactivation", which doesn't seem to jive with asterisks intended *80 behavior. On the other hand, *60 is defined as "Selective Call Rejection Activation," which does seem to make some sens...

...dering if anyone had any good code they could share for implementing vertical service codes within Asterisk. I'd really rather not have to spend hours making new wheels if someone has one or more that will fit. One of my issues is that I've had a very hard time finding out exactly which VSC's are already implemented in what parts of Asterisk. This system will be for the most part an IP Centrex platform for this customer, who will be selling services to his end-users. I've got a pretty good line on how I'm going to handle personal LD pin codes using ODBC, but if anyone...

Dear All, I have upgrade my samba from 3.0.33 to 3.3.3, that proces are success but I have a problem for samba-vscan. Error : [2012/01/16 10:32:00.074547, 0] smbd/vfs.c:167(vfs_init_custom) error probing vfs module 'vscan-clamav': NT_STATUS_UNSUCCESSFUL [2012/01/16 10:32:00.074559, 0] smbd/vfs.c:309(smbd_vfs_init) smbd_vfs_init: vfs_init_custom failed for vscan-clamav [2012/01/16 10:32:00.074569,...

...ad idmap config MEDITURE: range = 10000-49999 idmap config MEDITURE: schema mode = rfc2307); close($smb_conf_fh); close($resolv_conf_fh); } } I also have AD sites setup and have manually configured SRV records to perform load balancing. $ dig +short srv _ldap._tcp.vsc._sites.dc._msdcs.mediture.dom 0 50 389 dc02.mediture.dom. 0 25 389 dc04.mediture.dom. 0 100 389 dc01.mediture.dom. 0 100 389 dc03.mediture.dom. $ dig +short srv _ldap._tcp.aws._sites.dc._msdcs.mediture.dom 0 25 389 dc02.mediture.dom. 0 100 389 dc04.mediture.dom. 0 50 389 dc01.mediture.dom. 0 50 38...