search for: a70f

...STATUS_DOMAIN_CONTROLLER_NOT_FOUND (winbind -P). Windows' RSAT tools also completely fail to connect to the domain. Some of the old DCs started throwing "Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5] NT_STATUS_UNSUCCESSFUL" errors Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')". So… How the fuck do I recover from this? What's even wrong? -- Mit freundlichen Grüßen, / Best Regards, Sven Schwedas, System...

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center. The Gnome screen savers work ok. My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor. Does anyone have a fix for this?

I am trying to hook up linux to an LCD 1333x768 LCD TV. XP in 1024x768 show up just fine. X does not. I have set the screen preferences to 1024x768. I have edited the xorf.conf file instead of have a range from 50 - 70 I change it to be only 60. I start X and it still comes up on my A70F monitor but still will not show on my LCD TV. xvidtune does not run on this PC. It says something about "video modes are not tunable on this chip". My PC at this time is a dell SC420. Thanks for any input as to get the display working on the LCD TV under linux.

...Ok, this one, track down both uuid's, checkout which which > hostname belongs with these. > > Going by the output of `samba-tool drs showrepl` and sam.ldb, > the GUIDs are as follows: > > graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7 > graz-dc-bis 7e4973ba-4093-4523-a70f-7caa4845e34d (not in sam.ldb) > graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea > villach-dc-sem eb5f9772-cd8f-4cde-9629-f1898c94aedd > villach-dc-bis e1569c90-50f9-4bb5-bd85-79145e3ff6fd > > villach-sem/bis want to replicate to the dead and removed > graz-dc-bis for some reason...

...ectoryStudio can help > a lot with cleanup of these kind of things. > > Currently I'm using the ADSI MMC snap-in, any downsides > compared to ADS? I dont know, never used ADS :-/ Track done these : GUID's, the hostname's, ipnumbers A and PTR records 7e4973ba-4093-4523-a70f-7caa4845e34d d613fa11-064b-4bcc-ab01-20264f870f47 (how, see Verifying and Creating the objectGUID Record https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record) And as suggested, do this first through the RSAT tools or samba-tools, try removing them with these tools first. (how...

...NOT_FOUND (winbind -P). Windows' RSAT tools > also completely fail to connect to the domain. > > Some of the old DCs started throwing "Failed to bind to uuid > e3514235-4b06-11d1-ab04-00c04fc2dcd2 for > e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5] > NT_STATUS_UNSUCCESSFUL" errors > > Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')". > > > So… How the fuck do I recover from this? What's even wrong? > > > -- Mit freundlich...

...ostname > >>> belongs with these. > >> > >> Going by the output of `samba-tool drs showrepl` and sam.ldb, the > >> GUIDs are as follows: > >> > >> graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7 > >> graz-dc-bis 7e4973ba-4093-4523-a70f-7caa4845e34d > (not in sam.ldb) > >> graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea > >> villach-dc-sem eb5f9772-cd8f-4cde-9629-f1898c94aedd > >> villach-dc-bis e1569c90-50f9-4bb5-bd85-79145e3ff6fd > >> > >> villach-sem/bis want to replicate to the...

...-P). Windows' RSAT tools >> also completely fail to connect to the domain. >> >> Some of the old DCs started throwing "Failed to bind to uuid >> e3514235-4b06-11d1-ab04-00c04fc2dcd2 for >> e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5] >> NT_STATUS_UNSUCCESSFUL" errors >> >> Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')". >> >> >> So… How the fuck do I recover from this? What's even wrong? >> >&gt...

...gt;> belongs with these. >>>> >>>> Going by the output of `samba-tool drs showrepl` and sam.ldb, >>>> the GUIDs are as follows: >>>> >>>> graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7 graz-dc-bis >>>> 7e4973ba-4093-4523-a70f-7caa4845e34d >> (not in sam.ldb) >>>> graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea villach-dc-sem >>>> eb5f9772-cd8f-4cde-9629-f1898c94aedd villach-dc-bis >>>> e1569c90-50f9-4bb5-bd85-79145e3ff6fd >>>> >>>> villach-sem/bis want t...

Hi ... Can someone tell me whether or not this is indicative of a hardware, or software, problem? It happened a few times today, on two different drives, and it seem to "self-recover", since the server is still purring along without any noticeable problems: neptune# grep "timed out" /var/log/messages Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out

> Keytabs look reasonable, as far as I can see, but why does > graz-dc-sem have the same SPN output as graz-dc-1b in > addition to its own? A snapshotted server/cloned server? I dont know but thats not correct. I suggest, cleanup the DS with FSMO roles. Then remove a failty server and re-add it as a new installed DC. ( the good DS with FSMO) First backup:

Hello, i?ve Samba 4.7 with domain controller with 3 servers, 1 master (samba-ad) and two slaves (samba-slave1) and (samba-slave2). The problem is when create user account from "samba-ad? this account not sync to slave, but i create the account on "samba-slave1" or "samba-slave2? this is sync on all server. Samba version [???????.] root at samba-ad:~# samba -V Version