hi ya michael
for the differences in //myserver/myfiles vs myserver.uleth.ca
seems like a dns problem... ( get rid of /etc/hosts and /etc/lmhosts ... )
for login authentification...
- try using yp - i hate yp...cloggs/hangs the network
- try using ldap - your method
- try using rsync
- try using pam
- try using smbpasswd
- anything that will send passwd encrypted....
for file sharing...
- try nfs ( notoriously insecure )
- try using coda
it is not(??) a good idea to have home directories for each of the 5,000 users...
group them together 1,000 on 5 primary servers... and backup 5 servers...
- rest of them are just workstations - no backups... already have many different
workstations .... use rdist or mirror to keep those machines backedup/updated
--------
in your smbmount -I option is being mixed with non-existent(?) autofs options....
have fun
alvin
> I think I should explain my problem a little better...
>
> These linux machines will be setup in central student labs and be available to the
> general student population (5000 users). Because of the insecurity involved with
> the labs there is no way I can use nfs. I would like to use autofs and smbmount but
> have it done automagically for the user. I want to have their samba share mounted
> as their home directory where all configuration files will be written.
> e.g. .bashrc /Desktop for kde/gnome ect
> Another problem I have is with the server myserver. Let us say that \\myserver for
> the windows network is 142.66.1.2. In the dns tables there is a server called
> myserver.uleth.ca which is aliased to myserver (let us say 142.66.1.3). When I try
> to smbmount using //myserver/myfiles I get a connection refused because
> myserver.uleth.ca is not the same as \\myserver (I am not responsible for this
> naming convention).
>
> Perhaps what you have explained below will work for what I am trying to do but from
> my limited experience with linux is does not seem to solve the problem.
>
> What I would like to do is
> If user testuser1 logs on to the linux box it will mount their \\myserver\myfiles to
> /home/testuser1.
> In my situation I have to use the -I option with smbmount because of the naming
> problem explained above. I could probably have a new name made up (for example
> \\myfiles2) if autofs can't support the -I option.
>
> I don't know if this is possible because the password has to be sent to the server
> as plaintext.
>
> I hope I have explained my problem a little better this time. If anyone else has
> run into this type of situation and have a different
> (secure) solution I would be interested in hearing about it. This is my
> situation....
>
> Solaris file server (call it fileserver1) with everyones disk space
> Solaris file server which nfs mounts fileserver1 and runs samba and netatalk to
> share peoples user space to clients
> Macintosh labs running from OS 7.6-8.6
> PC labs running win9x/NT/Linux with 4 of the central PC labs dual booting
> win98/Linux
> I will be using ldapns (www.padl.com or www.rage.net/ldap for more info) which is a
> name service switch for authentication off a ldap server (Netscape Directory
> Server). When a user logs on it passwd uid,gid,home directory ect to the linux
> box. The only local user on the linux box will the the root user. Everyone else
> will authenticate off the ldap server.
>
> Mike
>
> ---
> Michael Mercier
> System Support
> Student Computer Labs
> University of Lethbridge
>
>
>
