Search the Community

We have approx 60 Macs (mix of emac, imacs, minimacs) and a G5 Xserve all running Leopard (or Leopard Server in the case of the Xserve). All desktop machines are binded (?!) to Open Directory on the Xserve and Active Directory on the multiple Windows Server 2k3 domain controllers. Every week since binding them to AD we get 3 or 4 desktop macs which appear to have lost their trust with Active Directory. We get the green 'everythings cool' light on both the OD and AD connection in Directory Utility yet we cannot login with any domain user. If we unbind the problematic mac, delete the object from AD and rebind it, systems are all go again. There is no obvious pattern, no specific machines that keep loosing trust, no specific models and we've checked the time which is spot on. We also have an Ubuntu 8.04 file server running samba which in turn authenticates with AD using Likewise open (setup to authenticate a month ago). Interestingly, no one could access the shares this morning so after taking a closer look I found using the 'ls -l' command in the terminal, that the usually assigned group 'domain^users' has been replaced with a gid number. Logging in directly to the server using a network account also failed. This looked rather familiar so after unbinding the server, deleting its AD account and then rebinding it all systems were go again and the gids upon running 'ls -l' had turned back into 'domain^users'. Not really what you want for a file server! If it makes any difference, all the macs and the ubuntu machine are on static ips. After originally thinking that it must be a Mac issue somewhere, I'm now leaning towards it being Server 2003 not liking something. Does anyone have any ideas, pointers or similar experiences? Kev

Hi all, I’m looking for some help with a slow DHCP problem. We’re using mac-based authentication, procurve switches and IAS. 30 vlans dynamically allocated, the 30 subnets managed by server 2008 DHCP. Everything works fine except DHCP is slow, not hideously slow, but can be 10 to 30 seconds or so. This was never a real problem and got put on the back burner; but we’re now running a few thin clients which ask for an address twice during boot (one for pxe, one for the thinclient os) and so its time to pin it down. In a nut shell, If a machine is put in a vlan dynamically then DCHP is slow. If the same machine is forced (port untagged) into a vlan then DHCP works as it should. IAS validates the machines immediately so the delay isn’t there (dhcp is slow even if I randomly /release /renew after a while). There’s nothing obvious shouting out of the DHCP logs – though I haven’t been through them with a fine tooth comb. I’ve had a Google around and nothing stands out. DMcCoy, I think we have a similar setup to you; did you experience anything like this? Anyone got any ideas? Edit: just found a slightly later firmware for the 2626’s (the changes log doesn’t mention fixing a dhcp problem but you never know…), I'll try that on monday...

Dear All, We currently have about 20 Macs that are integrated into our AD domain with Golden Triangles and magic. They used to be able to print to our W2K8 print server no problems, but recently they have started asking for domain credentials in order to print. All I have done so far is re-bind the server to the domain as that was not authenticating properly. Now that is working fine, I don't know what to try next. Any help is appreciated. Many thanks, Ben.

Hi all, I am having a problem saving a printer to the settings of a MacBook Pro within my workplace. I have managed to install the printer and get the user to print. However, when the printer asks for authentication it doesn't remember the credentials I am trying to save. I enter the correct credentials and click 'save to keychain' and it prints perfect. However, when going to print again, it has not remembered these credentials. Can anyone offer any help or guidance with this? Thanks in advance.