Sims 2 - Crashes when iMac part of an open directory domain

Question

Having a weird issue with running the The Sim 2 on my Kids machines.
Some background, we have an Aluminum intel iMac and am intel Mac Min both running Leopard 10.5.6 which are connected to an old G4 DP800 running Leopard Server 10.5.6. When I installed the Sims 2 on the iMac or the Mac Mini it crashes almost immediately when you try to run it. Got onto Aspyr, went back and forward with them and they couldn't replicate the issues.
Eventually I tried installing a fresh copy of Leopard 10.5.6 on an external USB drive and booting off that. It worked.
Now for the fun part. Having been able to run the Sims 2 successfully from this vanilla usb install of 10.5.6, I then tried adding this back into the Open Directory domain, still running form the USB drive, all I did was add the machine back into the open directory domain, I didn't reboot, I didn't log out and back in again all I did was open directory utility, added the machine to the open directory domain and then re-ran The Sims 2, and you guessed it, it was crashing again.
Just in case I did anything wrong, I repeated the whole process, and found this is repeatable, as soon as I the machine back into the open directory, then Sims 2 crashes.
The attitude from Aspyr when I related all of this to then was that I had a "non standard" setup.
It's a real pain having to keep a vanilla 10.5.6 install and having to re-boot each time to run this game, does anyone have any ideas or suggestions on this?
TIA
Dave

Answer 1

So I finally got it to work.
The Mavericks set up DNS assistant seems to add your local domain into the FQDN so you end up getting 'macsvr.domain.domain.com'
I uninstalled server, removed the /Library/Server folder also Server.app and two files in /Library/Preferences. Serverd.plist and servermgrd.plist.
I restarted server and let it do a first run, I set up my host name asking to set up DNS.
I then went into DNS, deactivated it and edited the domain. I then added NS and machine records, reverse lookups and finally made sure the FQDN was in the correct zone. I repeated this for the intended replica and created my OD replica on first run.
Check everything is good by using terminal, using the cmd: nslookup <ip address> for both master and replica, then: nslookup <FQDN> then: host <ip address>
This should resolve both OD master and OD replica IP and hostname
Hope this helps anyone else stuck on the set up.