[EMAIL PROTECTED] wrote:
--On Friday, June 18, 2004 12:04 AM -0400 Jeffrey Altman <[EMAIL PROTECTED]> wrote:
There was a race condition associated with the establishment of global drives which was fixed post-1.3.64. Please try one of the daily builds and see if it indeeds solves your problem. Or does not make it worse.
I installed 1.6410. There was no change in behavior. Rebooting after enabling a global drive, and then logging in trips the NOCM error. Disabling the global drive and rebooting allows everything else to work fine. Integrated logon to the MIT KDC is fine.
My problems are not major issue for me. I get by fine without global mappings. When I do get it working right, I will implement roaming profiles. That is my interest in global mappings.
Later, Jason
Please try to be very specific in describing your scenario. I have a global drive mapping G: to /afs/all and this appears to work
just fine for me. As expected, G: does not appear in the list of drive mapped as reported by NET USE.
I do wonder however why you need global mappings to implement roaming profiles. You should be able to implement
roaming profiles via the use of UNC paths.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
