[ale] Wierd Samba problem

[Dow Hurst]

You ought to see if you can have your Samba authenticate 
with the WINS server.  Or set up Samba to authenticate using 
whatever your company uses.  The Win2k machine held on to 
the current Samba share until it needed to reauthenticate 
with the new password.  Each user has one password for 
validating the shares.  At least this is my experience so 
far.  Others more versed in MS etiquette might know of many 
ways to have multiple passwords for a user, or just better 
ways to do what your doing.
Dow


Jim Lynch wrote:
> We had a power failure overnight and one of my Linux boxes rebooted.  My 
> win2k system was hosed 'cause the samba share went missing so I had to 
> reboot it.  It's on a UPS so it didn't go down.  When win2k came back 
> up, I tried to map the samba drive and it wouldn't map.  Told me I had a 
> bad pw or user name.   To make a long story short, I had to change my 
> samba password on the Linux box to be the same as my 2k password.  Then 
> it worked.   We have password expiration on the MS systems here and the 
> other day I was required to change it.  But I've rebooted 2k a couple of 
> times and I was able to map the share OK then.  It wasn't until the 
> Linux box rebooted that I ran into a problem.
> 
> Can anyone shed light on this seemingly strange behavior?  I assume I've 
> got something weird in my smb.conf file.
> 
> Thanks,
> Jim.
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
> 

-- 
__________________________________________________________
Dow Hurst                  Office: 770-499-3428            *
Systems Support Specialist    Fax: 770-423-6744            *
1000 Chastain Rd. Bldg. 12                                 *
Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
Kennesaw State University         Dow.Hurst at mindspring.com *
Kennesaw, GA 30144                                         *
************************************************************
This message (including any attachments) contains          *
confidential information intended for a specific individual*
and purpose, and is protected by law.  If you are not the  *
intended recipient, you should delete this message and are *
hereby notified that any disclosure, copying, distribution *
of this message, or the taking of any action based on it,  *
is strictly prohibited.                                    *
************************************************************