I have searched the archives and the internet and found nothing on this topic but I know it's a known issue. Second I would like to say this has nothing to do with NTDOM. I am running a samba server 2.0.0 on a freebsd box. I am connecting to the server using windows 9x and NT clients. I have hacked the windows registries to enable clear text passwords across the lan. The problem is when you log into the NT workstation, you have to re-enter the password to connect to samba shares even though the initial login password is the same as the samba password. The windows 9x clients do not have this issue when remounting shares when you log in. We run a variety of different samba servers and becomes increasingly annoying when you have to enter the same password 10 times when logging into the NT box after rebooting (which is done often for obvious reasons). Any help would be appreciated. Thanks, -Chad
> I have searched the archives and the internet and found nothing on this > topic but I know it's a known issue. Second I would like to say this has > nothing to do with NTDOM. > > I am running a samba server 2.0.0 on a freebsd box. I am connecting to the > server using windows 9x and NT clients. I have hacked the windows > registries to enable clear text passwords across the lan. The problem is > when you log into the NT workstation, you have to re-enter the password to > connect to samba shares even though the initial login password is the same > as the samba password. The windows 9x clients do not have this issue when > remounting shares when you log in. We run a variety of different samba > servers and becomes increasingly annoying when you have to enter the same > password 10 times when logging into the NT box after rebooting (which is > done often for obvious reasons). Any help would be appreciated. > > Thanks, > -ChadWe have the same problem. We're running: Samba 2.0.4b with "security = user", and public access to printers disabled. on SunOS 4.1.4 WinNT 4.0 Workstation sp5 There's also a related problem for accessing printers - until a disk share is "logged onto" on the system that serves the printer, printer connections are refused. It all works fine after an initial connection is made to a disk share. Everything works fine from Win95 boxes using the same servers. We prefer to disable public access to the printers - this makes the user the owner of the print job on the Unix box, and the user can remove the job from the queue without bothering the system administrator (me!). I have also searched the archives, and found three similar complaints: Daniel Grandjean, 30 Apr 1998, Printing from NT4 public=no Sean Murphy, 28 Jan 1998, NT Printing woes James Strauch, 17 Dec 1998, Samba Printing Question but, alas, there were no responses in the archives. I've also noticed that it seems to be the habit of list members not to send responses to questions to the mailing list :-( Thanks in advance for any help....
When the world was young, "Chad Thunberg" <chadth@atvideo.com> carved some runes like this:> I am running a samba server 2.0.0 on a freebsd box. I am > connecting to the server using windows 9x and NT clients. I have > hacked the windows registries to enable clear text passwords > across the lan. The problem is when you log into the NT > workstation, you have to re-enter the password to connect to > samba shares even though the initial login password is the same > as the samba password. The windows 9x clients do not have this > issue when remounting shares when you log in. We run a variety > of different samba servers and becomes increasingly annoying when > you have to enter the same password 10 times when logging into > the NT box after rebooting (which is done often for obvious > reasons). Any help would be appreciated.It sounds like you're running samba in user level security mode (ie, security = user) and do not have an NT PDC to handle authentication. Is that right? I suppose share level security would produce the same behavior... Have you tried running one samba box as a password server and pointing the other samba boxes in that direction? AFAIK, there's no PDC functionality in samba 1.9.x (only basic domain logins) but the 2.x tree has more and more PDC support in each version. Even without turning on the PDC stuff, couldn't you use domain login scripts (actually cheesy batch files) to specify the passwords and mount the shares? I'm not sure about the permissions on the batch files (visibility of passwords, etc), but it's worth a shot. Steve ************************************************ Steve Arnold CLE (Certifiable Linux Evangelist) http://www.rain.org/~sarnold
Hi Chad. I am using Samba 2.0.4. Encrypted passwords are supported and enabled. You need to add smbpasswd for each user so that samba can store a hash code on every user`s password. Hope it helps. Bye, Levent.> I am running a samba server 2.0.0 on a freebsd box. I am connecting to the > server using windows 9x and NT clients. I have hacked the windows > registries to enable clear text passwords across the lan. The problem is > when you log into the NT workstation, you have to re-enter the password to > connect to samba shares even though the initial login password is the same > as the samba password. The windows 9x clients do not have this issue when > remounting shares when you log in. We run a variety of different samba > servers and becomes increasingly annoying when you have to enter the same > password 10 times when logging into the NT box after rebooting (which is > done often for obvious reasons). Any help would be appreciated.
Chad Thunberg wrote:> > I have hacked the windows registries to enable clear > text passwords across the lan. The problem is > when you log into the NT workstation, you have to > re-enter the password to connect to samba shares > even though the initial login password is the same > as the samba password. The windows 9x clients do not > have this issue when remounting shares when you log in. > We run a variety of different samba servers and > becomes increasingly annoying when you have to enter the same > password 10 times when logging into the NT box after > rebooting (which is done often for obvious reasons). > Any help would be appreciated.Windows NT will not transmit the plain text password automatically to any SMB server. Thus the password prompt. However, the exception to this is when a user is logging on and NT is connecting the user's home directory. Also it is good to remember that validation to a server in user level security is only necessary for the first resource conneciton. For example, net use h: \\server1\homes password prompt: the command completed successfully. net use i: \\server1\apps the command completed successfully. Hope this helps, jerry ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
Glenn Burkhardt said:> There's also a related problem for accessing printers - until a disk > share is "logged onto" on the system that serves the printer, printer > connections are refused. It all works fine after an initial > connection is made to a disk share.This is basicly a feature of NT clients and nothing can be done about it. We tried 2 different workarounds: a) always send print requests to the server from which users mounted home directory - on grounds would be connected to & thus authorisation would work. b) Our final solution: use BSD lpr to access printers rather than SMB from the NT clients. -- ----------------------------------------------------------------------------- | Peter Polkinghorne, Computer Centre, Brunel University, Uxbridge, UB8 3PH,| | Peter.Polkinghorne@brunel.ac.uk +44 1895 274000 x2561 UK | -----------------------------------------------------------------------------