hhymwaa

Performing Arts Technician Grade 3 - Sackville School - East Grinstead We require, for a July 2015 start, a technician to work primarily in our Drama Department. The successful candidate will manage and maintain our extensive lighting facility, ICT, recording, video and audio equipment and help teachers in the classroom when students are using these. Familiarity with the range of equipment will be useful, but training can be provided. The ability to work with a variety of people and assist with administration is essential. Non-Teaching Vacancies | Sackville School

Solved! We spent a lot of time trying to find this fault and trying to figure out if it was an OD AD or client Mac problem, we looked closely at our AD DNS as we had also noticed that our Global Catalog was slow to respond. We then remembered that Openhive/captia had asked us to turn off our DNS dynamic updates (last November) as they said that our DNS was trying to update their DNS server, we did this, and there seemed to be no problem, PCs would bind OK, DNS worked fine. So having tried almost everything we could think off we turned on the DNS dynamic updates, and within half an hour our Global catalog worked and the Macs bound to the AD! Here's Reg setting Captia sent us, we have now deleted this DWORD Value Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Tcpip\Parameters On the Edit menu, point to New, and then click DWORD Value. Type DisableDynamicUpdate, and then press ENTER two times. In the Edit DWORD Value dialog box, type 1 in the Value data box, and then click OK. Note By default, the DNS update is enabled (0). Exit Registry Editor.

Yep, time and date checked

I have about 40 10.9 Macs on my AD Domain (plus OD server). Recently the two MacPros (one aluminium case and one black shiny ash tray) have lost their binding to the AD, so I have unbound them from both servers. I have then bound the MacPro to the OD, with no problem, but when I try to bind to the AD through the OD Utility >AD service (entering the FQDN then the domain admin account and password or DOMAIN\admin and password) I immediately get the message “Authentication server could not be contact acted”. · To resolve this I have checked · Server/client time is spot on · Pinging the DC is fine · DNS nslookup - fwd and rev to the DC is fine · I can mount a DC share · Dig –t ANY soa returns both DCs · Console – when console is cleared and I try to bind I get no log entries · Wireshark – I can’t see any traffic between the client and server except one MDNS entry I am not sure what steps to take next any thoughts