Mac Thread, Strange refusal to bind issue - naming clash in Technical; Trying to bind an OS 10.7 machine to our AD over recent days and the flipping thing doesn't want to ...
-
12th January 2012, 04:09 PM #1 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?
-
-
IDG Tech News
-
13th January 2012, 09:03 AM #2
- Rep Power
- 9
Are you talking about binding to apple server ?
If you want to bind Lion clients to Leopard server then you will have this problem. You will have to do unauthenticated binding. If you try to do authenticated binding then it will say computer account exists. No matter what you do its not going to do authenticated binding. I was puzzled by same problem. You can enable unauthenticated binding at the Leopard server by GUI or by command line.
IN GUI: Server Admin >Open Directory >Policies >Binding > Uncheck "Enable authenticated binding"
Command Line: sudo slapconfig -setmacosxodpolicy -binding disabled.
In unauthenticated binding the mac may not appear in Work Group Manager. You won't be able to add the mac to any computer group because it may not appear at all. As a result you won't be able to control the MCX settings by computer.
Hope this helps.
-
Thanks to sultan966 from:
speckytecky (13th January 2012)
-
13th January 2012, 10:20 AM #3 
Originally Posted by
sultan966
In unauthenticated binding the mac may not appear in Work Group Manager. You won't be able to add the mac to any computer group because it may not appear at all. As a result you won't be able to control the MCX settings by computer.
Hope this helps.
That's not strictly true. We do not use authenticated binding here and I still manage the computers fine. What you need to do is instead of using the plus button to add the computers to lists in WGM, make sure that the machines are switched on and then use the button that has three ... on it. This will bring up a list of the macs that are available on the network. You can then add these to the computer lists. It finds them by Mac address as far as I'm aware. I think you can also add them to the list by the mac address. This is how I have always done it. I have had people say that you should use authenticated binding as the computers can occasionally disappear and then are not managed by the MCX's. I've never really had a major issue though.
@speckytecky
Have you imaged this machine with an image taken from a mac that was already bound? If so, it is always best to image a mac before binding. Also if the sharing name in the sharing preference pane will not change, this comes from the DNS Server. make sure that the dns settings are correct. If there is an old DNS record, the mac may use it causing confusion with the naming. Its usually the reverse zone records that cause the issue IIRC.
-
Thanks to HodgeHi from:
speckytecky (13th January 2012)
-
13th January 2012, 04:32 PM #4 Thanks @sultan966. No it's to Active Directory.

Originally Posted by
sultan966
Are you talking about binding to apple server ?
If you want to bind Lion clients to Leopard server then you will have this problem. You will have to do unauthenticated binding. If you try to do authenticated binding then it will say computer account exists. No matter what you do its not going to do authenticated binding. I was puzzled by same problem. You can enable unauthenticated binding at the Leopard server by GUI or by command line.
IN GUI: Server Admin >Open Directory >Policies >Binding > Uncheck "Enable authenticated binding"
Command Line: sudo slapconfig -setmacosxodpolicy -binding disabled.
In unauthenticated binding the mac may not appear in Work Group Manager. You won't be able to add the mac to any computer group because it may not appear at all. As a result you won't be able to control the MCX settings by computer.
Hope this helps.
Last edited by speckytecky; 13th January 2012 at 04:37 PM.
-
-
13th January 2012, 04:35 PM #5 Thanks given to @sultan966 and @HodgeHi you have both given me areas to explore.
-
SHARE: 
Similar Threads
-
By contink in forum Hardware
Replies: 5
Last Post: 2nd July 2007, 08:20 AM
-
By CheeseDog in forum Educational Software
Replies: 0
Last Post: 16th April 2007, 11:13 AM
-
By johnny in forum How do you do....it?
Replies: 8
Last Post: 23rd February 2007, 01:31 PM
-
Replies: 6
Last Post: 16th September 2006, 09:33 PM
-
By woody in forum Scripts
Replies: 6
Last Post: 5th October 2005, 11:37 AM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules