Nicholas: Regarding your problem: "The SGI server is only serving files, no home directories, no printers (we have separate NT servers for each of those functions), and it is using "SERVER" level security. Encryption is on. Guest logins are disabled ... I'm confused greatly by this - one day, a user's login will work, another day, it'll suddenly stop working. " Please read the text document DOMAIN_MEMBER.TXT, that came with the Samba code and try authenticating with "domain" rather than "server" In brief here's what you'll do: 1) Run from an NT server or workstation with access to, SRVMGR.EXE and added your Samba machine to the domain. 2) Edit SMB.CONF [global] section [global] security = domain encrypt passwords = yes 3) Enter the following from your Samba server's command line:>./smbpasswd -j YOUR-NT-DOMAIN -r YOUR-PDC-NAMEI was inspired to try this by reading the article Linux World Article "Doing the NIS/NT Samba" http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html I have Implement "domain" rather than "server" and it works well.>From the DOMAIN_MEMBER.TXT here's what tipped me off the to probable cause of your troubles:"In addition, with "security=server" every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run out of available connections. With "security =domain", however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. " I hope that resolves your problem. The best advice I can give you regarding computer systems is to stress the economic benefits of a system and don't forget to include intangibles like uptime and reliability. How much does it cost when a system shuts down. How much is your company's yearly expenditures in licensing/support? What benefit does your company derive from it. Being hit across the head by the bottom line inspires more change than some of the best technical arguments. Cheers, Steve "The pictures, words, and descriptions of these comments are my own and not PeopleSoft Inc or Major League Baseball." __________________________________________________________________ Jump! on '99 with FREE calendars and e-mail at http://www.jump.com
You're using the old smbmount command. You need the one from Samba 2.0.3 to use with the new kernel - I got this to compile and install with the help of some comments at: http://www.wittsend.com/mhw/smbmount.html by editing the samba/packaging/RedHat/samba2.spec file and adding a "--with-smbmount" flag to the configure: ./configure --prefix=/usr --libdir=/etc --with-lockdir=/var/lock/samba --with-privatedir=/etc --with-swatdir=/usr/share/swat --with-smbwrapper --with-automount --with-quotas --with-smbmount I then magled the makerpms.sh script a little since it didnt' quite do permissions right on my machine. [root@baal RedHat]# diff makerpms.sh makerpms.sh.tmpl 10,12c10,11 < #( cd ../../.. ; chown -R ${USERID}.${GRPID} ${SRCDIR}/samba-2.0.3 ) < #( cd ../../.. ; tar czvf ${SRCDIR}/samba-2.0.3.tar.gz samba-2.0.3 ) < ( cd ../../.. ; tar czvf ${SRCDIR}/samba-2.0.3.tar.gz samba-2.0.3 ) ---> ( cd ../../.. ; chown -R ${USERID}.${GRPID} ${SRCDIR}/samba-PVERSION ) > ( cd ../../.. ; tar czvf ${SRCDIR}/samba-PVERSION.tar.gz samba-PVERSION )15,17d13 < ( cd ../../.. ; chown ${USERID}.${GRPID} ${SRCDIR}/* ; chown -R ${USERID}.${GRPID} ${SRCDIR}/samba-2.0.3* ) < ( cd ../../.. ; chown -R ${USERID}.${GRPID} ${SPECDIR}/{smb*,samb*} ) < ( cd ../../.. ; chown ${USERID}.${GRPID} ${SPECDIR}/* ) and then went to /usr/src/redhat/SPECS and did "rpm -ba samba2.spec" and then to RPMS to do a "rpm -Uvh samba-xxx" (The short point in all this is you need to compile with --with-smbmount, but it took me a few tries before I actually got the new smbmount installed and found it). Note that this installs the smbmount in /usr/bin/smbmount and not /usr/sbin/smbmount where the other one went. The Web site mentioned includes a script to run the appropriate smbmount depending on if you have a 2.2 or 2.0 kernel. Bill "B. James Phillippe" wrote:> > Hi, > > Thanks for answering my question on the new smbmount not working. I tried > all variety of combinations on the commands you suggested, but they all > simply do this: > > % smbmount -c //server/share 'mount /mnt/samba-share -n CLIENT -U user' > Usage: smbmount service <password> [-p port] [-d debuglevel] [-l log] > Version 2.0.3 > -p port connect to the specified port > -d debuglevel set the debuglevel > -l log basename. Basename for log/debug files > -n netbios name. Use this name as my netbios name > -N don't ask for a password > -m max protocol set the max protocol level > -I dest IP use this IP to connect to > -E write messages to stderr instead of stdout > -U username set the network username > -W workgroup set the workgroup name > -c command string execute semicolon separated commands > -t terminal code terminal i/o code {sjis|euc|jis7|jis8|junet|hex} > -D directory start from directory > > Perhaps there is something else I need to do? > > Again, the old smbmount works perfectly every time with: > > smbmount //server/share /mnt/samba-share -c CLIENT -U user -P passwd \ > -u nobody -g nobody -f 666 -d 777 > > thanks, > -bp > -- > B. James Phillippe . bryan@terran.org > Software Engineer, WGT Inc. . http://www.terran.org/~bryan-- Bill Eldridge Radio Free Asia bill@rfa.org