[Ross]

Just make sure you use the “changeip” command, you NEED to use this if you change IP’s.

[Ross]

Well, it seems to be an issue with your client since that error is not the typical error when Windows can’t see a Domain. Maybe is the way your joining…. Are you right clicking My Computer then going into the “Computer Name” tab and changing it to DOMAIN and putting in the “SOMETHING” for the domain.

This is an XP client right out of the box?

[Ross]

It depends… If your just managing via computer lists there is no need. But if your managing via OD groups with AD users or have shares on your master that AD users/groups will need to access you will need to.

[Ross]

I actually ran into this today… I had to choose “Standard” for Auth. under AFP to get it to work (Kerb or Any method did not work), this was only with replicas and connected to directory servers. The master was not a problem..

[Ross]

Take a look at this, see if it helps

http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=22988&DisplayTab=Article

[Ross]

Your server wouldn’t be accessible to the outside world would it? Meaning it has an outside IP or doing NAT?

[Ross]

Thats your problem….. its not an AD server, its an NT server. Just try it

[Ross]

its sounds like your trying to bind the XP machine to the Domain “somthing.com” this is not right. The NT domain should not have any “.” dots in it. What you should be binding to is what is listed in the Windows section for the OSX server under domain. This should not have dots and should just be “SOMEDOMAIN”. OSX server shouldn’t even allow dots in a PDC domain.

[Ross]

Or you could hard code the attributes into the clients, but this will only work if your home directories are on one share point. Its much better to add the attributes or extend the schema.

The three you REALLY need are:
apple-user-homeurl
homeDirectory
uidNumber

You may be able to Map the uidNumber to something that already exist on your Novel server but the rest will have to be entered.

Don’t forget your mount records as well, I take it your OSX server is providing this?

[Ross]

You shouldn’t see the server IP as a directory in WGM, if you have it setup right you should only see 127.0.0.1. I would check Directory Access on the server and make sure you didn’t bind the server to its self some how.

[Ross]

My bet is that it is creating the home directories but in the wrong place. Go to folder “/Volumes/” and see if you see more then one RAID. You can also select a user and verify the right information in the WGM inspector for that user.

[Ross]

How many Windows connections? I have found this when I have over 100+ connections on one server. Last time I talked to Apple people they were recommending no more then 125 for one server.

[Ross]

First you shouldn’t be binding X.4 clients via the AD plug-in to your OSX PDC. The client plug-in is for AD servers not a PDC which is NT and not even close to the same thing.

Now for your windows setting on your OSX server, the domain should not be a fully qualified domain. Its your NT domain so just make it “MYDOMAIN” or something. The OSX server shouldn’t even except a fully qualified domain in that field. Then just make sure WINS is working right and you should be able to bind your XP clients to your PDC.

[Ross]

I have used the whole serial number and had it work with 10.3.9… Give that a shot.

[Ross]

Disk1 1 is the right one… You don’t want to delete that. Read my post again… What happens a directory gets created in Volumes (Disk1) then when your volume comes up it gets renamed (disk1 1) If you remove (just move) (disk1) which should be a directory and reboot it will automatically get named back to disk1.

[Author]

Posts