Binding XP clients to 10.5 Server

Hi there.
I am trying to bind some xp clients to my 10.5 Server. I have set the server up as an OD master with a PDC.
Mac clients can bind with out a problem, but when trying to bind an xp machine I get an error message that says.
"Insufficient resources exist to complete the requested service"
Now I had this problem the other day when I started setting it up and in the end I created another DIrectory admin user for the windows clients and after some testing it looked like my password for the diradmin user was not liked. It had an ! on the end of it, but when I took the ! the XP machine did bind with out a problem.
Now I am trying to bind another machine and it is coming up with the same issue, but the new windows Directory Admin user is not working for that machine either.
I can't get any help from apple as I don't have a select service agreement that covers windows support so I am having to post here.
The log file is giving me this.
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetgrnam(2040)
odssam_getgrnam gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Groups record for 'LIBRARY$'!
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
2009-09-14 14:21:51.551 opendirectorypdbconfig[81679:713] CFPreferences: user home directory at /private/tmp/99 is unavailable. User domains will be volatile.
no credentials available
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(345)
samr_createuser: Running the command `/usr/bin/opendirectorypdbconfig -c createcomputeraccount -r library$ -n /LDAPv3/127.0.0.1' gave 136
[2009/09/14 14:21:51, 0, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:21:51, 1, pid=81678] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(371)
pdbdefault_createuser: failed to add a new account for 'LIBRARY$'
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetgrnam(2040)
odssam_getgrnam gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Groups record for 'LIBRARY$'!
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
2009-09-14 14:22:11.316 opendirectorypdbconfig[81692:713] CFPreferences: user home directory at /private/tmp/99 is unavailable. User domains will be volatile.
no credentials available
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(345)
samr_createuser: Running the command `/usr/bin/opendirectorypdbconfig -c createcomputeraccount -r library$ -n /LDAPv3/127.0.0.1' gave 136
[2009/09/14 14:22:11, 0, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1571)
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'LIBRARY$'
[2009/09/14 14:22:11, 1, pid=81691] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(371)
pdbdefault_createuser: failed to add a new account for 'LIBRARY$'
Any help on this would be appreciated.

Well I have had a look and the permissions for the tmp on the server are:
/tmp lrwxr-xr-x 1 root admin 11 Jul 18 10:31 tmp -> private/tmp
On my personal machine and another 10.5 server in the office the permissions are:
/tmp lrwxr-xr-x@ 1 root admin 11 29 Oct 2008 tmp -> private/tmp
The permissions on on /private/tmp are on all the machines:
drwxrwxrwt 6 root wheel 204 Sep 21 11:23 tmp
I have tried another approch, with slightly better results, but still no luck.
I manually created and entry into WGM for the XP machine. Just the name of the machine that is. When I then try bind the XP machine to the server I get the following logs.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
[2009/09/21 12:09:59, 0, pid=8391] /SourceCache/samba/samba-187.8/samba/source/passdb/passdb.c:lookupglobal_samname(596)
User HBC0094$ with invalid SID S-0-0 in passdb
[2009/09/21 12:09:59, 0, pid=8391] /SourceCache/samba/samba-187.8/samba/source/passdb/pdbinterface.c:pdb_default_createuser(389)
Could not get RID of fresh user
But still no luck I have run disk permissions repair on it as well.

Similar Messages

Need Help Binding Windows Xp clients to 10.5 server for a beginner

Hi
I've setup 10.5 server as a standard config. Which turns out it is a Open Directory Master and SMB role is Standalone Server.
I have been able to bind my 10.4 clients to the server domian using Directory Access and choosing automatic under LDAPv3/config.
So far the Macs are working well.
But I need to get the PC XP workstations on board. Where in XP do I have to go to enter in the info for the server to bind the clients to it? All this is new to me and still learning. The server is pretty basic. Authenticating users and giving them access to the shares.
Thanks
Steve

Hi Dave
Thanks for the tips. I was wondering if you could help me out some more? I have never done any binding on the PC. Macs seem quite easy. I'm having trouble taking the info I have on the Mac and applying it to the correct input on the PC's. Bare with me. I think I am almost there.
I did not have the diradmim account set up. But I do now.
Now I have gotten to my computer/properties/system properties/Computer name
I clicked on the Change button near bottom right
Now I am at this new window.
Computer name: I can put anything I want in here?
Member of: I should check Domain and enter the domain of the server?
(currently in my smb settings on the server I have workgroup set to WORKGROUP. Does this need to change?)
Last question I think. You mentioned the diradmin account on 10.5. Where do I enter this info on the PC.
Sorry for all the questions but having this info would help and get me where I need to be.
Thanks
Steve

Cannot bind 10.6 client to 10.7 server

Hi.
I have a mac mini with lion on it, and am trying to set up mobile user accounts.
Trying to bind a 10.6 mac book pro to the server, I go into open dir utility, LDAPv3, edit, click on the server, edit, bind
and I get the error msg: Unexpected Error while binding. Unexpected error while attempting to bind. Operation cancelled.
I am sure I have all the admin info correct. This error occurs on a new computer that has never been bound to the computer before.
Previously I have been able to bind computers to the server (although that was when I was on my own personal network, not at the clients....)
Please help I'm stuck! I have googled extensivley and nothing has come up.
Thanks in advance, rhys

check if the machine all ready exists in OD
(mac address)
if it does try removing it and binding the client machine again
can you join the server without binding

AFP login via Kerberos from 10.5 clients to 10.4 server broken

I don't know if this is connected to the problem laid out by William W. Higgins in [Open Directory or LDAP Problem with 10.5 Client and 10.4 Server|http://discussions.apple.com/thread.jspa?threadID=2163645&tstart=0]. The symptoms are... somewhat different, so I'll start a new thread.
We've got a small office with a bunch of 10.5.8 clients, a couple of 10.6 clients, one lone Windows 2000 client, and a number of remote users. I've had my OS X Server 10.4.11 machine (a PowerMac G5 single 1.8GHz, fwiw) working happily as an OD Master for the past few weeks. It's mostly a file server and a back DNS server for our public web site—we have web service turned on, but it's mostly to allow remote users to download files (or upload via WebDAV). The server has a secondary NIC that's hooked up to the cable modem in the DMZ. Everything else is behind the modem's NAT.
We've had some things show up on the logs that are making us want to tighten security, both in the LAN and over the internet. We've gone to HTTPS for the web server and are using TLS/SSL for the PureFTPd server. We closed the SMB ports on the external firewall—something we should have done years ago, probably.
I wanted to switch the AFP service over to Kerberos authentication only. However, when I make that change in Admin Server>AFP>Settings>Access, none of the clients can log on; they get an error reading:
+*Connection Failed*+
+There was an error connecting to the server. Check the server name or IP address and try again.+
+If you are unable to resolve the problem, contact your network administrator.+
Then, after you click on OK, you get the following:
+Sorry, the operation could not be completed because an unknown error occurred.+
+(Error code -5002)+
That code seems to indicate a Kerberos problem.
And when I try to log on as a network user from one of the clients, I get this message:
*+You are unable to log in to the user account "user" at this time+*
+Logging in failed because an error occurred.+
Gee, that's helpful!
Server Admin shows OD and Kerberos as up and running. The Password Service log has the following entry:
+Jan 21 2010 09:18:21 AUTH2: {0x4b4df87638fa1ec80000003400000034, bound-client-machine$} CRAM-MD5 authentication succeeded.+
So the log-on didn't go through Kerberos, for some reason, though it's been working fine that way for weeks.
I tried using +sso_util configure -r KERBEROS.REALM -a diradmin afp+ to make sure that single sign-on was running for AFP. No change.
I can use +dscl -u username -p localhost read /LDAPv3/Users/username+ and read the information on the user's home directory.
I can use /System/Library/CoreServices/Kerberos (or Ticket Agent) to request and receive a ticket. (Side note: does Kerberos really not allow login by secondary short names??? That's a pain! If I add principals for the secondary short names, will it authenticate correctly to the proper account???)
FTP is working. Web authentication is working. If I turn Kerberos authentication off for AFP, everything else seems to return to normal... but then the passwords are passed as cleartext, which isn't acceptable.
So... Is this a bug? Is this a conflict with PureFTPd? Am I doing something wrong?
Message was edited by: David Kudler

Post-reboot:
Well, the good news is that the kdc now shows up in the kadmin log as starting up:
Jan 26 11:43:02 localhost kadmind[98](info): Seeding random number generator
Jan 26 11:43:03 localhost kadmind[98](info): No dictionary file specified, continuing without one.
Jan 26 11:43:04 localhost kadmind[98](info): starting
The lack of dictionary file I believe is a minor error, right?
The bad news is that a) clients are no longer able to receive tickets (+*Kerberos Error* Configuration does not specify default realm+) and b) clients can't log on at all—not even via the Finder>Go>Connect to Server... command. Not even when you use the static IP address of the server rather than the DNS name.
DNS still seems to be working. I can get reverse lookup:
*cerberus:~ root#* dig -x 10.1.10.2
; << DiG 9.3.6-APPLE-P2 << -x 10.1.10.2
;; global options: printcmd
;; Got answer:
;; -HEADER<<- opcode: QUERY, status: NOERROR, id: 45389
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2
;; QUESTION SECTION:
;2.10.1.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
2.10.1.10.in-addr.arpa. 3600 IN PTR cerberus.limbo.jcf.org.
;; AUTHORITY SECTION:
10.1.10.in-addr.arpa. 3600 IN NS ns1.jcf.org.
10.1.10.in-addr.arpa. 3600 IN NS cerberus.limbo.jcf.org.
10.1.10.in-addr.arpa. 3600 IN NS 10.1.10.1.
;; ADDITIONAL SECTION:
ns1.jcf.org. 86400 IN A 207.58.140.213
cerberus.limbo.jcf.org. 3600 IN A 10.1.10.2
;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 26 11:50:51 2010
;; MSG SIZE rcvd: 163</div>
*cerberus:~ root#* dig cerberus.hades.jcf.org
; <<>> DiG 9.3.6-APPLE-P2 <<>> cerberus.hades.jcf.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36453
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;cerberus.hades.jcf.org. IN A
;; ANSWER SECTION:
cerberus.hades.jcf.org. 86400 IN A 10.0.1.2
;; AUTHORITY SECTION:
hades.jcf.org. 86400 IN NS cerberus.hades.jcf.org.
hades.jcf.org. 86400 IN NS 10.1.10.1.
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 26 11:51:46 2010
;; MSG SIZE rcvd: 93
</div>
*cerberus:~ root#* changeip -checkhostname
Primary address = 10.1.10.2
Current HostName = cerberus.limbo.jcf.org
DNS HostName = cerberus.limbo.jcf.org
The names match. There is nothing to change.
(The DNS also checks out from the clients.)
But.... fubar.
When I run +kadmin.local listprincs+, it lists all of the users and computers I've added—plus a couple that I don't recognize but that seem to be the products of bound computers (the names are along these lines, rather than the actual computer names for the clients: +LKDC:SHA1.59B886209B027XXXXXXXXXXXXXXXXXXXXXXXXXXX$@CERBERUS.LIMBO.JCF.ORG+). But when I run +kadmin.local list_policies *+, it just pops down to the next prompt. There don't seem to be any policies defined. That can't be right, can it????
Further weirdness: I tried rebinding the client that I'm working from (an iMac running 10.6.2), also using the IP address. It goes through the binding process, but no dice—when I try to run System/Library/CoreServices/Kerberos.app, I still can't get a ticket. And the weird bit is, there doesn't seem to be a /Library/Preferences/edu.mit.Kerberos plist file on the client. Well, no wonder the client's Kerberos app can't authenticate the realm—there's no local file in which the data is stored!
I should note that when I rebooted this morning, I first booted to the backup drive and ran Disk Utility; I repaired permissions—more than once—and repaired the disk directory as well. Perhaps I have confused the **** out of it. Though how the permissions got fouled in the first place is beyond me.
I have other things to do (as it says in my profile, I'm the local IT guy by default)—though everyone where I work needs this problem solved.
At this point my options seem to be:
1.) Back up, demote, promote and reload the OD server.
2) Reinstall from scratch.
If anyone has any suggestions in the next hour or so, I'd love to hear them!
Message was edited by: David Kudler

How to add 10.8 managed clients to 10.8 server

Specifically, using Workgroup Manager 10.8 rather than Profile Mgr.
Previously, you could point your clients to the OD Server using Directory Assistant (or via Users & Groups in 10.7) which would then become available to add to a Computer group you had created in WGM. Even though I've got mine set up that way, WGM 10.8 can't see any of 'em. Is there another prerequisite I'm not aware of? Or does this method no longer apply to clients running 10.8?
thanks.

I'll check but I wouldn't doubt it. You can add clients in Profile Mgr. that way too (it's the only way you can add them AFAICT). If you can't browse for available clients, why bother with WGM? They're just adding extra layers of administration hassle in my opinion to make you collect and submit UUIDs in order to bind clients.

Just need a simple client sending message to server example????

Im trying to find a simple client-server example, where i can put the client on one laptop, server on the other and pass messages from the client to the server.
I've been trying to follow examples and ive had problems with policies, stubs(?) etc etc
Would someone please be able to provide me with an example i can follow and show me how to setup a policy. Im not a business user, i just want to learn how to make a simple message-sending app with RMI

Ok! rmiregistry is working (i think), ie no error messages.
But, when i execute i now get this:
init:
deps-jar:
compile:
run:
Server exception: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: test.hello
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: test.hello
        at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:396)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250)
        at sun.rmi.transport.Transport$1.run(Transport.java:159)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
        at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
        at test.Server.main(Server.java:33)
Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: test.hello
        at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
        at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:386)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250)
        at sun.rmi.transport.Transport$1.run(Transport.java:159)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: test.hello
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:247)
        at sun.rmi.server.LoaderHandler.loadProxyInterfaces(LoaderHandler.java:711)
        at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:655)
        at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:592)
        at java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:628)
        at java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:294)
        at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:238)
        at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1531)
        at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
        ... 12 more

Local KDC (LKDC) relating to Leopard clients logging into Tiger Server

This is a follow-up to my posting on this thread:
http://discussions.apple.com/message.jspa?messageID=5982070#5982070
Pursuing the problem I had when I upgraded to Leopard, I found it odd that trusted binding to Tiger OD from a Leopard client created a funny computer entry in the Workgroup Manger (WGM). Previously when using trusted binding from a Tiger machine to a Tiger server, one entry would be created. And Logging in as an OD user worked every time for me. However, it appears that under 10.5.1 Kerberos has changed significantly in that it is now being used extensively through the Leopard OS for Peer-to-Peer applications. This may account for the screwed up Computer account entries in WGM when a 10.5.1 client binds to 10.4.11 Server using trusted binding. The giveaway clue to this is the LKDC:SHA1 entry created in the WGM computer record (usually 3 seperate records for 10.5.1 instead of the normal single record with a Tiger client). My question is this:
Are there any changes that can be performed via command line on the 10.5.1 client to mimic the old 10.4 client Kerberos configuration without pervasive Peer-to-Peer use of Kerberos? Is is a config setting for the mit.kerberos file? Could it be as simple as flipping a switch to get the older more compatible Kerberos config of a 10.4 Tiger client? Can I dump the Local KDC present in Leopard, and get back to the good old days of non-local KDC under Tiger?
http://www.afp548.com/article.php?story=LeopardServerReview-LocalDirectory
"The Local KDC
Yes, you read that right, the local KDC. All Leopard client systems will now create a Local KDC for use with peer to peer file sharing.
While this isn't even as close to as scary as it seems, it is a topic worthy of at least a separate article, if not a whole series. I put on my thinking toque and sat in my thinking corner for a while on this, and I've not yet been able to come up with a reason for why having a KDC on every machine is less secure than how 10.4 did things. Having said that, though, I fully understand how this can seriously freak out your network security team as they don't quite grasp all the ins and the outs of this. Combine this with Back to My Mac, another article that's forthcoming, and you have a very interesting collection of some "sleeper" features in Leopard.
So, in a nutshell, a Local KDC, the LKDC, is created when 10.5 is installed. Local users will get LKDC authentication authorities allowing them to get Kerberos tickets and use that for single sign on to all the services hosted on that client system. Kerberos is supposed to be only used when you use Bonjour to discover the other machine. So primarily in peer to peer on the same LAN cases.
It works, you can see this for yourself. Screen share to another machine as a local user by picking the machine out of the sidebar in the Finder. You'll have to enter in your password the first time, but after that you can close out of that screen sharing session and restart it without having to re-enter your password. You can also see the ticket in the Kerberos.app, still buried in /System/Library/CoreServices."

Eric,
Thanks so much for your thoroughness and assistance. I think we have decided, for now, to forgo the 10.5 clients attaching to the 10.4 server because of too many intermittant issues. Similar machines on 10.5 gave different results. And at this point, our client is very skittish about the process working at all. I think we need more testing and that is the directon we'll take for now.
Here are some of our results:
I did find information on afp548 regarding the 10.5 preference. It was specificall referenced in this article:
http://www.afp548.com/forum/viewtopic.php?forum=18&showtopic=16064
Clearing the check box on the 10.4 server under OD > Settings > Security "Require password change on new user login" did solve the memory issue that kerberos was having. After clearing the setting, I:
* deleted all binding references at the server (WGM > Accounts > Lists > All Computers
* Deleted the bindings at the client and the the LDAP server references in Directory Access
* Restarted the machine
* Reconnected the LDAP server, Rebind the machine
* Check the LDAP search in issuing id <username> in Terminal
* OPen System PReferences > Accounts > Login Items, the preference is there!
* Yeehah
Oh, but the user still can't login in that machine. Uhm, why? I have no idea. I take a new machine, 10.5.1, no login accounts except a local admin, and no that user still cannot login. Other users, no problem, but not that user.
Take a new system, 10.4.11, set up the binding, the LDAP server, try to log in that same user: works every time. Ugh.
So of course, I think there is something up with that user, but nothing in logs gives an indication of what is going on. That I can find. THis is after 10 hours of testing and trying. Needless to state, the client is frustrated, and so am I.
You know, we do have one 10.5.1 client laptop that did work. After lots of binding and rebinding, it just somehow starting working as expected. But, the reason that we're sticking with 10.4 clients for now is that machine will not respond to password change mandates. I select that user in the WGM, check the "require password change on next login" and nothing happens on their end. They are not an admin, I have reset their account more times than I can count, and so I expect there are more non-working items with 10.5.1 clients and 10.4 server that will get me. It needs more testing for now.
So, back to your message, I haven't tried the SSL certificate, but I will give that a try.
In general, for your network, how are your laptop users configured? As mobile users? Network homes? Or Local homes?
Thanks again for your help. I really appreciate it.

LDAP Bind Failure: Can't contact LDAP server in Presentation Server

I have configured LDAP configuration in the RPD and am able to connect to the LDAP from the BI server. Its returning the information i need when i test through the admin tool. But when i try to log in from the PS using the same network id and password, it gives me the below error:
State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused. [53003] LDAP bind failure: Can't contact LDAP server. (08004).
I know for sure, the network connectivity is working as i get my results back from the BI Server. Please advise, if i need to change other configurations on the Presentation end. As my network folks have run out of ideas. Thx!

user9125812 wrote:
Yes, i am pinging from OBIEE Server through the RPD and i am successful.Pinging the OBIEE Server through the RPD? Ping is a DOS command, how can oyu "ping through the RPD".
Can you go to the server, open a CMD windows and do "ping nsldap.companyname.com" and see if it works. If it works it could be that the LDAP port is blocked by a firewall or OBIEE is not able to make a connection. Make sure you are using the correct port as well. Install an LDAP client in your OBIEE Server and test that you can connect to your LDAP server from your OBIEE Server, not from the RPD. You can use this:
http://jxplorer.org/

Clients forget MCX after server rebuild

Hi everyone. I'm running Mac OS X Server 10.6.8 on an Xserve. The OD system is tied to an Active Directory server in a magic triangle setup, with the OD providing no Kerberos of its own. This was actually changed recently -- due to repeated errors and LDAP deafness, I tore the server down and rebuilt it, re-importing the computers and computer groups from Workgroup Manager. Seems to be humming along fine now.
Except for one thing: The bound client machines, so far just Mac OS X 10.6.8, are starting to forget their MCX settings. For instance, we have a setting requiring a password on wake from sleep or screensaver, and one by one, I'm getting reports that this isn't happening.
Re-binding the machines to the OD server seems to resolve the issue. I'm wondering if anyone can think of a way that might avoid this -- certainly it's a security problem to have the machines not following their security policy until I physically come by and update them.
If anyone can think of a way around this, I would be very grateful!

Hi
This is an old issue and I have a feeling the answer is Time Machine is not supported using port trunking? If you disable the aggregate bond I would not be surprised if it started working?
https://discussions.apple.com/thread/2131323?start=0&tstart=0
This problem appears to have affected 10.5 Server only? Perhaps later versions of the Server don't have the problem?
HTH?
Tony

Exchange 2010 Initialization failed: The WinRM client received an HTTP server error status 500

Good morning,
I have major problems with exchange 2010 this morning.
First off, exchange stopped sending and receiving any emails- whether internal or external. We are running a server 2008 R2 domain and exchange 2010 is installed on a Server 2008 virtual machine.
I tried simply rebooting the server and then tried logging on and getting into the Exchange Management Console. I receive the following error in the exchange management console:
Initialization failed
The following error occurred while attempting to connect to the specified Exchange server 'exchangesvr.chs.internal';
The attempt to connect to
http://exchangesvr.chs.internal/Powershell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any
other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
I followed the steps listed here:
http://technet.microsoft.com/en-us/library/ff607221(EXCHG.80).aspx
but everything appeared to be correct. I did not have to make any changes because everything was set as it should be according to that information.
Any help would be much appreciated.
Best regards
Katrina

Hi,
I had the same problem, and I spent a weekend looking a solution, fortunally, I have it:
Please follow this steps:
Install WinRM IIS Extension, adding this feature from Server Manager.
Change  IPv4 over IPv6 lookup preference, because the FQDN fails to find the server on TCP/IPv6.
To verify this, on Command Prompt please make this test: ping yourserver.yourdomain.domain.
Maybe you obtain TCP/IPV6 address response.
Probably the Internet Information Services (IIS) Manager dont have the binding for IPv6, only for IPv4.
To change IPv4 over IPv6 lookup group prefence, follow this steps:
Please open regedit, locate the skubkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
On DisabledComponents subkey, double click, change de value for
0x20 (or 4120 Hexadecimal). this value make  the Windows OS to prefer IPv4 over IPv6.
Repeat the test, on command prompt:
ipconfig /flushdns (Enter) to flush DNS cache.
ping yourserver.yourdomain.domain.
At this moment you obtain TCP/IPv4 address response.
To check Exchange Managment Console operation, you must restart the server.
Please restart the server.
          Best Regards,

10.6 Client and 10.7 Server Open Directory

I´ve got an Mac Mini running Lion Server. It´s configured as an Open Directory Server.
And I´ve got some 10.6 Clients running on the same local network.
All Clients have the Mini Server as DNS Server.
And now I want to use NetworkAccounts form the 10.7 Server on the 10.6 Clients.
I´ve connected the 10.6 Clients to the Server (without SSL) and all Clients say "Network Accounts available".
But if I try to log in on the Client it just shakes the login window. I´ve tried it on all my Clients with different Accounts but nothing worked.
It just won´t work! But why? Can you please help me?
What I´m doing wrong? Or is the combination of 10.6 Clients and 10.7 Server not Supported by OpenDirectory on 10.7 Server ?
Thank you !

Check your authentication against the server from one of the clients using the following command:
dscl /LDAPv3/<server name or IP> authonly <shortname of an account that cannot login>
The server name should be the same name or IP you used when binding your 10.6 client to a 10.7 server.
If you get the response "Failed to authenticate user <shortname> (tDirStatus: -14103)" you are having the same issue I was having. I found an answer to this, but you are not going to like it.
Apparently Workgroup manager and Server.app deal with accounts differently. If you are using Workgroup Manager to import a long list of accounts, don't. Server.app needs to write an addition setting that is not part of Workgroup manager or in Passenger I doesn't work correctly with accounts that have home folders that are not local. Here are the steps I used to resolve the issue:
Export all your accounts and groups
Using Server Admin, demote your OD to a standalone directory
Once the demotion is complete, use Server.app to promote your server to an OD Master
Update: I've not found it to make a difference if you use server.app or Server Admin to configure your Open Directory Master.
Once the server is again an Open Directory Master, import the users that you exported using Server.app instead of Workgroup Manager.
If you are importing groups, set the Home Directory by editing the account in Server.app before importing groups to avoid overwriting your group settings. Thankfully, you can select multiple accounts at a time.
Import your groups using Server.app
Verify group membership and test the loginsIf you test the login using the dscl command from above, you should get no error after entering the password, but as long as you have a bound client, you should be able to login at this point.
Hope this reaches you in time to help.

Binding Windows Clients to 10.7 OD Master

Has anyone here been able to bind Windows Clients to a 10.7 OD Master?

syedzaidi.nyc wrote:
http://help.apple.com/advancedserveradmin/mac/10.7/#apd52648A71-571A-433C-81A8-2 A7792333F22
States how one can do this.
@schoysi, however, I have run into the same problem as you. I am getting conflicting responses. The people at Apple were not able to provide an adequate answer and I am confused as heck. Would love to know if anyone has gotten this simple functionality to work. I know that PDC, SAMBA, and WINS are removed from both Windows 7 and 10.7 Server, however, OD is authenticating through DNS which would allow me to think that a Windows user should be able to bind through a domain name.
I would love to get as much help as possible on this. I myself have been trying every situation, and need to know if I am doing anything wrong. I truly appreciate the support.
Thanks,
Syed
The above Apple documentation suggests you can bind a Windows Vista or Windows 7 (but not XP) client to a Lion Server. However it also reads like it is talking about a PDC style domain which like you I thought was not possible with Lion Server.
Lion Server has a totally new written by Apple themselves replacement for Samba. The widely believed reason Apple did this was that when Samba switched to a GPL 3.0 license it made it effectively impossible for Apple to continue using Samba code. As the replacement code in Lion is brand new it does not yet address all needs and is likely to have a number of bugs as well.
One would hope that as time goes on Apple will be improving the new code just like iCal Server made great strides as each version was released.
I don't have a spare PC + Windows license to experiment with and Microsoft's ghastly production activation makes it a pain to redo the same machine several times.
The 'Golden Triangle' approach is definitely stated by Apple to work. This involves connecting a Lion Server to a Windows Active Directory system. One would logically also bind the Windows client to the same Active Directory system but then be able to also access the Mac server with the same account as used in Active Directory.
Of course not everyone has an Active Directory setup nor wants one. Hence in the long run the desire for Apple to eventually provide enough capability to do it all itself. This is in Samba 4 i.e. it is supposed to be able to act as a poor mans Active Directory server, but that is covered by the GPL 3.0 license as mentioned above.

SAP Client to the SAP Server: internal Error (-1102)[Message 131-183]

Hi,
We are using Windows 2008 Server R2, SQL 2008 Standard, SAP B1 8.81 PL08.
When we trying to connect SAP Client to the SAP Server. There has internal Error (-1102) occurred. We can view the database on client, but we always get the same error message after enter the User ID and Password. We have checked the native client and it is installed and also opened the following ports: 1433, 30000, 30001. We have tried to open all of firewall, but itu2019s no use.
When I set a computer in to the engine room and set the network connection, this one can connect SAP Client to the SAP Server.
But when client connect to server by VPN, the IP address will not in the same section. Then We tried to set the IP address has the same network section with the server, but it's still disable.
I set a computer for SAP Server without firewall, complex network, virtual IP and no router in my office. And use a SAP Client which is in different network domain to connect to SAP Server by internet, not VPN, but the SAP Client still canu2019t connect to SAP Server. I get the same internal Error (-1102).
It can not only ping to SAP Server IP, but telnet to the port 1433, 30000, 30001, 445.
When I use a pc with server tools, it can connect to the SAP Server by the localhost license. But if I use a computer only install client and assign the server license. The latter one always got the error.
How could we solve this problem? Is there has another setting I am missing which might be blocking the connection?
Thanks in advance.

Hi,
We are using VPN and using Terminal Licensing or Remote Desktop Conneciton.
The idea here is VPN will connect you to the network and when you are connected to the network
dont use the direct LAN IP connection use the Terminal Licensing to connect.
Again both are needed VPN and Terminal Licensing. VPN for the connection and if successfully connected
use or connect from Terminal Licensing or Remote Desktop connections.
Thanks.
Clint

[Microsoft][SQL Server Native Client 11.0][SQL Server]The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 'Items' (OITM) (OITM)

Dear Experts,
i am getting the below error when i was giving * (Star) to view all the items in DB
[Microsoft][SQL Server Native Client 11.0][SQL Server]The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 'Items' (OITM) (OITM)
As i was searching individually it is working fine
can any one help me how to find this..
Regards,
Meghanath.S

Dear Nithi Anandham,
i am not having any query while finding all the items in item master data i am giving find mode and in item code i was trying to type *(Star) and enter while typing enter the above issue i was facing..
Regards,
Meghanath

SCCM client deployment on windows server 2012 R2

Hi All,
Can some one please share the information , step by step guide to install SCCM 2007 Sp2 client installation on windows server 2012 R2 machine. IF step by step guide is there this would be really helpful.
Regards,

You have to install update http://support.microsoft.com/kb/2861663 to your SCCM server to adds support for Windows 8.1 and Windows Server 2012 R2.
Other then that should be the same as other client (Push\Logon Script\GPO etc.)
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Binding XP clients to 10.5 Server

Similar Messages

Maybe you are looking for