Strange refusal to bind issue - naming clash
Trying to bind an OS 10.7 machine to our AD over recent days and the flipping thing doesn't want to play. We have bound quite a few to date so are pretty used at to how to do it. The problem with this particular machine is I suspect something to do with it's name; we noticed that despite being called one name somewhere along the line it had decided that it was another machine that is already happily bound to the network. We have sort of successfully renamed it now and it appears to have accepted it's new name and indeed appears in DHCP as it's new name on our MS domain. However, try to bind it and it persistently thinks it's still the other machine. Grr! Any thoughts on this please?