Please bear with me as I am very much an OSOL newbie. I'm setting up an OSOL server (in VirtualBox) to be joined to a Windows Server 2008 R2 domain. Things seem to be working fine up to the point that I can use smbadm to join the machine to the domain. At this point, I can see the machine from my Win2k8 server by going to \\osolserver and I can see the one test share that I have created. I can even adjust its permissions (I did 'chmod A=eveyrone@:full_set:fd:allow' on it so that I can just get Windows to do the management with my various users); when I give a domain user access to a share, doing 'ls -V' shows the ACL stored using (what I take to be) the ephemeral ID. I can't change the share's owner from Windows, though, but I think this won't be too important.
Now these last steps aren't strictly necessary, but I figured I'd try them out for the fun of it so that I can see the actual user instead of the ephemeral ID, and do so without having to do a manual mapping (I would rather avoid having to create an OSOL user for each AD user to do any admin on the OSOL-side). I ran kclient as well as enabling the idmap and name-service-cache services, and I also copied /etc/nsswitch.ad to /etc/nsswitch.conf. Now when I try to access the OSOL box through Windows Explorer I get this error: "\\osolserver is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in from this station." Does anyone have any clue what might be causing this? Interestingly, I get the above error when trying to access it via \\osolserver, but not when using its IP address directly (i.e. \\192.168.1.2 or whatever). This isn't the most important thing in the world, but it would make the OSOL side of the administration a mite nicer. TIA! -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
