> You should be using NIS (http://www.bresink.com/osx/nis.html) or > something similar to manage user security (I am familiar with NIS but > this article suggests there may be more appropriate solutions for a > all-Apple network). Users should be authenticating to a nameserver and > should be able to log onto any machine on the network. Local user ids > should exist as a fallback for when the network is unavailable, but I > can see no reason why an application such as you describe (what exactly > is it?) would use local ids.
We use ADmitMac, since our network is a Windows Active Directory domain. Not the most reliable of apps, but it allows the Mac users to authenticate to the network and Windows servers transparently. If there is a way to access a Mac over the LAN using root (or similar) privileges on a Windows network without using a local account, I'm all ears. ************************************************************************ * ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in <== * ==> the body of an email & send 'em to: [EMAIL PROTECTED] <== * Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name * Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST * Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L * New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress * Need more help? Send mail to: [EMAIL PROTECTED] ************************************************************************ * List archive at www.mail-archive.com/computerguys-l@listserv.aol.com/ * RSS at www.mail-archive.com/computerguys-l@listserv.aol.com/maillist.xml * Messages bearing the header "X-No-Archive: yes" will not be archived ************************************************************************
