Search results

  1. B

    Active Directory craziness

    As soon as I have a few spare moments, I'm going to do just that. Thanks for the reminder!
  2. B

    Active Directory craziness

    I finally discovered the culprit. On the PDC, I had to change LDAP Server signing policies to "None" to get it to work. A fairly obscure setting, I think, but all's finally well.
  3. B

    Active Directory craziness

    This may not be the most appropriate venue for this question, but I'm asking everywhere I can think of: We've got a mix of iMac G5 and PowerMac G5 machines running on a Windows 2003 network. They were bound to the domain and everything was working splendidly as far as AD is concered. Earlier...
  4. B

    10.4.2 TCP/IP issues

    I've resolved it, and it turns out that a mal-configured switch was flooding the network with traffic. All of our Windows machines handled it fine, but it crippled the Macs. With the switch offline, they regained connectivity, but still had to be unbound, then re-bound to AD. Go figure.
  5. B

    10.4.2 TCP/IP issues

    I've deleted and recreated the computer accounts in AD. The problem seems to be that the Macs aren't connecting to the network properly to even see the domain.
  6. B

    10.4.2 TCP/IP issues

    I've tried unbinding, but it just hangs. I've also wiped one Mac clean and reinstalled the OS, and it's experiencing the same issues. Trying to bind it to Active Directory returns an "invalid domain"-type error message.
  7. B

    10.4.2 TCP/IP issues

    We have 11 brand new Macs, all running 10.4.2. They were bound to Active Directory on a Win2003 network and all users were logging in perfectly. Then we had a brief power outage. Since the outage, TCP/IP seems to have gone haywire on 10 of the 11 machines. They can pull IP addresses from DHCP...
Back
Top