Hooray, the Tru64 Managers come through again! Many thanks to:
Rob <rob.naccarato_at_sheridanc.on.ca>
Darryl Cook <pgmr_at_ppalf.appstate.edu>
Oisin McGuinness <oisin_at_sbcm.com>
Bruce Senn <sennb_at_union.edu>
Paul Crittenden <crittend_at_storm.simpson.edu>
Paul gets the big prize for having a winning solution:
If you are not running enhanced security on this machine then remove the 2
C2 subsets, OSFC2SEC425 and OSFXC2SEC425. I had this same problem and when
I unloaded them things worked. I also use SECURITY=SHARE in the smb.conf
file.
Other suggestions were:
1. From Rob Naccarato:
For -L to work, make sure you have a guest account.
man smb.conf and look for 'guest'.
2. Darryl Cook said:
I assume you are using win95 to login? I ran into a
problem very similar to this. I cant remember the exact
error but what was happening was that win95 was sending the
password in all caps and the unix end wouldnt validate my
password. There is a very easy fix to this. It involves
running areg on the win95 end and setting some stuff. If
you think this is along the same lines send me your fax
number and I can fax the stuff to you. Its a couple of
pages long. Its in the samba docs but sorda hard to find.
3. Oisin McGuinness said:
Which system did you configure and build Samba on? The configure
script in the source directory will set different build flags depending on
whether
it finds the security library and API's (header files). Take a good look
at the -D stuff in the Makefile that configure generated.
A quick guess is on one of the machines there is a mismatch between
the security mode Samba was built with and the security mode the machine
runs in.
It is possible to give arguments to the configure script to force certain
options...
4. From my buddy Bruce Senn:
Sounds to me like Samba is assuming enhanced security. Maybe a
compiled-in option, or maybe 4.0E. Maybe once the client system thinks
you are enhanced security it can't change its mind.
FWIW, we used to get a bogus password error message from Eudora when a
user was not in the authorization file. Basically the bad password error
message meant, I can't log in for any reason.
Thanks to all, and I hope one of these answers works for the next person!
Sheryl
% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %
% Sheryl A. Lemma Internet: lemma_at_lvc.edu %
% Assistant Director Voice: (717)867-6060 %
% Administrative Computing FAX: (717)867-6019 %
% %
% L E B A N O N V A L L E Y C O L L E G E %
% %
% Tru64 Unix 4.0E, Coll: Live 16, Dev 16, Ben: Live 5.0, Dev 5.0 %
% %
% Visit my Personal Web Page at %
%
http://www.geocities.com/Heartland/Plains/4407/ %
% %
% Never underestimate the power of a smile! %
% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %
Received on Tue Jun 15 1999 - 20:36:18 NZST