We are running Samba 1.9.17alpha5 with Win95 OSR2 clients. We have a very annoying intermitent logon problem where the clients don't seem to run the netlogon script and then gain access to the desktop as the previous user including the connection to their home share. From the Samba logs, the client appears to not always make a connection to the [netlogon] share to run the logon script. It does, however, always connect to [netlogon] to open the config.pol file, which is always run after the logon script. We are using Kixtart version 3.37 (or whatever the latest version is), and we've noticed an occassional share violation on the kix32.exe file in the Samba logs. We've also just noticed a new error in the Samba logs that says, "Connection 23 not open". What the heck does that mean? Any and all help greatly appreciated.
On Tue, 26 Aug 1997, Rob Naccarato wrote:> > We are running Samba 1.9.17alpha5 with Win95 OSR2 clients. > We have a very annoying intermitent logon problem where > the clients don't seem to run the netlogon script and then > gain access to the desktop as the previous user including > the connection to their home share. From the Samba logs,ah, _you're_ seeing this occasionally, are you? GOOD! so am i :-) if you have any NT workstations, you should be able to see these symptoms (seeing [homes] and [user1] AND [user2] at the NetShareEnum level) every single time. it happens, i think, when the first user (user1) logs off, and somehow this logoff doesn't trigger the smbd process for user1 to die. normally (under w95) it does. under NT, at the moment, it definitely doesn't. a login by user2 immediately afterwards will connect using the smbd process previously used by user1. OOPS! because the shares are still set up, particularly the [homes] share, for user1. then, you get [user2] created, but the share [user1] still exists! i have only been able to reproduce the problem, not fix it: i've sent details, as best i can, to the other samba team people, so that those more familiar with smbd (where the problem lies) can fix it. in the mean-time, i keep on hacking a local copy of smbd to see if i can narrow this down some more.> the client appears to not always make a connection to the > [netlogon] share to run the logon script. It does, however, > always connect to [netlogon] to open the config.pol file, which > is always run after the logon script.[hm. personal question: how did you get it to open / load the config.pol file?]> We are using Kixtart version 3.37 (or whatever the latest > version is), and we've noticed an occassional share violation > on the kix32.exe file in the Samba logs. We've also just > noticed a new error in the Samba logs that says, "Connection > 23 not open". What the heck does that mean???? absolutely clueless. Kixtart (hur hur). is that the program that modifies the registry? particularly, it's being suggested for use in modifying the local profile directory location to an SMB share, making you appear to have roaming profiles, where instead you're just wasting bandwidth every time you look at the start menu?> Any and all help greatly appreciated.if anyone else knows anything about this, can apply some brain-power to smbd, or anything, i'd also appreciate hearing from you, through the digest. regards, luke
[please excuse the (possibly stupid) nature of the indentation on this
posting: i installed office 95 after installing exchange client, and
it's overwritten my default viewer. given that i am with pi for only
four more working days, i'm going to leave it as it is].
BIG NOTE - lkcl@pires.co.uk will become invalid from the end of august
1997.
right - we understand what's going on, and the bottom line is, you
can't use the [homes] share at the moment to store profiles. it _has_
to be the share _generated_ from the [homes] share.
for NT, this is because there is a background process that downloads
profiles for you, that doesn't drop the connection just because a user
logs out. therefore, the [homes] share will still be redirected to
the old user, and the background process (probably WINLOGON.EXE) still
has valid file handles open on this [homes] share. for w95, if there
is a problem with some logout or some file handles whereby a file is
still open on the [homes] share, w95 will intermittently display the
same symptoms, namely:
when the second user logs in, the [homes] share will still be pointing
to the old users' directory, except that they won't be able to access
any of that user's files because smbd will have done a setuid() to the
new user.
we'll be looking into this, to find a solution: if nothing else, we'll
have to enforce "browseable = no" on the [homes] share, which will
catch everyone out who is using it ("i'm trying to use roaming
profiles and i can't get it to work") but at least when "logon
path =
\\%L\%U\profile" (which i will suggest be made the default, for
compatibility with both NT and w95) instead of "logon path =
\\%L\HOMES\profile" no-one will get caught out by the above problem.
rob, are you using the current default of "logon path = \\%L\HOMES"?
luke
----------
From: Luke Kenneth Casson Leighton[SMTP:lkcl@cb1.com]
Sent: Monday, August 25, 1997 7:46 PM
To: Rob Naccarato
Cc: Multiple recipients of list
Subject: Re: Win95 clients not logging in to Samba
On Tue, 26 Aug 1997, Rob Naccarato wrote:
>
> We are running Samba 1.9.17alpha5 with Win95 OSR2 clients.
> We have a very annoying intermitent logon problem where
> the clients don't seem to run the netlogon script and then
> gain access to the desktop as the previous user including
> the connection to their home share. From the Samba logs,
ah, _you're_ seeing this occasionally, are you? GOOD! so am i :-)
if you have any NT workstations, you should be able to see these
symptoms
(seeing [homes] and [user1] AND [user2] at the NetShareEnum level)
every
single time.
it happens, i think, when the first user (user1) logs off, and somehow
this
logoff doesn't trigger the smbd process for user1 to die. normally
(under w95) it does. under NT, at the moment, it definitely doesn't.
a login by user2 immediately afterwards will connect using the smbd
process previously used by user1. OOPS! because the shares are still
set up, particularly the [homes] share, for user1.
then, you get [user2] created, but the share [user1] still exists!
i have only been able to reproduce the problem, not fix it: i've sent
details, as best i can, to the other samba team people, so that those
more familiar with smbd (where the problem lies) can fix it. in the
mean-time, i keep on hacking a local copy of smbd to see if i can
narrow
this down some more.
> the client appears to not always make a connection to the
> [netlogon] share to run the logon script. It does, however,
> always connect to [netlogon] to open the config.pol file, which
> is always run after the logon script.
[hm. personal question: how did you get it to open / load the
config.pol
file?]
> We are using Kixtart version 3.37 (or whatever the latest
> version is), and we've noticed an occassional share violation
> on the kix32.exe file in the Samba logs. We've also just
> noticed a new error in the Samba logs that says, "Connection
> 23 not open". What the heck does that mean?
??? absolutely clueless.
Kixtart (hur hur). is that the program that modifies the registry?
particularly, it's being suggested for use in modifying the local
profile
directory location to an SMB share, making you appear to have roaming
profiles, where instead you're just wasting bandwidth every time you
look
at the start menu?
> Any and all help greatly appreciated.
if anyone else knows anything about this, can apply some brain-power
to
smbd, or anything, i'd also appreciate hearing from you, through the
digest.
regards,
luke
ok - smbd's shouldn't exit under 1.9.16p11, either. if they do, then i'd like to know how! the \\%L\HOMES connection in password.c, and the \\%L\homes later in the code, you will need to change to \\%L\%U, if you want to stick with 1.9.16p11. basically, you should never refer to \\%L\HOMES in a profile path: it should always be \\%L\%U. luke ---------- From: Rob Naccarato[SMTP:rob.naccarato@sheridanc.on.ca] Sent: Tuesday, August 26, 1997 3:56 PM To: Luke Leighton Cc: samba@arvidsjaur.anu.edu.au Subject: Re: Win95 clients not logging in to Samba [$article=~s/*//;]> when the second user logs in, the [homes] share will still bepointing> to the old users' directory, except that they won't be able toaccess> any of that user's files because smbd will have done a setuid() tothe> new user. > > we'll be looking into this, to find a solution: if nothing else,we'll> have to enforce "browseable = no" on the [homes] share, which will > catch everyone out who is using it ("i'm trying to use roaming > profiles and i can't get it to work") but at least when "logon path > \\%L\%U\profile" (which i will suggest be made the default, for > compatibility with both NT and w95) instead of "logon path > \\%L\HOMES\profile" no-one will get caught out by the aboveproblem.> > rob, are you using the current default of "logon path =\\%L\HOMES"? Well, I guess so. We've decided to go back to 1.9.16p11 because of the smbd's not exiting in 1.9.17aplha5. Anyways, with 1.9.16p11, we've had to add Simeon Walker's NIS patches and I've noticed that in the logs, Samba will connect the user to \\%L\HOMES. Hmmm. How can I fix this properly in ipc.c? -- Rob Naccarato "I know I'm a lot of feathers, Sys Admin but not much chicken." Sheridan College -KM Oakville, Ont. Canada