SMB automount problems

[Anonymous]

I am new to this forum, so please ignore any naive mistake I am going to make.

I have successfully integrate the AD and OD for my office. The Windows server system is win2003 and MAC server is 10.3.9. I can login a mac (10.3.9) with a managed user authenticated by AD.

Two problems:
1. I did set the profile folder to //server/home/username in AD user property. At the first time I login, I can see the HOME folder is automounted, and is shown on the desktop and the dock. Then, if logout, and login again, the home folder will no longer be automounted, but I can use "Command+K" to mount it. No matter how many times I do logout-and-login-again, or restart the computer, the home folder cannot be automounted. The funnest thing is that, if I turn off the computer and have a good night. The next morning I boot up that computer and login with the same user, the home folder can be automounted again!!!! But if I logout and login again, no go. This scene happens everyday! What do you think is the problem?

I check the system.log. The fist time I login, there is no error message, but the logins after that one shows the following err message:
/System/Library/CoreServices/SecurityAgent.app/Contents/MacOS/SecurityAgent: MCXSecurityAgent: Skipping mount of kDSStdRecordTypeUsers/kDSNAttrOriginalHomeDirectory as "abcdef": Missing or badly formed URL.

So is the win server’s problem or the ad plugin’s?

2. This one might be not a problem. But I just want to make sure. When the hoem is successfully automounted, the HOME icon on desktop links to the //server/Home, but not //server/Home/username/. Is it possible to let it link to user’s own folder instead of the share point?

Thanks a lot. You help sure helps me!

[Anonymous]

nobody can answer me??? bump bump…
even a word on "sorry about that" or "That was easy" is welcome.
Thanks again.

[mhelman]

I have seen this happen as well. Here’s some things to check:

Are your clients being managed by an OS X Server computer list as well as authenticating to AD? If so, I found that trying to cache the settings caused problems.

Are you mounting the SMB share with AFP as well from the same client? This (as I’ve been told) is not a good idea and I would agree as it can cause some problems similar to what you describe.

HTH.

[Anonymous]

Thanks for the reply.

Yes, my clients are managed by an OS X server and authenticated to AD. And when you said "cache the setting", did you mean "Mobile User" in the Mac clients? I did not set the test user to be a mobile user. If you did not mean that, where I can check to not to cache the setting?

I don’t think I mount the SMB share with AFP. actually I have no idea how to do that and why we need to do that.

So, what else you can figure out I should check? I am using the wireless connection and a DHCP server who assigns the ip address in a different subnet from the one of the AD/OD server. Say
Client : 192.168.100.1
AD : 192.168.300.100
OD : 192.168.300.110

Do you think that is a problem? Maybe not?

Thank again

[QUOTE BY= mhelman] I have seen this happen as well. Here’s some things to check:

Are your clients being managed by an OS X Server computer list as well as authenticating to AD? If so, I found that trying to cache the settings caused problems.

Are you mounting the SMB share with AFP as well from the same client? This (as I’ve been told) is not a good idea and I would agree as it can cause some problems similar to what you describe.

HTH.
[/QUOTE]

[mhelman]

If you are managing your Mac client via a Computer List on the Mac OS X Server (OD) then you will want to make usre you try the default settings first. If you did not change the cache setting for your managed Computer List then it is already at the default.

Try working with the most basic setup you can first and see if everything works properly. If so, start to add in your other settings one at a time.

You may also want to check and search the Apple Discussion Lists http://lists.apple.com/archives/ as there are many asked and answered questions there that may help.

[Anonymous]

ok, I guess I might find the probelms to the first question.

After I change the setting in AD user property, I finall successfully solve the problem. I can see the Home Dir automounted everytime I login the Mac.

FYI, who has the same problem, just do the following in windows server:
“Users and Computers” >> User Properties >> Account >> Account Options >> Check “Use DES encription types for this account”.

But I still not understand what’s the matter. Are there something about “digital sign” things we disabled in the domain controller properties??

Any follow ups? Thanks!

[Anonymous]

and by checking “Trusted for delegation” solve the problem too. So I guess that is caused by the ad security setting, instead of the problem of ad plugin.

Thank you, mhelman, for giving me useful information.

[mhelman]

Hi,

That’s correct, SMB signing is not supported. Good work solving the problem!

If you require SMB signing then you can look at a product called ADmitMac at http://www.admitmac.com/.

Mark

[Author]

Posts