On 02/ 7/11 10:05 AM, John Ryan wrote:
Hi,
I have 2 problems, that sound related, but might no be.
My server is running snv_134, and connected to an AD domain.
1. I'm using a CIFS share for my Windows roaming profiles. Sometimes, a
Windows machine complains it can't read the NTUSER.DAT file and logs the
user on with a temporary profile. Logging the user off, deleting their
profile, and restoring a previous version fixes the problem.
The file NTUSER.DAT exists in the proper place, and has the correct ACLs.
I don't recall that we've had any such problem report.
Could you qualify and/or quantify "sometimes" a bit more?
How often and/or with how many users does this happen?
Do you see this with a specific Windows version as client? If yes, what
version?
What's your domain controller OS (specific flavor)?
2. If an Office application crashes, and a user tries to open the file
again, Windows complains that it can't open the file. If the user waits
an hour or 2, he/she can open the file again.
Is there a way to see the locks on the file and preferably remove them?
Try connecting to your Solaris with Windows Computer Management Console.
In the tree view panel, under System Tools-> Shared Folders -> Open
Files, if you can see the file you have problem with then try to close
it.
You are running a relatively old build, have you considered using
Solaris Express 11? It's running snv_151a. I don't know what's the
terms of use for that, so you would need to check that out.
Afshin
Regards
John Ryan
_______________________________________________
cifs-discuss mailing list
cifs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
_______________________________________________
cifs-discuss mailing list
cifs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
