User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
email@hidden wrote:
I can't locate your original post and don't know that I'm
remembering the symptoms correctly.
Long pauses, and outright failures, during login/logout, /when/ too many
users attempt to do so simultaneously. Only fix is to restart /server/,
not just /service/.
You said you suppressed roaming profiles, but how? On each and every client?
The only way to do it on the server is to add:
logon path =
which nulls out the compiled-in default of \\%N\%U\profile. That would
translate to \\osx-login2\%UserName%\profile and hit each user's
default share in [homes] below causing i/o on the PDC in addition to whatever
your login.bat did.
We found that by removing or even commenting-out 'logon path =
\\%N\profiles\%u', any new user logging-in is effected by the
configuration change. Upon XP login, a user is warned that network
profiles could not be found, and that a temporary profile will be used
instead. This occurs as soon as smb.conf is saved, and I assume happens
since smb.conf is read by each new smbd daemon spawned by each new
login. As soon as profiles are enabled again, after saving smb.conf, a
user logging-in to XP will not receive the profile error. This happens
regardless whether the Windows services are restarted or not.
OK, this all makes sense now....what's going on is that you're getting
screwed by roaming profiles and the reason is that there's a compiled-in
default value for "logon path". Thus, when you remove or comment
out the one in smb.conf, you don't suppress roaming profiles, instead
the compiled-in default for the roaming profiles takes over.
For example, if a user "FRED" logs in via your PDC osx-login2, then if:
a) smb.conf has 'logon path = \\%N\profiles\%u'
the client tries to load from the [profiles] share
\\osx-login2\profiles\FRED
b) smb.conf has no logon path
the client tries to load a from the [homes] share
\\osx-login2\FRED\profile
The problem with roaming profiles is that they can become huge with
almost no effort on the part of the user as they hold the desktop and
*everything* under the "Documents and Settings\FRED" directory which
includes things like "My Documents", the internet browser cache,
and most importantly the user's additions to the registry. The profiles
are accessed a lot and have to be copied back to the server at logoff.
What happens to you in case (a) then is a whole lot activity which
can slow the server. In case (b), since you didn't know they were
doing it, you don't have the right directory structure available and
so WindowsXP tells you that they have to use a temporary profile.
This temporary is truly that and is virtually useless.
I think this matches the symptoms you report
>
> Interestingly, with the 'logon path = \\%N\profiles\%u' directive
> removed from smb.conf, and with all other XP logins receiving network
> profile errors, a user who has a 'User Profile Path' specified in
> Workgroup Manager will not receive an error, and will load her profile.
>
This is the final piece. A user with his own path defined will load
that no matter what smb.conf has. Since you put that in, you probably
made sure it existed and was writable by the user.
Bottom line...the only way to disable roaming profiles and regain sanity
is by making sure they're overridden in smb.conf with a null string:
logon path =
